The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment | ~90-120 min | Quant, verbal, technical MCQs and coding |
| Technical Interview | ~30-45 min | DSA, DBMS, OOP, networking and projects |
| HR Interview | ~20-30 min | Communication, fit and logistics |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online Assessment
~90-120 minA multi-section test: quantitative aptitude, English/verbal, a technical section (Unix, SQL/PL-SQL, OS, C output) and 2-3 coding problems. The technical section reflects Amdocs' stack, so brush up on Unix and SQL, not just DSA.
- C output-prediction snippets
- Unix command and shell concept MCQs
- SQL/PL-SQL query questions
- 2-3 easy-medium coding problems
- Quant and verbal MCQs
- Revise C output questions and pointers
- Practice SQL/PL-SQL and basic Unix commands
- Solve easy-medium coding problems
- Take a timed multi-section mock
- Ignoring Unix/SQL and only doing DSA
- Slipping on C output/pointer subtleties
- Poor time split across many sections
- Correct code plus strong technical MCQs
- Comfort with Unix/SQL
- Balanced section performance
Technical Interview
~30-45 minA fundamentals round on data structures, DBMS, networks, OOP and your chosen language, plus resume projects. Expect to explain approaches, write small code, and answer SQL and Unix questions given the stack.
- Explain a data structure and use-case
- OOP pillars with examples
- SQL query and DBMS concepts
- A Unix/OS concept
- Project walkthrough and contribution
- Revise DSA, DBMS, OOP and networking to spoken depth
- Practice SQL and a few Unix commands
- Rehearse resume projects
- Prepare small code you can write on the spot
- Bluffing on Unix/SQL
- Definitions without examples
- Weak project ownership
- Clear fundamentals
- Stack comfort (SQL/Unix)
- Project ownership
HR Interview
~20-30 minA conversational round on motivation, teamwork, career goals, and logistics like relocation and shifts. Communication and genuine interest matter most.
- Why Amdocs and the telecom-software domain
- A teamwork or challenge story
- Career goals
- Relocation and shift flexibility
- Strengths and a growth area
- Research Amdocs' telecom/BSS-OSS domain
- Prepare STAR behavioral stories
- Rehearse an authentic 'Why Amdocs'
- Prepare honest logistics answers
- No domain awareness
- Generic motivation
- Hesitation on shifts/relocation
- Clear communication
- Domain interest
- Flexibility
What to master
- C output and pointers
- Unix commands and concepts
- SQL and PL-SQL
- Data structures and algorithms
- DBMS and OOP
- Networking basics
- Resume project depth
- STAR behavioral storytelling
Eligibility
Typically 60%+ across academics with no active backlogs; CSE/IT/ECE and allied branches. Software Engineer fresher packages often around 6-8 LPA. Confirm exact cutoffs per drive.
Amdocs salary & compensation (2026)
Telecom software product firm (GCC-like); pay above pure services but below top product GCCs like SAP/Oracle.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| Software Engineer / Trainee | 0–2 yr | ₹5–9 LPA | — | Entry product/support engineering. |
| Software Engineer | 2–5 yr | ₹10–18 LPA | — | Core BSS/OSS product work. |
| Senior Software Engineer | 5–9 yr | ₹19–32 LPA | — | Component ownership. |
| Team Lead / Specialist | 9–13 yr | ₹34–52 LPA | — | Technical or people leadership. |
| Architect / Manager | 13+ yr | ₹55–85 LPA | — | Product architecture or delivery ownership. |
How the package is structured
- Base-heavy with modest bonus; limited RSU except senior roles.
- Cloud/microservices modernization skills pay a premium.
- Telecom-domain (charging, billing, 5G) expertise accelerates growth.
- US hiring is limited; India tracks stay local.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1-3: C output, pointers and easy-medium coding
- Days 4-5: Unix commands and SQL/PL-SQL practice
- Days 6-8: DSA, DBMS and OOP revision
- Days 9-10: quant and verbal aptitude with a mock
- Days 11-12: rehearse resume projects
- Days 13-14: STAR answers plus a mock technical and HR round
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
Why does Amdocs test Unix and SQL?
Its telecom-software (BSS/OSS) stack relies on Unix and databases, so the technical MCQs and interview include Unix commands and SQL/PL-SQL alongside standard DSA.
How hard is the coding?
Easy-to-medium, typically 2-3 problems in the online test. Correctness and covering edge cases matter.
How many rounds are there?
Usually 3-4: online test, technical interview and HR, sometimes with an extra technical or managerial round.
Does Amdocs ask C output questions?
Yes, C output-prediction and pointer questions are common in the technical MCQ section.
Is there relocation or shift work?
It can apply depending on the project, so be ready to answer honestly in the HR round.
What language should I use for coding?
Use the language you are strongest in; C/C++, Java and Python are commonly supported.