Academic snapshot
Marks: 55% official language / 60% or 6.0 on many campus JDs
Degree: B.E. / B.Tech / M.Tech / MCA (plus listed non-B.Tech tracks)
Backlogs: No current backlogs
Year: Final-year and recent grads
Coforge is a digital services and IT company serving clients in travel, banking, insurance, and other industries, formerly known as NIIT Technologies. India hubs in Greater Noida, Bengaluru, Hyderabad, and Chennai are primary hiring locations for software and consulting roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, college % list, possible communication-first round, possible bond slide | Aptitude + coding bar |
| careers.coforge.com | Application form; campus@coforge.com for queries | Same assessment flavour when invited |
| Referral | Visibility | You still sit the test |
Off-campus does not mean easier quant. It often means more applicants who skip speaking practice and fail a Mercer communication section.
Is 6.0 CGPA enough? It matches many campus mailers. The official fresher page has cited 55% throughout 10th, 12th, and degree with no current backlogs. If your mailer says 60%, that is your floor. A 6.1 who finishes the coding question and speaks clearly beats a 7.8 who blanks on SQL in technical.
10th / 12th: They count. Keep marksheets. “Throughout” means they can reject a 9.0 B.Tech with a 52% in 12th if the rule is printed.
What helps the resume screen: One project you can explain without jargon, any internship, readable English. See certifications after aptitude and coding, not instead of them.
Academic snapshot
Marks: 55% official language / 60% or 6.0 on many campus JDs
Degree: B.E. / B.Tech / M.Tech / MCA (plus listed non-B.Tech tracks)
Backlogs: No current backlogs
Year: Final-year and recent grads
Skills they actually filter
Primary: Aptitude, easy coding, spoken English
Languages: Java, Python, SQL
Domain: Travel / BFSI / insurance curiosity helps
Exam filter: Coforge Assessment (+ communication on some drives)
| Item | Typical expectation | Reality check |
|---|---|---|
| Graduation | 55% official / 60% or 6.0 on many campuses | Mailer wins |
| 10th & 12th | 55%+ throughout in official fresher text | Keep scanned marksheets |
| Degree | B.E./B.Tech/MCA/M.Tech | Service-desk has a different stream |
| Backlogs | None current | Clear before joining |
| Coding | Java or Python + SQL | One language you can finish |
| English | Separate communication round on some drives | Practice speaking, not only MCQs |
Coforge is a volume campus hirer with a real English filter. Clearing CGPA only gets you into the funnel. Treat communication + aptitude as the cut, then technical as the offer conversation.
Download 2026 Coforge placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Coforge does not publish a permanent official paper set. “Previous year papers” on this site are pattern trainers - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Communication | Listening, speaking, grammar speed |
| Online assessment | Aptitude, CS/SQL MCQs, one coding problem |
| Technical | OOP, DBMS, projects, easy DSA |
| HR | Location, bond, CTC, joining |
Think of papers as simulators for 90-minute stamina. Coforge reuses themes (time-work, DI, OOP MCQs, fractional knapsack-style coding) more than exact clones.
| Theme you saw in a set | What to drill next | Why Coforge asks it |
|---|---|---|
| Time-work / percentages | Speed without silly arithmetic | Volume aptitude |
| DI tables | 45-second skip rule | Same |
| OOP MCQs | Interface vs abstract, overloading | Technical section + interview |
| SQL | Joins, GROUP BY | MCQ + tech |
| Fractional knapsack / greedy | When greedy fails | 25-minute coding window |
| Sorting / searching | Narrate in interview | Tech round |
2024 PDFs often drill fractional knapsack. Own greedy by ratio and knowing when 0-1 knapsack needs DP instead. That transfers.
Coforge hires freshers through campus cells, careers.coforge.com, and referrals. After eligibility, the shape is classic Indian IT services: English + aptitude, then a fundamentals interview, then HR on location and (sometimes) bond.
Campus recruitment
Primary path - PPT, communication and/or OA, then interviews. Locations listed as “all Coforge locations” on some mailers.
Online applications
careers.coforge.com fresher page. Follow the assessment mail for platform (Mercer and others appear).
Referrals
Help visibility. You still need aptitude accuracy and a complete coding submit.
College list vs 55%/60% rules, 10th/12th, no current backlogs. This is a gate.
2024 GFG: listening, speaking, grammar MCQs before the aptitude test. Mercer blogs: reading (many items), listening, grammar plus the cognitive test.
Pass habit: Speak in complete sentences. Do not memorise a TED talk. If you freeze, restart the sentence - that is better than silence.
| Section (2024 campus example) | Time | What shows up | Pass habit |
|---|---|---|---|
| Aptitude | ~30 min | Quant, reasoning, DI - easy-moderate | Skip after 45 seconds |
| Technical MCQs | ~35 min | Programming, OOP, OS, CN, SQL | Eliminate options |
| Coding | ~25 min | 1 problem (knapsack/greedy cited) | Fully passing > clever incomplete |
Languages: Java, Python, SQL (SQL more in MCQ/interview).
Student tip: 25 minutes is not a Codeforces round. Read constraints, implement the greedy or simple DP you know, test samples.
Deeper OA notes: Coforge Online Assessment.
A 30-minute aptitude section that “felt easy” in a 2024 GFG note still has a cutoff. The fail mode is slow arithmetic and one DI table that ate 8 minutes. Drill:
You do not need CAT 99. You need no silly blanks and a coding submit.
35 minutes is enough to overthink. Typical mix: output of a small Java/C snippet, OOP definitions, OS process vs thread, HTTP port, a JOIN question. If you do not know, eliminate two options and move. This is not the round to invent a new memory model.
Projects first, then DBMS, OOP, sorting, one programming question. Interviewers are checking whether you can join a delivery team in travel or insurance, not whether you invented a compiler.
Example narration (sorting): “I’ll use merge sort if n is large and we need stability; otherwise language sort.” I’ll state O(n log n) and an example of when bubble sort is a joke answer.”
Location flexibility (Noida vs Bengaluru), night-shift honesty if asked, bond/service agreement if the drive has one, CTC around ₹4.5-7 LPA, joining vs exams. Some batches run HR the same day as technical; some run HR first in a classroom while names are called.
| # | Round | Duration | What they check |
|---|---|---|---|
| 0 | Communication | Drive-dependent | English you can use at work |
| 1 | Online test | ~90 min common | Aptitude + MCQ + 1 coding |
| 2 | Technical | 30-45 min | Fundamentals + projects |
| 3 | HR | 15-20 min | Fit, location, bond, CTC |
| Phase | Typical duration | Notes |
|---|---|---|
| Register / PPT | Days | Read bond slide if any |
| Communication + OA | 1-2 days or split weeks | Mercer from home on some drives |
| OA → interview | Days to several weeks | One blog: April test, June campus interviews |
| Offer / paperwork | Days after HR | Written letter + any agreement |
| End to end | ~2-8 weeks often | Services calendars slip |
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude | Skip rules | Daily mock quiz |
| Tech MCQs | OOP, SQL, OS | 20 flash cards |
| Coding | One complete easy-medium | 25-minute timer |
| Speaking | Clear, short answers | Record intro twice |
| HR | Bond, city, CTC | Two STAR + one honest location line |
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 Coforge 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 Coforge 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): Official Coforge fresher careers text commonly cites 55% throughout 10th, 12th, and degree/diploma with no current backlogs for B.E./B.Tech campus hiring. Many campus mailers still print 60% or 6.0 CGPA. Degrees: B.E./B.Tech/MCA/M.Tech (and some non-engineering service-desk tracks). Always verify careers.coforge.com or your placement email - the mailer wins.
What you are training for: Typical 2024-2026 campus shape: a communication assessment (listening, speaking, grammar) on some drives → Online Assessment (aptitude + technical MCQs + 1 coding, often ~90 minutes) → Technical interview → HR. Some batches run HR before or on the same day as technical. Platforms like Mercer appear in write-ups. End-to-end often a few weeks; one drive had weeks between OA and on-campus interviews.
Short version of the prep split: Split time roughly: 35% aptitude+verbal speed, 25% easy coding, 20% CS/OOP/SQL MCQs, 10% spoken English if a communication round exists, 10% HR including bond/location. Languages: Java, Python, SQL. Do not skip speaking practice if Mercer/communication is on the mailer.
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Coforge 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 Coforge 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 Coforge 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 Coforge?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. 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 Coforge-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 Coforge story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Coforge papers on three different days, then interview prep on the leftovers.
Figures are candidate-reported India bands (as of August 2026).
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer / GET fresher | ₹4.5-7 LPA | Primary band for this hub |
| Associate / support-adjacent | Often lower | Different JD |
| Service agreement | Drive-specific | Read the letter |
Confirm base vs variable and any bond on the written offer.
Know ₹4.5-7 LPA. Ask split and joining date. Do not negotiate like a product-company blog.
Keep every email.
Five problems, five sittings, until submit-and-test is automatic.
You are not sitting IELTS. You are proving you can join a stand-up with a client-facing lead.
Listening: answer the question asked, not a neighbouring one. One clause is enough.
Speaking: 45-60 seconds on “introduce yourself” - name, college, one project, one skill, stop. Fillers (“basically, like, actually”) count against you if they bury the noun.
Grammar MCQs: subject-verb, preposition, tense. Speed. Do not invent a third tense.
Practice: record on your phone in a noisy hostel corridor once. If you can stay clear there, Mercer at home is easy. If you only practise in silence, the real mic will surprise you.
| Minute | Move |
|---|---|
| 0-3 | Read twice. Write one example. Name the pattern (greedy / search / two pointers). |
| 3-18 | Code the happy path. No fancy class hierarchy. |
| 18-23 | Samples + n=1 + empty. |
| 23-25 | Submit. Do not start a second algorithm. |
Fractional knapsack in 2024 was a gift if you knew value/weight sort. If your drive’s one question is a simple DP, the same clock applies. An un-submitted 90% solution is a 0.
From 2024-style write-ups, expect a mix like:
Prepare short answers. A 10-minute lecture on blockchain in your library app is how you run out of time before DBMS.
Memorising GDS codes is wasted time. Saying “I saw travel in the PPT and I am fine working on booking workflows” is enough.
10th marksheet, 12th marksheet, all semester marksheets, ID, passport-size photo if the mailer asks, resume one page, and a printout of the bond/eligibility email. Services drives still fail people on a missing 12th PDF. That is a silly way to exit after clearing OA.
| Day | 15-minute drill |
|---|---|
| 1 | Record intro. Transcribe. Cut fillers. Re-record. |
| 2 | Listen to a 1-minute clip (news), speak the gist in 20 seconds. |
| 3 | 20 grammar MCQs (tense, preposition). |
| 4 | Project in 40 seconds: problem, your part, one number. |
| 5 | “Why Coforge?” in 30 seconds. |
| 6 | Full mock: intro + project + why, no notes. |
| 7 | Light replay of the best take. Sleep. |
This will not make you a debater. It will stop a blank stare on Mercer speaking items.
Give yourself: aptitude 0-30, MCQ 0-35, coding 0 or 25 (submitted and sample-correct = 25, else 0). If coding is 0, the mock failed even if aptitude was 28. That is how volume hiring works. Fix coding first, then shave aptitude time.
If any answer is “I’ll see,” you are not ready for HR.
You do not need a 400-page CAT book. For a 30-minute Coforge-style section, spend time in this order:
Log every mock: which of the five ate the clock. That log is the prep plan. Downloading three new apps is not.
Interviewer: “We do airline systems.” Have you thought about what happens when a flight is delayed?”
Good: “Inventory and passenger rebooking - I’d expect a workflow with statuses, not a single boolean.” I have not built one; I would start with booking, inventory, and a delay event.”
Bad: “I would use Kafka and microservices.”
Same pattern for insurance claims. Statuses and audit beat buzzwords.
Saturday 10:00 - communication: 15 minutes speaking + 20 grammar.
Saturday 11:00 - 90-minute OA split.
Saturday 13:00 - review only the misses.
Sunday 11:00 - 30-minute technical oral with a friend (OOP + SQL + project).
Sunday 12:00 - HR answers aloud, including bond.
Two weekends of that beat twelve nights of random YouTube.
Given items with value and weight, you may take fractions, maximise value for capacity W.
Write this once without an editor. Then code it under 25 minutes. If your 2026 prompt is binary search or two pointers instead, the same “name the pattern in 3 minutes” habit still wins.
SELECT student_id, AVG(marks)FROM resultsGROUP BY student_idHAVING AVG(marks) > 80;Explain WHERE vs HAVING. Write a JOIN of students and results. That is enough for most Coforge technicals. If you cannot, stop watching system-design YouTube.
A services drive can take a large batch from one college. That is not a participation trophy. Communication + OA still delete a chunk. Technical still deletes people who cannot explain their own project. Your job is to be easy to say yes to: complete coding, clear English, documents ready, bond answer ready. Fancy side projects help; they do not replace those four.
Three numbers show up in the wild:
Use the mailer in your inbox. If none yet, assume you need 60% and clean 10th/12th. Do not argue with the placement cell using a screenshot of 55% if their notice says 65%. The college often pre-filters the list before Coforge sees it.
The fresher careers page also describes a non-B.Tech service-desk path. Different English bar, different coding expectation, different CTC. If you are a B.Tech targeting SE/GET, do not prepare as if the desk stream is your offer. If you are BCA on a mixed mailer, read which designation is printed.
Services interviewers hear twenty “e-commerce clones” a day. Structure:
If you cannot do that without looking at the laptop, rewrite the resume bullet until you can. Coforge technicals are short; a rambling architecture tour wastes the DBMS questions you could have scored.
Even when there is a separate communication round, OA verbal still appears. Read the question first. For RC, match the option to the passage, not to your opinion. Para-jumbles: find the opener with the full noun, not “this/these.” Ten minutes of this the morning of the test is enough if you have been practising; zero minutes is how people throw away an otherwise easy paper.
The official fresher page points campus queries to campus@coforge.com. That is for college/process questions, not “please share OA dumps.” If your drive is off-campus via the careers form, use the portal status, not a random Telegram admin. Paying for a “guaranteed Coforge slot” is how people get scammed.
Keep the same email thread from PPT to offer. Verbal “you’re selected” in a classroom is not an offer letter. Wait for the PDF, read location and any service agreement, then resign other holds.
If two services offers arrive the same week, compare site, bond, and joining date before CTC ego. A ₹5 LPA Noida seat you will actually join beats a ₹6.5 rumour with a clause you cannot live with. Keep 10th and 12th scans in the same folder as the offer PDF. A missing 12th marksheet is a silly way to stall joining after you cleared Mercer. Name, percentages, and dates must match every form you already submitted.
Typical path: (communication round on some drives) → online assessment (aptitude + technical MCQs + 1 coding) → technical interview → HR. Platforms and order vary. Confirm the mailer. End-to-end often a few weeks.
Most fresher loops report 3-4 stages. Communication can be elimination before OA. Count the invite.
Yes. Free Coforge placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the paper archive.
One 2024 campus split: 30 min aptitude, 35 min technical MCQs, 25 min one coding. Other drives use Mercer with cognitive + technical + coding + spoken English. Verify your invite.
Official fresher language: 55% throughout 10th, 12th, and degree, no current backlogs. Many campus mailers print 60% or 6.0 CGPA. Your notice overrides this page.
Candidate-reported CTC often lands around ₹4.5-7 LPA (as of August 2026) for SE/GET freshers. The written offer is the only number that matters.
Some campus drives have reported a service agreement (one public note: 2 years, about ₹1.5 lakh). Drive-specific. Read the PPT and the offer. Ask HR in writing.
Split time roughly 35% aptitude, 25% easy coding, 20% CS/SQL MCQs, 10% speaking, 10% HR. Details: preparation guide.
Java or Python for coding; SQL in MCQs and interviews. Confirm on the invite.
Yes on some campuses (listening, speaking, grammar) before or beside aptitude. Prepare to speak even if your mailer only lists OA.
Finish the one coding question. Practice speaking out loud. Decide bond/location before HR. Know the ₹4.5-7 LPA band.
Start with Coforge interview experience on this site, then GFG 2024 campus notes and recent blogs. Use them as maps, not scripts.
Similar sport: volume aptitude plus a short coding gate. Coforge’s coding window can be shorter (~25 min). Communication as a separate elimination is the extra twist on some drives.
No GDS certification required. A one-line awareness that Coforge is strong in travel, insurance, and BFSI is enough for HR.
Some mailers include BCA/BSc. The official fresher page also describes a non-B.Tech service-desk stream with its own rules. Read the JD; do not assume every SE drive is open.
All three run aptitude-plus-coding gates. Nagarro often feels more coding-forward. Hexaware is similar volume hiring. Coforge’s extra twist on some campuses is a communication-first round and a travel/insurance story in the PPT. Prep aptitude and one complete coding question for all; add speaking drills if Coforge is on your list.
Steal: 90-minute split; communication as a real filter; bond decided before HR; one complete coding submit.
Ignore: memorising fractional knapsack numbers from a 2024 GFG post; quoting product CTC; skipping 12th marksheet because your B.Tech CGPA is high.
If you only do three things: time one 90-minute mock, record a 60-second intro, and read any bond slide twice.
Communication round first (listening, speaking, grammar). OA later: aptitude 30 / MCQs 35 / coding 25 (fractional knapsack). Interview same day: projects, DBMS, OOP, sorting. Takeaway: English is not optional; the coding window is short.
A student blog described Mercer (camera on) with cognitive, technical MCQs, one coding, plus spoken sections; shortlist weeks later; physical HR then technical; mailer listed 2-year bond ~₹1.5 lakh and 65% throughout for that drive. Takeaway: calendars slip; read the cutoff on your mailer (65% ≠ 55%).
Helped: complete coding; calm speech; honest location; documents ready.
Hurt: blank coding; mumbled communication; surprise at bond; 12th percentage below printed rule.
Application in April, remote Mercer with camera, shortlist mail in May, campus HR+technical in June. Students who “took a break” after OA forgot SQL and mumbled intros. Takeaway: keep a 30-minute weekly maintenance loop (one aptitude set, one coding, one recorded intro) until the interview date, even if the calendar looks empty.
PPT mentioned a 2-year agreement; student said yes in HR then tried to back out after another offer. That burns the college’s relationship and your reference. Decide before the cabin. Asking “please confirm the amount and tenure in the letter” is allowed. Pretending you never heard the slide is not.
All three are mid-tier services with aptitude-plus-coding gates. Nagarro often feels more coding-forward. Hexaware similar volume hiring. Coforge’s twist is communication-first on some campuses and a travel/insurance story in the PPT. Prep aptitude+one coding for all; add speaking drills if Coforge is on your list.
Mercer at home, interviews weeks later: keep a 30-minute weekly maintenance loop (one aptitude set, one coding, one recorded intro) until the interview date. Students who “took a break” after OA forgot SQL and mumbled intros.
Bond surprise: decide yes/no before the cabin. Asking HR to confirm amount and tenure in the letter is professional. Discovering the clause after you said yes is how people panic-sign.
Missing 12th marksheet: a silly way to stall joining after you cleared Mercer. Name, percentages, and dates must match every form.
More narratives: Coforge interview experience.