Academic snapshot
Marks: 60% or 6.0 common; some notes 6.5 / 65% in grad
Degree: B.E./B.Tech/M.Tech/MCA; BCA/B.Sc on listed posts
Backlogs: None active
Year: 2024-2026 batches on many 2026 off-campus ads
CGI Placement Papers 2026
CGI is a global IT and business consulting firm delivering application development, systems integration, and managed services across industries. In India, CGI runs large delivery centers and regularly hires freshers through campus and off-campus recruitment drives.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to CGI in 2026?
CGI India does not publish one eternal fresher CGPA. Campus mailers and Njoyn posts print the number that matters. This hub is the ASE / GET / apprentice engineering filter, not a partner-track consulting MBA case.
Who this hub is for
- For: B.E./B.Tech/MCA (and listed BCA/B.Sc) targeting CGI India via campus or cgi.com/en/careers.
- Not the same track: Experienced consulting manager loops, or pure service-desk if the JD is non-engineering. Read the job ID.
- Non-CS: Some 2026 apprentice posts accept any B.Tech specialisation; CS/IT is still preferred for Java/Python ASE roles.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, college % list | Aptitude + SQL/fundamentals bar |
| Njoyn / cgi.com | Job ID, batch years, on-site vs apprentice language | Same interview flavour when invited |
| Referral | Visibility | You still sit the test |
Off-campus does not mean easier quant. It often means more applicants and a longer ATS wait.
Degree, 60%, and “is 6.0 enough?”
Is 6.0 CGPA enough? It matches many guides (or 60%). Some 2026 explainers say successful India candidates sit above 65% / 6.5 in graduation with 60% in 10th/12th. If your mailer says 65%, that is your floor. A 6.2 who writes a JOIN and speaks clearly beats a 7.9 who blanks on SQL.
10th / 12th: Often checked. Keep scans.
What helps the resume screen: Java or Python, SQL, UNIX, Git, one project. COBOL/SQL keywords appear on some GET posts; do not fake mainframe. See certifications after SQL and aptitude.
Skills they actually filter
OA: Aptitude + tech MCQs + sometimes 1-2 coding
Interview: SQL, OOP, projects, UNIX light
Languages: Java, Python, SQL
Tone: Consulting communication in HR
Detailed eligibility criteria breakdown
| Item | Typical expectation | Reality check |
|---|---|---|
| Graduation | 60% / 6.0 (sometimes 65% / 6.5) | Mailer / Njoyn wins |
| 10th & 12th | 60% in several explainers | Keep marksheets |
| Branches | CS/IT preferred; any B.Tech on some apprentice IDs | Match the post |
| Backlogs | None active | Clear before joining |
| Shifts | Common on apprentice/support | HR will ask |
Who usually fits and who struggles
Good fit: You like client delivery (not only building your own app), you can write SQL without Stack Overflow, and you will relocate. Consulting branding is real in HR; day-one work is still a project team.
Harder path: You only grind LeetCode hard; you refuse shifts; you cannot explain a JOIN. CGI technicals are not Bar Raiser. They are “can we staff you on a bank/gov/telecom account.”
Branch myth: CS is preferred, not always mandatory. An ECE graduate with Java+SQL clears ASE loops. A CS graduate who cannot speak in complete sentences fails HR.
Gaps: Recent-batch language on 2026 posts is common (2023-2026 appears on some GET ads). Older gaps need a story. Active backlogs are a no.
CGI placement papers - last few years
Download 2026 CGI placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What these papers train for the written and SQL rounds
Public sectional CGI OA dumps are thinner than TCS NQT blogs. Papers on this site are services-pattern trainers: aptitude, SQL/CS MCQs, easy coding, interview themes. They are not leaked Njoyn forms.
| Round (typical) | What to practice |
|---|---|
| Aptitude / verbal | Quant, logical, English speed |
| Technical MCQs | Java/Python, OOP, SQL, UNIX |
| Coding (when present) | 1-2 easy-medium problems |
| Technical interview | Projects, SQL live, fundamentals |
| HR | Relocate, shifts, Why CGI, client tone |
Think of papers as simulators for mixed aptitude+SQL stamina. CGI reuses themes (percentages, JOINs, OOP definitions) more than exact clones. A clean 2024-style services paper still trains a 2026 invite even when the platform name changes.
Themes that keep repeating (2024-2026)
- OA (synthesised): Quantitative + logical + verbal; technical MCQs on Java, SQL, UNIX, OOP; coding 1-2 problems at LeetCode easy-medium on some drives. Exact counts not stably published.
- Technical: SQL queries on a sample schema, project walkthrough, OOP, one logic/coding question. COBOL/RDBMS on a subset of GET posts.
- HR: Consulting fit, communication, location, shifts, “are you okay supporting a global client timezone.”
- 2026 off-campus mix: ASE/GET alongside Apprentice IDs (application development, production support). Different JD, same need to read the post.
How to use one paper set in a single sitting
- Timed: 30-40 min aptitude → 20-30 min tech MCQs → 25 min one coding if your invite has it.
- Untimed: write three SQL queries on paper (JOIN, GROUP BY, HAVING).
- Map misses to aptitude and coding.
- Record a 60-second intro that mentions consulting/delivery without sounding like a slogan.
- Log one STAR story (deadline, production bug, teamwork).
Related problems to practice
| Theme you saw | Drill next | Why CGI asks it |
|---|---|---|
| Percentages / time-work | Speed | Volume aptitude |
| SQL JOIN | Employees-department queries | Interview + MCQ |
| OOP MCQs | Interface vs abstract | Technical |
UNIX ls/grep/chmod |
15 commands | MCQ / support-adjacent |
| Two-sum / strings | Complete submit | Coding add-on |
CGI placement process, round by round
CGI hires freshers through campus cells, cgi.com (Njoyn), and referrals. After eligibility, the shape is Indian IT services plus a consulting-communications overlay.
Application methods
Campus recruitment
PPT → cell list → OA → technical → HR. Same technical bar as off-campus; reserved seats and a familiar hall.
Njoyn / careers
Direct apply with job ID (GET, ASE, Apprentice). Resume screen can look for SQL, Java, UNIX keywords.
Referrals
Help visibility. You still need the test and a SQL-capable interview.
1. Resume screening
Degree, batch, %, keywords (SQL, Java/Python, Git). 3-10 days typical. Honest resume; later rounds will open SQL.
2. CGI Online Assessment (duration varies)
India fresher drives commonly follow aptitude + technical MCQ/coding. Public counts are not stable. Treat this table as a working map, then obey the email.
| Block | What usually shows up | Pass habit |
|---|---|---|
| Quant / logical | Percentages, puzzles, DI | 45-second skip |
| Verbal | Grammar, RC | Stem first |
| Tech MCQs | Java/Python, OOP, SQL, UNIX | Eliminate |
| Coding | 1-2 easy-medium | Complete submit |
No single public cutoff. Clean easy marks first. Details: online assessment.
3. Technical interview (30-45 min)
Projects, SQL on a whiteboard or shared editor, OOP, one coding/logic question, maybe UNIX. For mainframe-ish GET posts: RDBMS + COBOL basics if you claimed them. About “can we put you on a client team next month,” not system design theatre.
SQL you should write cold:
SELECT d.name, COUNT(e.id)FROM employees eJOIN departments d ON e.dept_id = d.idGROUP BY d.nameHAVING COUNT(e.id) > 5;Explain WHERE vs HAVING. That is enough for most CGI freshers. If you cannot, stop watching system-design YouTube.
4. HR / managerial (15-25 min)
Why CGI (consulting + delivery, global clients), relocate to Bengaluru/Hyderabad/Chennai/Mumbai/Pune, shifts, communication. Around 90% of tech-clear candidates get offers if logistics are honest.
Timeline from application to offer
| Phase | Duration | What happens |
|---|---|---|
| Apply / screen | 3-14 days | Njoyn or cell |
| OA | 1 day | Aptitude + tech |
| Interviews | 1-3 weeks | Technical + HR |
| Offer | 1-7 days | Letter + BG |
| End to end | ~2-6 weeks often | Longer if ATS is quiet |
ASE vs apprentice: do not mix prep
ASE / GET: Java or Python + SQL + aptitude. Coding more likely.
Apprentice (app dev / production support): SQL, basics, communication, shifts, maybe less DSA. Still not a free pass.
If the JD says COBOL, spend a weekend on file concepts and SQL, not on pretending you wrote a compiler.
Technical cabin: short answers
Why CGI not TCS? “Consulting plus delivery, smaller-feeling teams on some accounts, I want client exposure.” Do not insult TCS; you may still join them.
UNIX: Know ls, cd, grep, chmod, pipes. That is the fresher bar.
Project: User, your module, one bug, one number. Stop.
Client-communication drill (15 minutes a day)
CGI HR is checking whether you can sit on a call without collapsing. Record:
- 60-second intro (name, college, one skill, one project).
- 30-second “I can relocate and I understand shifts if the JD has them.”
- 40-second project.
Fillers (“basically, like”) bury the noun. Cut them.
Weekend mock
Saturday: 60-minute aptitude+MCQ, then 25-minute coding.
Saturday evening: three SQL queries on paper.
Sunday: 30-minute technical oral with a friend + HR answers including city.
Two weekends beat a month of unread PDFs.
Njoyn without getting lost
- Open the official careers search, not a third-party “CGI apply now” clone.
- Copy the job ID (J-numbers appear on 2026 apprentice posts).
- Fill education % exactly as on marksheets.
- Keywords: Java or Python, SQL, UNIX/Linux, Git, one project metric.
- Save the confirmation mail. Status lives on the portal.
Paying a Telegram “CGI slot” is a scam pattern. Campus queries go through your cell; off-campus queries go through the portal, not a random “HR WhatsApp.”
UNIX / Linux: the 15-command fresher bar
pwd, ls -l, cd, mkdir, cp, mv, rm, cat, head/tail, grep, chmod, ps, kill, pipes |, redirect >. Know what a process vs a file is. That covers almost every CGI MCQ and many support-adjacent interviews. You do not need to be a sysadmin.
SQL drill pack (write on paper)
- Employees with salary > department average (subquery or window).
- Count tickets per status last 7 days.
- Find duplicate emails.
- Latest order per customer (
ROW_NUMBERorMAX(date)join). - WHERE vs HAVING on the same table.
If you cannot do 2, 3, and 5, you are not interview-ready. Framework names will not save you.
Consulting vs services: what to say in 40 seconds
CGI sells consulting plus managed IT. India freshers still join delivery teams. A good line: “I want to work on client problems with a consulting firm’s delivery model, and I am fine with the location and shift rules on this JD.” A bad line: “I want to be a partner in two years” or “I only want product companies but CGI is backup.” They have heard both.
Do not insult TCS/Infosys in the cabin. You may still join them next week.
COBOL: only if the JD or resume claims it
A few GET posts still mention COBOL + SQL. If you did not study it, do not add it. If you did a college mainframe elective, say file concepts and SQL, not “I modernised a bank core.” Fake COBOL is an easy reject.
Documents and joining
10th/12th/degree scans, ID, Njoyn ID. Apprentice vs ASE tenure must match what you told HR. Background check will match percentages. Keep every email from PPT to offer.
Night-before checklist
- Job ID and login
- One aptitude set already reviewed
- Three SQL queries rewritten from memory
- City + shift sentence
- Resume one page matching Njoyn
- Sleep
What “consulting giant” means for your odds
CGI can hire quietly via job IDs rather than a mega campus day. That feels like fewer competitors until 4,000 people apply to the same Njoyn post. Your edge is SQL + complete English + a resume that matches the ID, not a 200-problem LeetCode badge.
Preparation resources for CGI
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.
How students actually prep for CGI
If a CGI 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 CGI sits around ₹4.5-7 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Campus and off-campus explainers commonly cite about 60% or 6.0 CGPA (some successful-candidate notes say 6.5 / 65% in graduation and 60% in 10th/12th), B.E./B.Tech/M.E./M.Tech/MCA and often BCA/B.Sc for listed roles, no active backlogs, and 2024-2026 batches on many 2026 posts. CS/IT preferred; some apprentice JDs accept any B.Tech. Always verify the Njoyn requisition or campus JD.
What you are training for: Typical India fresher loop: apply on CGI careers (Njoyn) or via campus cell → aptitude/technical online test (quant, logical, verbal, SQL/Java/Python/UNIX MCQs, sometimes 1-2 coding) → technical interview → HR/managerial. Timeline often 2-6 weeks. Exact section counts are not stably published; follow the invite.
Short version of the prep split: Drill services aptitude, SQL (joins, aggregations), one coding language (Java or Python), UNIX/Linux basics, and OOP/DBMS for the technical cabin. Consulting communication matters in HR: client-ready English, shifts, relocate. Full plan: /cgi/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the CGI 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 CGI 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 CGI 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 CGI?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a CGI-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.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the CGI story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 CGI PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed CGI papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many CGI papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in CGI-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
What CGI pays freshers (candidate-reported)
Figures are candidate-reported India bands as of August 2026.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| ASE / GET fresher | ₹4.5-7 LPA | Primary band for this hub |
| ASE (some 2026 blogs) | ~₹4.0-6.6 LPA | Overlaps the hub range |
| Apprentice / stipend-like | Often lower | Different JD |
| Share purchase / benefits | Role-dependent | CGI employee share plan appears in public career copy |
Confirm base vs variable on the letter. Do not quote a ₹12.5 LPA outlier as your expectation.
Benefits students actually care about
Health insurance, learning/certifications, global-client exposure, employee share purchase plan in company materials. Site and shifts still decide whether you will stay.
How to talk CTC in HR
Know ₹4.5-7 LPA. Ask split and joining. Ask whether the role is apprentice vs ASE. Do not negotiate like a product company.
Offer-stage discipline
- Read city and shift clause
- Match 10th/12th/degree to Njoyn
- Apprentice tenure vs FTE
- Verbal “selected” is not the PDF
What’s changed in CGI hiring lately
Njoyn job IDs everywhere
Off-campus GET/ASE/apprentice posts are applied on CGI careers. Batch windows (2024-2026) are printed on the ID, not on this hub.
Apprentice alongside ASE
Production-support and app-dev apprentice openings need shift honesty and SQL, not only DSA.
SQL still the interview language
Public OA counts stay sparse. Interviews still reopen JOINs and projects.
Consulting tone in HR
Client communication and relocation beat buzzword architecture tours.
Net for 2026: do not wait for a published 65-question official paper. Time aptitude, write SQL daily, finish one coding problem, practise a 60-second intro.
FAQs students ask about CGI placements
Papers & process
Can I download CGI placement papers PDF?
Yes. Free CGI placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
What is the CGI placement process?
Apply (campus or Njoyn) → aptitude/technical OA (SQL/Java/UNIX MCQs, sometimes coding) → technical interview → HR. Often 2-6 weeks. Confirm the invite.
How many rounds are there in CGI interview?
Usually 3 (OA, technical, HR). Some posts add a distinct coding challenge.
Does CGI hire through Njoyn?
Yes. CGI careers runs on Njoyn. Use the job ID. Portal status is the source of truth.
OA & language
What programming languages are allowed in CGI?
Java, Python, SQL most. UNIX commands in MCQs. COBOL on some GET posts if the JD says so.
Are CGI apprentice roles the same as ASE?
No. Apprentice JDs often stress support, shifts, and a different pay/tenure story. Read the ID.
Eligibility & offer
What is CGI eligibility criteria for freshers 2026?
Commonly 60% or 6.0 (some notes 65% / 6.5 in graduation), listed degrees, no active backlogs, recent batches. CS/IT preferred. Your Njoyn/campus notice wins.
What is CGI salary for freshers in India?
Candidate-reported ₹4.5-7 LPA for ASE/GET-style roles (August 2026). Apprentice may differ. Confirm the letter. Cities: Bengaluru, Hyderabad, Chennai, Mumbai, Pune.
Is CGI a consulting firm or an IT services company?
Both. Global consulting + IT. India freshers mostly join delivery teams. HR still tests client-ready English.
Where are CGI joining locations in India?
Bengaluru, Hyderabad, Chennai, Mumbai, Pune most often. Relocate and shifts are common questions.
Prep & comparisons
How to prepare for CGI placement?
Aptitude + SQL every day + one coding language + a 60-second intro. Guide: preparation guide.
Any pro tip for CGI placement preparation?
Make SQL and one complete coding problem automatic, then speak like you could join a client stand-up.
CGI vs Hexaware vs Accenture vs Capgemini?
All services/consulting hybrids with aptitude gates. Hexaware has GET/PGET + SpeechX. Accenture/Capgemini are larger volume. CGI’s twist is Njoyn job IDs, SQL-heavy interviews, and a consulting HR script. Prep aptitude+SQL for all; add Hexaware speaking if both are on your list.
Do I need COBOL for CGI?
Only if the JD or your resume claims it. Default fresher prep is Java/Python + SQL. Do not invent mainframe experience.
Can BCA students apply?
Some posts list BCA/B.Sc. ASE software roles may still prefer B.Tech/MCA. Read the qualification line.
What should I write on a CGI resume?
Match the job ID: Java or Python, SQL, UNIX/Linux, Git, one project with a metric. Do not add COBOL unless you can defend it. Keep % identical to marksheets for Njoyn.
Is there negative marking in CGI OA?
Not stably published. Follow the invite. Even without -1, random fills waste time you need for SQL MCQs and coding.
Real CGI interview notes from candidates
Public detailed CGI fresher OA blogs are thinner than TCS/Infosys. Use composites, then verify the invite. More: interview experience.
Njoyn off-campus GET/ASE (2026 explainers): Resume screen looks for CS/IT, batch year, SQL/Java/Git keywords. OA mixes aptitude with SQL and programming fundamentals. Technical reopens COBOL only when the post is mainframe-adjacent. Takeaway: tailor the resume to the job ID instead of one generic “software engineer” PDF.
Technical cabin composite: Interviewers ask a JOIN, a project bug, and “what would you do if a client ticket comes at 11 p.m.” Students who only prepared trees and graphs felt the round was “too easy” and still failed SQL. Takeaway: CGI is not hiding a Hard problem. They are hiding a JOIN.
HR composite: Relocation + shifts + Why CGI. Candidates who said “I want work-life balance and WFH” on a production-support apprentice ID wasted everyone’s time. Takeaway: read the JD’s shift line before you practise “Why CGI.”
What to steal: SQL on paper; one coding submit; 60-second intro; honest city/shifts; Njoyn job ID on every form.
What to ignore: Fake COBOL; Telegram “CGI OA 2026 leak”; quoting ₹9 LPA as guaranteed GET pay.
Selected vs rejected: Helped: clean SQL, calm English, documents. Hurt: blank JOIN, mumbled HR, surprise at Bengaluru on-site.
Apprentice vs ASE mix-up: A student prepared only DSA, sat a production-support apprentice ID, and could not talk shifts or basic SQL. Another student with weaker CGPA but honest support internship language cleared. Takeaway: the job ID is the syllabus.
Long ATS silence: Njoyn can go quiet for weeks. Keep a 30-minute weekly loop (aptitude + 3 SQL + intro) until you withdraw or join. Students who “took a break” after applying forgot JOIN syntax before the interview mail arrived.
Client-timezone HR: “Are you okay with overlap hours for a US/Europe client?” Yes only if you mean it. Saying yes and then refusing in week two is how teams remember your college.
CGI is a consulting-and-delivery hire, not a 65-question official paper you can memorise. Public OA counts stay messy. Interviews do not. They ask SQL, a project, and whether you will move and speak like a client-ready junior.
Use this site papers as services simulators. Drill JOINs until they are boring. Keep a 60-second intro. Apply on Njoyn with the real job ID. Follow the preparation guide for a week plan and interview experience plus HR questions for cabin language.
If CGI and Hexaware/Accenture/Capgemini collide, compare ASE vs apprentice vs GET/PGET, city, and shifts. A 5 LPA ASE you understand beats a 6 LPA title you cannot explain. Keep every portal mail. Do not pay for a “CGI dump.” Do not invent COBOL. Do not ghost a shift you agreed to.
Share purchase and benefits show up in career copy. They are not a reason to skip reading the apprentice tenure line. Ask HR what the designation is in the letter. Ask joining city. Ask whether the role is production support. Then decide.
Week-of-drive: one aptitude mock, three SQL queries from memory, intro once, sleep. That is enough if you have been practising. Cramming UNIX man pages at 2 a.m. is how people blank grep in the morning.
Campus PPT: write down the job ID even if the cell already registered you. Off-campus: that ID is your entire process. Mixed IDs (Java ASE vs any-branch apprentice) are how students prep the wrong language. Read it twice. Then prep that. Then stop.
Similar companies on this hub exist so you can reuse aptitude+SQL, not so you can copy-paste the same “Why CGI” into Accenture HR. Change the sentence. Consulting delivery is the CGI-specific bit. Use it if it is true for you. If it is not, pick another firm. That honesty survives a 20-minute HR. A slogan does not.
Interview day: Njoyn login works; job ID on a sticky note; three SQL queries you can rewrite if the editor is empty; one project story with a bug; city/shift sentence. If the OA is remote, camera on, no second monitor drama. If technical is virtual, share screen only when asked; talk while you type the JOIN.
Managerial overlay: some loops combine HR with a delivery manager. They will ask how you handle a wrong estimate or a ticket you do not understand. STAR: situation, what you did, result in one number. Keep it under 90 seconds. CGI does not need your life history.
On-site vs hybrid: apprentice and support JDs are office/shift heavy. ASE may vary by account. Ask. Do not assume Montreal-style consulting WFH on a Bengaluru production roster.
Why the OA feels “generic”: because CGI does not publish a stable 65-question brochure. Students waste weeks hunting a leaked paper instead of timing aptitude and writing SQL. The hunt is the fail mode. Timed mocks plus JOINs are the pass mode.
After the offer: read designation (ASE vs apprentice), city, joining date, any training bond if present (less famous than Hexaware’s 3-year slide, still read). Compare with other services letters on site and tenure, not on a LinkedIn CTC screenshot.
Keep the online assessment page for platform notes and this hub for the spine. That split is on purpose. Week plans live on the preparation guide. Do not paste a week plan back onto the hub. Drill. Apply. Show up. Write the JOIN. Speak. That is CGI for freshers in 2026.
Campus vs Njoyn double apply: if your college is hosting CGI and you also applied off-campus, tell the cell. Two parallel processes can confuse joining dates. One offer letter is the one you sign. The other you withdraw politely.
Referrals: a CGI employee can push a resume. They cannot sit SQL for you. Send them a one-page PDF that matches the job ID. Do not send a 4-page illustrated CV.
English in technical: if you can write a JOIN but cannot explain it, practise out loud. Consulting HR is not the only round that hears you. The technical interviewer is a future teammate on a client call.
What not to do this week: download five new apps; memorise COBOL reserved words you will not use; argue 55% vs 60% on a forum; pay for a “guaranteed CGI” slot. Do: one timed aptitude, three SQL, one intro. Repeat tomorrow.
Come back to this hub only if a new job ID changes apprentice vs ASE. Otherwise the map is: Njoyn ID, aptitude clock, JOIN on paper, city/shift sentence, letter. Ghosting a shift you agreed to is how teams remember your college. Withdraw in writing instead.
If you cannot write a department JOIN without looking, that is today’s prep, not another FAQ. Write it. Sleep. Sit the drive. Read the PDF. That is CGI for a fresher loop. If two Njoyn IDs are open (ASE and apprentice), apply only to the one you will actually join; dual processes are how joining dates collide. Withdraw the extra application in the portal if you already have a written ASE offer.