Academic snapshot
Marks: 60% or 6.0 CGPA throughout 10th, 12th, graduation
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT)
Backlogs: None active at selection
Year: Final-year and recent grads (within ~2 years)
Amdocs is a global software company known for telecom business support systems including billing, CRM, and network management software. India delivery centers in Pune and Gurugram are major hiring hubs for engineers building products for telecom operators worldwide.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Amdocs is a volume campus hirer with a telecom flavour. The printed floor is usually 60% throughout. Coding and sectionals still decide who sees an interviewer.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, college % list, possible GD | Aptitude + one coding submit |
| Careers / Naukri | Resume volume | Still expect a timed OA |
| Referral | Visibility | You still sit every elimination round |
Off-campus does not mean easier percentages. It often means more applicants who skip verbal and die on a sectional.
Is 6.0 CGPA enough? It matches the commonly reported floor. A 6.2 who finishes aptitude sections and one coding problem beats an 8.4 who leaves technical MCQs empty. A 7.5 B.Tech with 58% in 12th is how people get dropped after the form check.
Branches: CS/IT dominate. ECE/EEE and related streams appear on many notices.
Gaps and backlogs: Active backlogs are a hard blocker on most drives. About 2 years education gap shows up in student tables.
What helps the resume screen: One project you can defend, readable English. BSS buzzwords without a billing sentence you can say aloud do not help. See certifications after aptitude and one language.
Academic snapshot
Marks: 60% or 6.0 CGPA throughout 10th, 12th, graduation
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT)
Backlogs: None active at selection
Year: Final-year and recent grads (within ~2 years)
Skills they actually filter
Written: Quant, logic, verbal, CS MCQs
Coding: 1-2 problems; at least one must usually pass
Interview: OOP, DBMS, project, BSS examples
Languages: C, C++, Java, Python
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 60% or 6.0 | Mailer wins |
| 10th & 12th | Same throughout rule | Keep scans |
| Branches | CS/IT/ECE/EEE and listed cousins | Confirm drive |
| Backlogs | None active | Clear before joining |
| Gap | Often max ~2 years | Explain honestly |
Good fit: You can finish a 90-minute mixed paper, you will write one complete program, and you can map OOP/SQL to a prepaid vs postpaid example without a TED talk.
Harder path: You only practised LeetCode hard and skipped percentages; you leave verbal empty; you treat GD as a debate club; you quote 18 LPA in HR.
ECE/EEE reality: Listed drives welcome circuital branches. The OA still wants sectional aptitude and one passing program. A networks course helps the TCP/CDR sentence; it does not replace percentages.
Download 2026 Amdocs placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Amdocs does not publish one permanent official paper set. Papers on this site are pattern trainers.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed 90 min: aptitude, CS MCQs, 1-2 coding |
| Technical | Live coding + OOP/DBMS + BSS-flavoured examples |
| GD (some campuses) | Structured 60-second takes |
| HR | Why Amdocs, location, CTC band |
| Theme | Drill next | Why Amdocs asks it |
|---|---|---|
| Percentages / TSD | Speed arithmetic | Volume aptitude |
| Series / syllogism | 45-second skip | Logic sectional |
| Normalisation / 3NF | Billing-table example | BSS MCQs and tech |
| Polymorphism | calculateBill() prepaid vs postpaid |
OOP with domain |
| Two-sum / palindrome | Complete submit | OA coding wrappers |
Worked flavour (not a leaked paper): mark-up 40% then 25% discount → 5% profit if CP is 100. Train 150m + platform 250m in 20s → 72 km/h. Series 3, 7, 15, 31, 63 → 127. CDR two-sum and subscriber-id palindrome show up as wrappers, not as a reason to skip generic DSA.
If a dump site sells you “exact Amdocs 2026 paper,” it is almost certainly a recycled aptitude set with a telecom sticker. Timed mocks on this site plus one language beat a paid ZIP. Interviewers still ask you to write the code, not recite the ZIP.
Amdocs hires freshers through campus cells, careers / job portals, and referrals. After eligibility, the shape is services-plus-telecom: mixed OA, technical, HR, sometimes GD.
Campus recruitment
College placement cells. PPT, then OA and interviews. Listen for GD language.
Online applications
amdocs.com careers or listed portals. Follow the invite for platform and duration.
Referrals
Improve screen odds. You still need sectional aptitude and one passing program.
60% / 6.0 throughout when printed, listed degrees, no active backlogs. Gate.
Candidate reports commonly describe ~90 minutes and about 25-30 items.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Aptitude | 15-18 | ~45 min | Quant, logic, verbal |
| Technical | 5-7 | ~20 min | Programming, DS, DBMS |
| Coding | 1-2 | ~25 min | Arrays, strings, basic algorithms |
Pass habit: 45-second skip on seating puzzles. Bank easy quant. Leave time for one complete passing program. Student notes often cite sectional cutoffs and overall ~60-65%. Roughly 25-30% of a large OA batch advancing is a common rumour, not a promise. No negative marking is often claimed; still read the mailer.
Virtual or onsite. Easy-medium live code, OOP, DBMS, OS/CN, project. BSS flavour: billing tables, CRM, prepaid vs postpaid, why TCP for CDRs. Map the fundamental first, then the telecom sentence.
2024 GFG: virtual GD on generative AI, 5-6 judges, after technical. Structure: define, one pro, one risk, one close. Do not interrupt. Do not stay silent.
Why Amdocs, location, joining vs finals, integrity. Know the ₹5-7 LPA SE band.
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / screen | 3-5 days | Eligibility check |
| OA | 1 sitting | Same week or later |
| Shortlist | 2-3 days | 2024 note: 13/85 to tech |
| Technical (+ GD) | 1 day | Virtual common |
| HR | Same day or next | Short |
| Offer | 3-5 days | Written letter wins |
| End to end | ~2-3 weeks campus often | Off-campus can stretch |
Saturday 10:00: 90-minute mixed OA.
Saturday 12:00: error log + rewrite one program.
Saturday 16:00: 15 BSS-mapped one-liners (3NF, polymorphism, TCP vs UDP).
Sunday 11:00: 20-minute technical oral.
Sunday 11:30: 60-second GD take if your college named it.
Sunday 12:00: HR including CTC band.
calculateBill() interface, prepaid vs postpaid implementations.That is enough fresher depth. A 40-slide BSS architecture is how people waste a week.
10th, 12th, all semesters, ID, resume one page. Throughout 60% means the 12th PDF matters.
Campus: PPT → OA → shortlist (13/85 in one 2024 note) → Teams technical → optional GD → HR. Off-campus: portal application, then a similar OA. Screenshot the invite. If GD is not named, do not invent a debate club. If it is named, do not skip it because a blog said “Amdocs is only three rounds.”
List three slow quant types, rewrite the coding solution once, say the four BSS sentences once. Then stop. The technical is usually a CS grill plus a project, not a new domain textbook.
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.
Week calendars live on the preparation guide. This H2 is the focus split.
| Bucket | Share | What “done” looks like |
|---|---|---|
| Timed aptitude | ~40% | Full 90-minute mocks |
| One complete coding submit | ~30% | Arrays/strings with tests |
| CS + BSS mapping | ~20% | Four examples you can say in 20 seconds each |
| Project + HR (+ GD) | ~10% | Metric story + 60-second GD take |
If you already clear aptitude and fail coding, invert 40/30 for two weeks. If you code fine and blank on 3NF, add the cheat-sheet daily without quitting mocks.
Week A: three 90-minute mixed OAs; 45-second skip rule on puzzles; one complete coding submit per mock.
Week B: four BSS sentences daily; one live easy-medium code; one 60-second GD take; HR including ₹5-7 LPA and city.
If you have a month, add SQL joins and one project metric story. Do not add a telecom certification binge unless aptitude and coding are already stable.
In HR, one sentence is enough: telecom BSS and billing systems, India engineering, you want to write reliable customer-facing backends, you will relocate. Then a project metric. “I researched your Q3 revenue” is optional. “I will only do GenAI” is a bad answer. “I will learn the account stack and I already write Java/Python” is the SE answer.
The GFG ASE note called the Teams round a wide CS grill. Translate that to a checklist you can finish in 45 minutes of prep per day for a week:
If you only revise “telecom architecture,” you will blank on a mutex. If you only revise LeetCode, you will blank on 3NF. Amdocs wants both at fresher depth.
Student notes keep repeating sectional plus overall. That means:
Set a watch. At minute 50, if coding is untouched, stop the puzzle. At minute 75, if coding is still untouched, you are choosing to fail. One passing program plus average aptitude beats a hero graph and an empty RC.
Amdocs India staffing follows accounts. The letter may name a city you did not dream about. Ask HR. If you cannot go, say so. Day-one no-shows burn the next campus cycle. Hybrid language is account-specific; do not assume WFH because a 2021 blog said so.
Amdocs can take a batch and still drop 72 of 85 before technical (2024 note). That is not personal. It is a mixed OA plus a CS grill plus, sometimes, a GD. Be easy to say yes to: complete written, one passing program, a billing example, a calm GD, documents ready. Keep a backup services process live until the PDF lands. Name and percentages must match.
If Amdocs, Infosys, and TCS all land the same week, compare city, training story, and the actual letter, not LinkedIn prestige. A ₹5-7 LPA SE you will join beats a rumour 9 LPA with a clause you cannot live with.
If a Amdocs 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 Amdocs sits around ₹5-7 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): Candidate-reported campus floor is often 60% or 6.0 CGPA across 10th, 12th, and graduation; B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT); final-year or recent grads (within about 2 years); no active backlogs; max about 2 years education gap; full-time degrees. Your drive notice overrides this page.
What you are training for: Typical fresher loop: Online Assessment (~90 min, aptitude + technical MCQs + 1-2 coding) → Technical interview (~45 min) → HR (~30 min). Some campuses add a group discussion after technical (one 2024 GFG ASE note: 13 of ~85 reached tech, then a generative-AI GD, then HR). About 2-3 weeks on many campus batches.
Short version of the prep split: Split time roughly 40% timed aptitude, 30% one complete coding submit, 20% CS + telecom/BSS vocabulary, 10% project + HR. Clear sectional cutoffs. Languages: C, C++, Java, Python. Full plan: /amdocs/preparation-guide/.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Amdocs 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 Amdocs 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 Amdocs 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 Amdocs?” 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 Amdocs-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 Amdocs story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Amdocs papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Amdocs papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Amdocs-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Amdocs 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 Amdocs. 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.
Figures below are candidate-reported India bands (as of August 2026).
| Track | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer (fresher) | ₹5-7 LPA | Primary band for this hub |
| Early associate / later SE | ₹6-10 LPA | Experience and title vary |
| QA (entry) | ₹3.5-4.5 LPA | Testing basics help |
| Business analyst (entry) | ₹5-7 LPA | Not the default SE letter |
Confirm base vs variable on the written offer.
Health insurance, PF/gratuity, learning after joining (manager-dependent), meal/transport on some letters. Hybrid varies by account. Ask HR.
Know ₹5-7 LPA SE. Ask how the package splits. One calm question beats a 12 LPA demand on a services letter.
Aptitude plus one coding submit
90-minute mixed OA remains the volume filter. Empty sectionals still kill strong coders.
BSS flavour in technical
Billing, CRM, prepaid vs postpaid examples keep showing up. Fundamentals first.
GD is campus-dependent
2024 GFG: generative AI GD after technical. Practise if named; do not assume every drive.
₹5-7 LPA SE band
Still the commonly cited fresher story. Confirm the letter.
Net for 2026: do not wait for Amdocs to become a coding-only product company. Double down on timed aptitude, one complete program, and four BSS sentences.
Some services letters hide training months and service agreements. Ask HR, once, without drama:
Write the answers down. If they will not put them in the letter, that is also an answer. Compare with Infosys/TCS the same way so you are not comparing a blog midpoint to a real PDF.
If Amdocs and a NQT-style drive overlap, do not invent a new language. Same C/Java/Python, same skip rules, different HR story (BSS vs “largest IT services”). Aptitude muscle transfers. SuperCoder-style extras at other firms do not replace Amdocs sectionals. Keep the watch.
Print 10th and 12th tonight if the drive is this week. Throughout 60% is a document problem as much as a marks problem. A missing scan after a 13/85 technical shortlist is a silly way to exit. Name, percentages, and dates must match the form you already submitted. Keep the scans on your phone and in a drive folder, not on a hostel pen drive you will lose at 8 a.m. Screenshot the OA invite too, so sectional rules are not a rumour from a 2023 Telegram screenshot. Your mailer is the only blueprint that counts on test day. Trust that over any blog table on test morning.
Typical path: OA (~90 min) → Technical (~45 min) → HR (~30 min). Some campuses add GD. About 2-3 weeks on many batches.
Most fresher loops report three after resume. GD is extra on some campuses. Count the mailer.
Often ~90 minutes, ~25-30 items: aptitude, technical MCQs, 1-2 coding. Details: online assessment.
Sometimes. A 2024 GFG ASE note describes a generative-AI GD after technical. If named, practise a 60-second structured take.
Commonly 60% or 6.0 CGPA throughout; listed computing degrees; no active backlogs; gap often ≤ ~2 years. Your notice wins.
Candidate-reported SE often ₹5-7 LPA (as of August 2026). The written offer is the only number that matters.
Roughly 40% timed aptitude, 30% one complete coding submit, 20% CS + BSS mapping, 10% project/HR. Guide: preparation guide.
C, C++, Java, Python on most invites. Do not switch the week of the drive.
Often as flavour on top of OOP/SQL/networking. Map fundamentals to billing/CRM. Do not memorise a BSS textbook.
Share aptitude+coding prep. Amdocs leans telecom BSS and a ₹5-7 LPA SE band with occasional GD. Customise HR and examples.
One complete coding submit. Honour sectionals. Four BSS sentences. GD structure if named.
Amdocs interview experience and the 2024 GFG ASE note in the stories section.
Timed aptitude + one language + one project beat certificate stacks. See certifications.
Only after one is fully passing. Student notes treat one complete submit as the line. A second partial is extra, not a substitute.
After assessments, “out of almost 85 students, only 13 students got invited for the technical interview” on MS Teams with a wide CS grill. Seven advanced to a virtual GD on generative AI with a 5-6 person panel, then a short HR chat. Five final selects. Source: GeeksforGeeks Amdocs ASE.
Takeaway: technical is a real cut. GD is not a formality when it exists. Funnel math is harsh; one complete OA coding submit still matters.
What helped: full timed mocks; one passing program; 3NF/polymorphism with a billing sentence; calm GD; knowing ₹5-7 LPA.
What hurt: empty verbal; two partial codes; BSS jargon without SQL; dominating GD; product-company CTC in HR.
The 2024 generative-AI GD is a useful template even if your topic is different:
Do not interrupt. Do not stay silent for eight minutes. Do not give a product-launch speech. A 5-6 person panel is watching whether you can work in a group, not whether you win a debate trophy.
Aptitude: mark-up then discount (CP 100, +40%, −25% → 5% profit). Train + platform TSD. ×2+1 series (3, 7, 15, 31, 63 → 127).
Technical: 3NF on a billing table; calculateBill() polymorphism for prepaid vs postpaid; TCP for CDR pipes.
Coding wrappers: two call durations that sum to a threshold (hash two-sum); subscriber id palindrome ignoring case and spaces.
If you can do those in a timed sitting, you are practising the pattern, not a Telegram dump.
13 of 85 to technical, 7 to GD, 5 offers (one 2024 campus). That is a reminder to finish the OA coding submit and to treat GD as a ranked round when it exists. It is not a reason to skip applying. Volume services always have harsh funnels.
More narratives: Amdocs interview experience.