Globant's Software Engineer interviews usually pair an HR screen with a stack-specific technical round (JavaScript/React, Java/Spring, or .NET), and some candidates report a separate project-matching step that can add time before a final offer.
$125K
Avg. Base Comp
$156K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Globant's Software Engineer interview process usually starts with an HR or recruiter screen covering your background, current role, and experience, and candidates describe this first conversation as friendly and low-pressure. The core technical interview, typically with a developer or senior engineer, is where preparation pays off most, and its content tracks closely to your stack. A Web UI Developer reported roughly an hour on JavaScript and React: closures, hoisting, setImmediate versus process.nextTick, throttle and debounce, output-based questions, a Promise.all polyfill, and React state handling and performance. Java candidates describe OOP, SOLID, testing, Spring Boot, and JPA. A .NET-focused senior candidate faced abstract classes, access modifiers, TPL, async/await, dependency injection, design patterns, and ASP.NET routing. A junior candidate noted that questions escalate step by step from basics like class versus object, so expect interviewers to keep pushing until they find the edge of your knowledge.
What stands out across these reports is what can happen after a strong technical round: some candidates describe a separate project or client-assignment step. One backend candidate received offer terms but was told finding a matching project could take months. That candidate later faced a live coding challenge with a project manager and was rejected. Another candidate had an offer letter held up until the client confirmed. Timing is inconsistent: a Cloud Engineer went from first recruiter contact to a response in about six days for an urgent client need, while others describe processes stretching over several weeks. Prepare deeply for your specific stack, and ask recruiters directly whether an offer depends on client or project confirmation before treating it as final.
Synthesized from 21 candidate 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.
The HR professional was the best part of the process. She asked several questions, listened carefully and really seemed interested in understanding my profile. The problem came in the technical part, which for me fell well short of expectations. Instead of a more practical conversation or solving a coding problem, the interviewer wanted me to describe from memory the structure of an entire application, with classes, compositions, annotations and even two endpoints, a GET and a POST. The feeling was that he expected me to know literally how the code was put together, almost as if I had memorized the whole project codebase.
Prep tip from this candidate
It is worth reviewing how to build a controller from scratch, including annotations, class composition and defining GET and POST endpoints. It also helps to practice explaining the structure of an application without relying on opening the IDE, because the interview seems to demand that level of detail from memory.
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 | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Find the Missing Number | |
| Largest Salary by Department | |
| String Shift | |
| Rolling Bank Transactions | |
| Size of Joins | |
| Customer Orders | |
| Comments Histogram | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Retailer Data Warehouse | |
| Minimum Change | |
| Flight Records | |
| Upsell Transactions | |
| Lowest Paid | |
| Level Of Rain Water In 2D Terrain | |
| P-value to a Layman |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically start with a recruiter or HR call covering work history, current role, and professional experience. Candidates describe the tone as friendly and low-pressure compared with the technical rounds that follow, and salary expectations can come up during the process.
The main technical round typically pairs you with a developer or senior engineer for roughly one to one-and-a-half hours and focuses on your stated stack. A JavaScript/React candidate reported closures, hoisting, event-loop, output-based, and React state and performance questions. Java candidates covered OOP, SOLID, testing, Spring Boot, and JPA. A .NET candidate described TPL, async/await, dependency injection, and ASP.NET routing. Output prediction or a technical challenge may be included.
Some candidates report extra steps beyond the main technical interview. One backend candidate was asked to live-code a loosely specified problem on a call with a project manager, with no test cases to validate against. A junior candidate described a third interview dedicated to feedback. These extras are not universal.
Some candidates report that clearing the technical interview is not the end of the process: Globant may require additional interviews tied to finding or confirming a client project. One backend candidate received offer terms but was told matching a project could take months; weeks later, a project manager ran a live coding round that ended in rejection. A senior candidate added that these project-assignment interviews can be competitive.
Timing varied widely. One Cloud Engineer candidate went from first recruiter contact to a response in about six days because of an urgent client need. A Web UI Developer's offer letter was delayed because the client had not yet confirmed. It is worth asking HR directly whether an offer depends on client approval before treating a verbal yes as final.
