Globant Software Engineer interview typically runs 3 rounds: HR, technical interview, client/project interview. Timeline is usually a few weeks and can be slow, with client-side approval affecting the pace.
$90K
Avg. Base Comp
$178K
Avg. Total Comp
3-5
Typical Rounds
3-6 weeks
Process Length
We’ve seen Globant evaluate software engineers less like a single-company product team and more like a proxy for the client’s needs. A recurring theme across candidate reports is that the technical bar shifts with the project: one person was pressed to recite the structure of an application from memory, while others faced deep dives into JavaScript event-loop behavior, C# async patterns, or cloud and DevOps tooling. That tells us the company is looking for engineers who can speak fluently about real implementation details, not just name the right concepts. If your answers stay abstract, the follow-up questions tend to expose it quickly.
Another pattern is how much weight they place on practical context. Multiple candidates mentioned questions about current projects, day-to-day work, and how they would handle production issues, plus follow-ups on architecture choices like microservices, circuit breakers, dependency injection, and design patterns. We also saw a strong preference for clear, grounded explanations of past work — especially when the interviewer kept probing until they were satisfied the candidate truly understood the tradeoffs. In other words, Globant seems to reward engineers who can connect fundamentals to the systems they’ve actually built, whether that’s a React UI, a backend service, or a cloud deployment.
The non-obvious risk here is inconsistency. Some candidates described a warm, straightforward process, while others felt the technical tone was tense or overly memory-based, and the client’s approval could change the outcome late in the process. That means preparation is only half the battle; the other half is being ready for a very specific kind of scrutiny. Our candidates report that the people who do best are the ones who can stay precise under pressure and adapt quickly when the interviewer pivots from theory to a concrete codebase or architecture scenario.
Synthetized from 5 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Globant process.
A profissional de RH foi a melhor parte do processo. Ela fez várias perguntas, escutou com atenção e realmente parecia interessada em entender meu perfil. O problema veio na parte técnica, que para mim ficou bem aquém do esperado. Em vez de uma conversa mais prática ou de resolver um problema de código, o entrevistador quis que eu descrevesse de memória a estrutura de uma aplicação inteira, com classes, composições, anotações e até dois endpoints, um GET e um POST. A sensação foi de que ele esperava que eu soubesse literalmente como o código estava montado, quase como se eu tivesse decorado toda a base do projeto.
Prep tip from this candidate
Vale revisar bem como montar uma controller do zero, incluindo anotações, composição de classes e definição de endpoints GET e POST. Também ajuda praticar explicando a estrutura de uma aplicação sem depender de abrir o IDE, porque a entrevista parece cobrar esse nível de detalhe de memória.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Globant
Design a system to enforce file and code restrictions in a multi-team Git repository.
| Question | |
|---|---|
| Text Editor With OOP | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Prime to N | |
| Employee Salaries | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Comments Histogram | |
| Size of Joins | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Upsell Transactions | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Raining in Seattle | |
| Manager Team Sizes | |
| Hurdles In Data Projects | |
| Job Recommendation | |
| P-value to a Layman | |
| Minimum Change | |
| Address Schema | |
| Lowest Paid |
Synthesized from candidate reports. Individual experiences may vary.
The process usually starts with HR or a recruiter reaching out to discuss your background, experience, motivation for leaving, and salary expectations. In some cases they also assess English level and explain the role or client context before scheduling technical interviews.
This round is typically a deep technical conversation with a developer, architect, or two programmers. Candidates reported questions tailored to the stack, including JavaScript and React, C# and async/await, backend architecture, DevOps tools like Docker and Kubernetes, and practical coding or problem-solving questions.
Some candidates go through a second technical interview that goes further into architecture and implementation details. Topics mentioned include microservices, circuit breaker, CQRS, git rebase, Terraform, cloud, Selenium, XPath, and handling dynamic elements, with interviewers probing for depth rather than surface-level answers.
For many roles, the final decision depends on alignment with the client or project. Candidates noted that this stage can influence whether the offer moves forward, and that the company may adjust the role based on client needs.
In some processes, there is a final HR conversation or feedback call after the technical rounds. Candidates described this as a closing step where the company shares next steps or feedback, though the timeline can be slow and the offer may still depend on client confirmation.