Academic snapshot
Marks: 6.5+ CGPA / 65% (candidate-reported)
Degree: B.E. / B.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Globant is a digital engineering company that builds software products and AI-powered experiences for global brands across industries. Founded in 2003, it maintains growing India delivery centers in Pune, Bengaluru, and other cities, hiring for full-stack, cloud, and AI engineering roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT, college CGPA list when printed | Coding + communication bar |
| Careers portal | AI-powered talent flow on career.globant.com; resume volume | Still expect an assessment + interviews |
| Referral / studio | Faster visibility into a specific studio | You still defend code and projects |
Off-campus does not mean easier coding. It often means more applicants and a less predictable section list. If your CGPA sits near 6.5, spend energy on mocks, not on hunting a 6.0 blog post from 2022.
Studio vs “any IT offer.” Globant’s campus story is digital products and AI studios for global brands. That does not make the first filter a personality test. You still need passing code. What changes after the assessment is the conversation: client tone, agile rituals, and whether you sound like you could sit in a sprint review without reading a script. If you are also prepping TCS/Infosys-style papers the same week, keep a separate Globant hour for OOP + one product story - do not assume the same 90-question aptitude marathon.
Is 6.5 CGPA enough? It matches the commonly reported floor. Selection still hinges on assessment correctness and whether you can talk like someone who will sit on a client call. A 6.6 with clean timed coding beats a 8.4 that cannot explain a project without reading the resume.
Branches: CS/IT/ECE (E&TC) dominate shortlists. Related circuit branches show up when DSA and OOP are solid. If your college lists only “CS/IT,” do not assume ECE is auto-included.
Gaps and backlogs: Active backlogs are the usual blocker at offer time. A short gap is easier to explain with a shipped project than silence. Older off-campus posts also cited 60% throughout - your mailer wins.
What helps the resume screen: One project you can defend as a product (users, stack, hardest bug), any internship with ownership language, and JavaScript/Java/Python keywords you can actually use live. Certificates are optional extras. See certifications after fundamentals are solid.
Academic snapshot
Marks: 6.5+ CGPA / 65% (candidate-reported)
Degree: B.E. / B.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Branch & skills
Preferred: CS / IT / ECE (E&TC) and related
Languages: Java, JavaScript, Python
Focus: DSA, OOP, agile communication
Differentiator: Product-studio + client-ready talk
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.5+ CGPA / ~65% (some older posts: 60%) | Verify every drive; 10th/12th sometimes listed too |
| Degree | B.E. / B.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE / E&TC | Strong DSA can help adjacent branches on some drives |
| Year | Final year + recent grads | Batch years are printed on off-campus posters |
| Backlogs | No active backlogs preferred | Clear them before offer paperwork |
| Coding languages | Java, JavaScript, Python | Stick to one for OA + interviews |
Minimum CGPA required (candidate-reported): 6.5+ CGPA / 65% is the commonly cited campus floor for fresher builder roles. Treat it as a shortlisting filter when printed - Globant still decides on assessment correctness and cultural-fit narration.
Globant shortlists on academics when the JD prints a floor, then filters on the Assessment. Clearing CGPA only gets you into the funnel - coding speed and communication decide whether you see an offer.
Globant does not publish one universal India cutoff. Numbers below are candidate-reported (as of August 2026). Your placement cell mailer always wins.
Download 2026 Globant placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Globant does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Assessment | Timed coding correctness + language/OOP fundamentals |
| Technical | Live coding narration + project ownership |
| Cultural fit | Agile, feedback, client-tone stories |
| HR | Why Globant, Pune/Bengaluru move, notice/exams |
UI studio vs ASE generalist papers. If the mailer says Web UI / frontend, yesterday’s “only Java DSA” plan is incomplete. Add a night of closures, let/var/const, and one React component you can draw from memory. If the mailer is generic ASE, stay on Java/Python DSA + OOP and do not cram a new UI framework 48 hours out. The 2024 LinkedIn UI loop is a warning, not a universal syllabus.
| Theme you saw in a set | What to drill next | Why Globant asks it |
|---|---|---|
| First unique character | Hash map + queue variants | String processing on product UIs |
| Valid parentheses / stack | Nested structures | Parser / editor / form validation intuition |
| Two sum / hashing | Complements, duplicates | Classic OA speed |
| OOP (inherit vs compose) | Small class design | Studio code reviews talk this way |
| JS closures / event loop | let vs var, promises | Web UI studio screens |
| SQL joins (when present) | Aggregations | Data-backed product features |
2024 PDFs often drill “first non-repeating character.” Own the frequency map + left-to-right scan - then drill a related problem that returns the last unique character. That transfers to interviews; memorising the story text does not.
Globant India hires freshers through campus placement cells, career.globant.com, referrals, and studio-specific drives. After resume screen, the shape is digital-engineering: timed assessment, then coding + culture, then HR.
Campus recruitment
Through college placement cells - PPT, then assessment and interviews on a batch timeline.
Online applications
Apply on career.globant.com; complete any talent-experience / assessment steps in the mailer.
Referrals
Employee referrals improve visibility. You still need passing code and a clear cultural-fit story.
Placement cell or recruiter checks degree, CGPA floor when printed (6.5+ / 65% commonly reported), backlogs, and year of passing. Projects that look like real products (web app, API, mobile, a bit of AI) help when volumes are high. This is a gate - coding is the hard filter.
Public sectional dumps are thinner than Cognizant-style papers. Treat this as a working map:
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Coding | 1-2 problems | ~40-60 min | Arrays, strings, hashing, OOP-flavoured logic |
| Fundamentals / MCQ | ~10-20 (when present) | ~20-30 min | OOP, language basics, light aptitude |
| Domain (UI tracks) | JS/HTML/CSS mix | Drive-specific | Closures, DOM, one logic problem |
Languages: Java, JavaScript, Python (C/C++ on some papers). Platforms: HackerRank, Codility, or Globant’s own talent flow - confirm yours.
Pass bar in practice: A fully passing easy/medium beats a clever incomplete hard. UI tracks still fail people who cannot explain let vs var.
Student tip: Skim all prompts in 3 minutes. Bank the solvable one. Write two edge cases before submit.
| Minute | Move |
|---|---|
| 0-4 | Skim all statements; mark the easier coding |
| 4-20 | MCQ / fundamentals if present - skip sticky items |
| 20-50 | Coding problem 1: restate → brute → optimize → tests |
| 50-70 | Second problem or harden edge cases |
| 70-75 | Flagged MCQs; do not open a new hard rabbit hole |
Deeper OA notes: Globant Online Assessment.
Video shared editor or live discussion. Expect 1 DSA or language problem plus a project deep-dive. UI studios add JavaScript (scope, closures, event loop) and a React/HTML question. Backend-leaning panels stay on Java/Python OOP, collections, and SQL.
You should:
Example narration (stack / valid brackets): “I’ll use a stack of opening symbols. A mismatch or leftover openers fails. Empty string is valid.” I’ll code the map first so the loop stays boring.” That 30-second plan already helps.
This is Globant’s differentiator versus a three-round services mill. They want evidence you can work in squads, take feedback, talk to non-engineers, and stay curious about AI-assisted delivery without sounding like a LinkedIn bot.
Prepare:
Worked cultural-fit shape (requirements moved): “Sprint goal was a checkout flow. Mid-week the client wanted guest checkout too.” I listed what we would drop (saved-cards UI), flagged the test cases, and told the lead in stand-up instead of silently slipping the date.” That is a studio answer. “I am adaptable and a team player” is not.
Worked technical shape (project ownership): Name the user, the stack, the hardest bug, and the metric (latency, conversion, test coverage). If it was a group project, say your files. Interviewers at digital-engineering firms have heard “we used React and Node” a thousand times - they are listening for the bug.
Why Globant, relocation to Pune or Bengaluru, notice/exams, strengths-weaknesses with proof. Know the ₹7-12 LPA fresher band so CTC talk is grounded. Ask one real question about the studio (travel, tech, client industry) - it beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | Assessment | ~60-90 min typical | Timed coding + fundamentals |
| 2 | Technical | 40-60 min | Code + project ownership |
| 3 | Cultural fit | 20-30 min | Agile / client communication |
| 4 | HR | 15-25 min | Logistics, motivation |
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then assessment window |
| Assessment → shortlist | Few days common | Portal flows can be faster or slower |
| Interview loop | ~1-2 weeks | Tech → cultural fit → HR |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~2-4 weeks campus batches often | Off-campus can be 3-6+ weeks |
| Component | Focus | Prep move this week |
|---|---|---|
| Coding | Hashing, strings, stacks, arrays | Two timed mediums back-to-back |
| OOP / language | Classes, collections, JS scope | One page of flash + one tiny design |
| Aptitude (if present) | Speed | Timed mock quiz |
| Cultural fit | Client-tone STAR | Two stories spoken aloud |
| HR | Why studios, city | Relocation answer + CTC context |
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Globant invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Globant sits around ₹7-12 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Globant eligibility for freshers 2026 is candidate-reported, not one official published cutoff. Common campus/ASE baseline: B.E./B.Tech/MCA in CS, IT, ECE/E&TC or related; typically 6.5+ CGPA / 65% across 10th, 12th, and graduation; no active backlogs preferred; final-year students and recent graduates. Always verify the drive notice or career.globant.com posting.
What you are training for: Globant India fresher loops commonly run: Globant Assessment (timed coding + fundamentals) → Technical (DSA/OOP + projects) → Cultural Fit / values → HR. Some drives merge cultural fit into HR. Campus batches often finish in about 2-4 weeks; off-campus and studio-specific loops can stretch.
Short version of the prep split: Treat Globant as a digital-engineering studio, not a mass IT services drill. Split time roughly: 45% DSA/coding, 20% OOP + language depth (Java, JavaScript, or Python), 20% CS fundamentals and projects, 15% cultural fit / agile stories. Clear the assessment before polishing studio vocabulary.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Globant previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Globant drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Globant usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Globant?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Globant-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Globant story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Globant papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Globant papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Globant-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Globant paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Globant. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Globant, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on role (ASE vs UI vs other), location (Pune / Bengaluru), hiring year, and written components.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Associate Software Engineer / fresher | ₹7-12 LPA | Primary band for this hub |
| Older off-campus posters | ~₹3.8-4.8 LPA during probation (historical) | Do not mix 2022 posters with 2026 campus talk |
| Specialist / experienced | Wide spread | Outside fresher prep scope |
Confirm base, variable, and probation language on the written offer. Do not treat blog midpoints as guarantees.
Know the ₹7-12 LPA fresher context, ask how the package splits, and clarify joining date vs exams. One calm question beats aggressive negotiation with a 2022 screenshot.
Typical path: Globant Assessment (coding + fundamentals) → Technical → Cultural Fit → HR. Some drives merge cultural fit into HR. Campus batches often finish in about 2-4 weeks. Confirm round names on your invite.
Most fresher ASE loops report four stages. UI or experienced loops may add a domain screen. Count the mailer.
Yes. Free Globant placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers, not leaked live papers. Start with the 2026 PDF or the paper archive.
Candidate reports describe a timed coding + fundamentals screen. Section counts are less standardized than big IT drives. Platforms like HackerRank or Codility appear; the careers site also runs an AI-powered talent flow. Verify yours.
Commonly reported floor: 6.5+ CGPA / 65% (some older posters: 60% throughout), CS/IT/ECE-related degrees, no active backlogs preferred. Your drive notice overrides this page.
Candidate-reported ASE / fresher CTC often lands around ₹7-12 LPA (as of August 2026), mainly Pune and Bengaluru. Historical probation figures were lower. The written offer is the only number that matters.
Those are the main India hubs candidates report. HR usually checks willingness. Studio/client needs can drive city - be honest early.
Split time roughly 45% DSA, 20% OOP/language, 20% projects/CS, 15% cultural fit/HR. Clear timed assessment mocks first. Details: preparation guide.
Java, JavaScript, and Python are the usual set; C/C++ appear on some papers. Confirm on the invite. Do not switch the week of the drive.
A values / studio-fit conversation: agile teamwork, feedback, client communication, learning mindset. Prepare specific STAR stories. It can reject strong coders who only give slogans.
All three care about code quality and communication. Globant leans digital studios + AI experiences for global brands. EPAM is often engineering-delivery heavy; Thoughtworks is known for a strong consulting/craft bar. Prep DSA for all; customise the studio story.
No. A solid product project beats a copied chatbot. Know enough to talk about where AI helps delivery without pretending you trained a foundation model.
Bank a passing assessment solution first, keep an error log, and rehearse one project in client language before cultural fit. Correctness under time beats a half-finished clever solution.
Start with Globant interview experience on this site, then recent community write-ups for your target studio. Patterns shift - use them as maps, not scripts.
Older off-campus ASE posters mentioned probation (sometimes months) before confirmation CTC. Current campus offers vary. Ask HR what the written letter says about probation, variable pay, and notice - do not recycle a 2022 poster as fact.
India fresher roles students report are still city-based (Pune / Bengaluru) with studio/office norms that depend on the account. HR will ask. If you can only do fully remote, say so early rather than after the offer.
Then those questions land in HR or at the end of technical. Still prepare the same STAR set. Missing the named round on the mailer does not mean Globant stopped caring about communication.
Profile patterns that got selected: B.Tech CSE/IT/ECE, roughly 6.8-8.0 CGPA, one internship or a shipped web/backend project, decent English for client-facing talk, steady DSA rather than last-week panic.
Assessment: Timed coding. Fully passing solutions beat partial cleverness. Students who triaged prompts early survived. UI tracks punished weak JavaScript fundamentals even when the logic problem was easy.
Technical: Resume walkthrough, one coding or language problem, “what did you do on this group project?” Interviewers noticed people who could name a trade-off (REST vs extra client state, SQL vs dumping JSON in a file).
Cultural fit / HR: Why this studio? Working with unclear requirements? Relocation? Keep answers short: situation → what you did → result. Generic culture praise landed flat.
Takeaway candidates repeated: clear DSA plus a coherent product story beats a high CGPA with weak explanation. Talking like a teammate mattered as much as the final snippet.
What hurt other candidates: coding before clarifying constraints; treating cultural fit as HR small talk; listing five frameworks; freezing when asked “explain this to a designer”; anchoring salary on outdated 3.8 LPA posters without reading the current offer.
A September 2024 LinkedIn Web UI Developer loop (India) described a first round on JavaScript, React, HTML/CSS plus one coding problem (scope, closures, let/var/const), then a resume-deep technical, then HR. Interviewers were described as unhurried - which still means you need real answers, not more time to bluff.
Older 2022 ASE off-campus posters (Pune, 60%, CS/IT/E&TC) are useful for process shape (registration → assessment → technical → HR) but not for 2026 CTC.
A week-of-drive checklist that actually gets used:
What “selected” looked like vs “almost”: Selected students usually had one fully passing assessment problem, a project they could narrate without opening GitHub, and a cultural-fit story with a date and a decision. Almost-selected students often had better CGPA but froze on “what did you personally ship?” or treated cultural fit as a compliment contest.
More fresher narratives: Globant interview experience.