CGI India fresher loops mix aptitude-heavy online tests with resume-focused technical and HR conversations. This page synthesizes campus SE, SDE Intern, and older AMCAT-style drive patterns into round tables, outcome notes, and prep traps.
Round-wise process at a glance
Round
Typical format
What clears you
Pre-placement talk
Company / process / CTC overview
Attend; note role location
Online test
5 sections (quant, verbal, BA, coding×2, CS)
Pace; do not neglect Business Analytics
Technical / techno-managerial
~30-45 min; resume + coding + SQL/OOP
Know every resume line; optimise OA code if shown
HR
Location, Why CGI, communication; sometimes videos/presentation
Clear motivation and communication
Technical interview experience 1 - Campus drive with AMCAT-style OA
Technical interview experience 1
Candidate profile: Campus fresher process documented Aug 2018 on GeeksforGeeks (AMCAT pattern).
Round 1 - Online test (sequential sections)
Quantitative Aptitude (~16 Q, ~60 s each) - easy if practised
Verbal Ability & RC (~22) - moderately tough
Business Analytics (~8) - candidate called this the hardest section
Coding (2) - pattern printing / bitwise described as cake-walk
Computer Science (~26) - DBMS, OS, CN only in this recollection
No negative marking; cannot skip ahead across sections
Round 2 - Technical / Techno-Managerial
Prompt: array A[], integer NUM → output pair (a, b) with a * b = NUM in O(n) (hash table hint)
Shown OA coding results - asked to optimise and improve readability
Random puzzles; SQL queries; deep projects / internships
Tip: Know your resume cold
Round 3 - HR extras
Two 1-minute selfie videos: Introduction and My Role Model
5-min presentation on an emerging tech (topics provided: DevOps, Blockchain, RPA, IoT, AR, ML - other topics allowed)
Willingness to work for CGI is the soft bar
Key takeaways: Practise Business Analytics style DI; prepare a short emerging-tech talk; be ready to defend and refactor your OA code live.
Takeaways
What decided it: Clearing sequential OA sections (especially Business Analytics) and defending an O(n) pair-product solution plus OA-code refactor live
Common fail: Treating BA as filler, or blanking when shown your own OA code to optimise
How to practise: Timed DI sets; hash-map pair-product drills; rewrite one pattern/bitwise solution for clarity; rehearse a 5-min DevOps/ML-style talk once aloud
OOP: pillars; inheritance; polymorphism; two types of polymorphism
SQL queries
HTML tags (candidate flagged as a weak spot)
HR round (~30 min, online 1:1)
Preferable location
What do you know about CGI?
What excites you to join CGI?
Communication-focused
Timeline note
~45 days to offer; ~6 months to onboarding in this account
Hybrid culture mentioned; patience required
Final result: Placed
Key takeaways: Fresher CGI technicals can stay on OOP/SQL/resume basics. Revise HTML/web basics if on the resume; expect slow post-select logistics.
Takeaways
What decided it: Solid OOP/SQL/resume answers in a ~30 min campus technical, then clear Why CGI and location answers in HR
Common fail: Weak HTML/tag basics when web appears on the CV, or abandoning prep during the long offer wait
How to practise: Flashcard OOP pillars and polymorphism types; write 3 SQL joins from memory; draft a 60-second CGI pitch and keep DSA warm while waiting
Technical interview experience 3 - Large campus drive, two technical rounds
Technical interview experience 3
Candidate profile: Campus Software Developer drive with AMCAT-style OA; pattern aligned with GeeksforGeeks CGI recruitment overview and multi-round fresher reports.
Online test
Aptitude, verbal, technical MCQs (Java/OOP/SQL), sometimes sectional cutoffs
Coding: pattern printing, frequency sort, or similar easy–medium tasks on some drives
Tree traversals; Dijkstra explanation; basic multithreading
Live SQL joins on employee/department schemas
Technical round 2 (larger drives)
Pattern printing programs; Trie concepts; basic Linux internals (/proc, swap) on some panels
One reported funnel: ~85 shortlisted after OA → 16 offers - second round bar noticeably higher
HR close
Family background, role/location preference, Why CGI, team environment
Sometimes merged with final technical on smaller drives (~30 min combined)
Key takeaways: If your college shortlist is large, prep round-two DS/systems topics, not only OOP definitions. Honest relocation answers matter - HR often checks client-timezone flexibility.
Experience 4 - Software Engineer on-campus (Jan 2021, single panel)
Combined technical + HR (2021)
Candidate profile: On-campus Jan 2021 per GeeksforGeeks SE report - five-section written test then one virtual panel (~30 min).
Intro; project explanation; branch/domain motivation (e.g. why ECE if non-CS)
Skills/courses only from resume - no surprise topics off-CV
Common HR prompts woven into same panel
Final result: Selected
Key takeaways: Smaller CGI drives collapse rounds - your resume is the question bank. Confidence and resume-aligned answers beat generic LeetCode grinding.
HR interview experience
HR interview experience
Typical prompts: Why CGI, location preference, role model / intro videos, emerging-tech presentation, communication checks. Older SE campus reports (Jan 2021) used a single panel for both technical and HR in ~30 minutes after a 5-section written test.
Tip: Prepare a 60-second CGI pitch (global IT consulting, India delivery centres, role you applied for).
Sample answers for high-frequency questions
Q. Find two numbers in an array whose product is NUM in O(n). A. Scan once; for each x, if x != 0 and NUM % x == 0 and (NUM / x) is in a hash set of seen values, return the pair; else insert x. Handle zeros and duplicates carefully.
Q. OOP pillars - polymorphism types? A. Encapsulation, Abstraction, Inheritance, Polymorphism. Compile-time (overloading) vs run-time (overriding via virtual dispatch). Give a one-line real example for each.
Q. Why CGI? A. Concrete: global consulting + India delivery, tech stack from PPT/JD, and how your project skills map to client delivery - not “good package” alone.
Q. Emerging-tech 5-minute talk structure? A. What it is → one real use case → risks/limitations → why it matters to CGI clients → one slide-worth takeaway. Practise aloud once.
These links are research inputs used to map CGI OA sections, techno-HR prompts, and campus timelines - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.
Confirm section counts and presentation requirements against the current CGI drive mail.
