DXC Technology Fresher Hiring 2026: Test Pattern, Packages and the Work Nobody Describes
Updated August 2026 · Figures are indicative — always confirm on DXC Technology's official careers page
DXC Technology is a large global IT services company formed in 2017 from the merger of Computer Sciences Corporation with the enterprise services business of Hewlett Packard Enterprise, and that lineage explains more about fresher hiring here than any careers page will. Both parent businesses were built on running other companies' technology estates — infrastructure, data centres, long-lived enterprise applications, insurance and banking systems — rather than on building new products. The company has since moved substantially into cloud, security and application modernisation work, but a large part of what it does is still keep critical systems running for clients who cannot afford them to stop.
That matters to you because it shapes where freshers actually land. Students apply expecting a development role and a meaningful share of the intake across this part of the industry goes into managed services, application support and infrastructure operations — work that is real engineering but is structured around tickets, incidents, change processes and service levels rather than around feature releases. Some of it runs in rotational shifts, because the clients are in other time zones. None of that is a reason to avoid the employer; it is a reason to walk in knowing what you are applying to, ask which track your role sits in, and stop being surprised by an answer the industry has been giving for twenty years.
The company has a substantial India delivery presence across several cities, and hires freshers through both campus drives and off-campus routes with the usual variation between them. Everything drive-specific below — sections, weightings, eligibility, package band — changes by cycle, role family and location, so treat this page as orientation and confirm against the posting you are sitting. One more thing worth knowing upfront: assessments here often carry a genuine English or communication component, which is not decoration at a company whose engineers talk to client stakeholders daily.
Roles & packages
| Role | Package | How to qualify |
|---|---|---|
| Associate Professional — Software Engineering | Indicative ₹3.5–4.5 LPA, varies by cycle and route | The development-oriented fresher entry point — application development and maintenance on client engagements |
| Associate Professional — Application / Production Support | Indicative ₹3–4 LPA | Keeping existing client applications running: incidents, defect fixes, releases; often shift-based and a large share of intake |
| Infrastructure and cloud operations | Indicative ₹3–4.5 LPA | Servers, networks, platform and cloud operations under ITIL-style processes; certification-driven progression |
| Service desk / technical support | Indicative ₹2.5–3.5 LPA | The most communication-weighted route and the easiest to enter; rotational shifts are normal, and internal movement to technical tracks does happen |
| Insurance software and BPS tracks | Indicative, varies by drive | A distinctive line of business — insurance platforms and services, where domain knowledge becomes the career asset rather than the stack |
Exam pattern
| Section | What it covers |
|---|---|
| Aptitude | Quantitative and logical reasoning at standard fresher level — arithmetic, ratios, time and work, series, puzzles, data interpretation |
| English / communication | Weighted more heavily here than at many recruiters, and some drives include a spoken or written assessment rather than only grammar MCQs — a direct consequence of client-facing delivery work |
| Technical MCQs | Programming fundamentals, data structures, DBMS and SQL, operating systems and networking basics; the mix shifts toward networks and OS for infrastructure-oriented roles |
| Coding | Usually one to two problems at easy to moderate difficulty for development tracks — logic, arrays, strings, basic algorithms — rather than a product-company bar |
| Interviews | A technical round on fundamentals and your project, then an HR round covering shifts, location, service agreement and communication |
Selection rounds
- Online assessment — aptitude, English or communication, technical MCQs, and coding where the role calls for it
- Technical interview — programming fundamentals, DBMS and SQL, OS and networking basics, and your project in depth
- HR interview — willingness to work in rotational shifts, location and relocation, service agreement terms, and a genuine communication check
- Documentation and onboarding, followed by training and allocation to a client engagement
Syllabus: what to prepare
| Area | Topics |
|---|---|
| Aptitude and reasoning | Percentages, ratios, averages, time and work, time-speed-distance, profit and loss, probability, number series, puzzles, data interpretation |
| English and communication | Comprehension, error spotting, sentence correction, vocabulary in context — plus speaking clearly and structuring a spoken explanation, which some drives assess directly |
| Programming fundamentals | One language you can defend (C, C++, Java or Python), control flow, functions, arrays and strings, recursion basics, and reading code you did not write |
| Data structures and algorithms | Arrays, strings, linked lists, stacks and queues, hashing, sorting and searching, basic complexity — moderate depth rather than competitive level |
| DBMS and SQL | Keys and constraints, normalisation, joins, group by and having, subqueries, transactions and ACID — with real query writing, which support work uses daily |
| Operating systems and networking | Processes and threads, memory management, basic Linux commands and file permissions, OSI and TCP/IP layers, TCP versus UDP, DNS, HTTP and HTTPS, IP basics — weighted more for infrastructure and support tracks |
| Service management awareness | What an incident, a service request, a change and a problem are, and what an SLA means — not usually tested formally, but knowing the vocabulary makes your interview answers sound informed rather than naive |
Sample questions
- Write a program to check whether a string is a palindrome, and state its time complexity.
- Find the second-largest element in an array in a single pass.
- What is the difference between a primary key and a unique key, and when would you use each?
- Write a SQL query to find duplicate rows in a table, then explain how you would remove them safely.
- What is the difference between a process and a thread?
- Which Linux commands would you use to check disk space, running processes and the last lines of a log file?
- Explain what happens when you type a URL into a browser and press enter.
- What is the difference between TCP and UDP, and why does a file transfer use one rather than the other?
- A user reports an application is slow. Walk me through how you would start investigating.
- Explain your project to me as if I were a client with no technical background.
Practise the DXC Technology interview before you face it
Phiny's AI runs a realistic DXC Technology-style mock interview — technical and HR rounds, instant feedback on every answer. Text interviews are free and unlimited.
Start a free DXC Technology mock interviewPreparation tips
- Take the English section seriously — it is a genuine filter here, not a formality, and some drives assess speaking or writing rather than only grammar. Practise explaining a technical thing out loud in plain English for two minutes, because that is closer to what the work actually requires.
- Ask which track your role sits in before you accept: development, application support, infrastructure operations, or service desk. They are different careers with different hours, and the answer is knowable at offer stage rather than a surprise after joining.
- Answer the shift question honestly. Rotational shifts including nights are normal in managed services because the clients are in other time zones, and saying yes to something you cannot sustain is worse for you than an honest no — but understand that flexibility genuinely widens which roles you are considered for.
- Learn basic Linux and networking even if you are targeting a development role. A handful of commands, log reading, and understanding what DNS and TCP actually do puts you ahead of most fresher candidates here and is directly useful in support and infrastructure interviews.
- Write SQL rather than memorising definitions. Support and maintenance work uses queries daily, and being able to write a join or find duplicate rows under questioning is worth more than reciting normal forms.
- Prepare the troubleshooting question, because it is asked in some form and most freshers have never thought about it. A structured answer — reproduce it, check what changed, read the logs, isolate the layer, escalate with evidence — reads as someone who could actually do the job.
- Learn the service-management vocabulary: incident, service request, change, problem, SLA. Ten minutes of reading, and it changes how your interview answers land in a company organised around exactly those things.
Frequently asked questions
What kind of company is DXC Technology?
It is a large global IT services company, formed in 2017 by merging Computer Sciences Corporation with the enterprise services business of Hewlett Packard Enterprise. Its work centres on running and modernising technology for large enterprises — infrastructure and cloud operations, application development and maintenance, security, analytics, and a substantial insurance software and services business — rather than on building its own products. For a fresher the practical translation is that you are working on a client's systems within a delivery organisation, with the scope and the priorities set by that client's contract. It is a real engineering environment with real operational discipline; it is not a product-company environment, and expecting one is the most common source of disappointment.
What is the selection process and test pattern?
The usual shape is an online assessment followed by a technical interview and an HR round. The assessment commonly covers aptitude, English or communication, technical MCQs across programming, DBMS, operating systems and networking, and a coding section for development-oriented roles. Two features distinguish it from a generic mass-recruiter test: the English component carries real weight and in some drives is spoken or written rather than multiple-choice, and the technical mix leans toward operating systems and networking for infrastructure and support tracks rather than being purely programming. Sections and weightings vary by drive, role family and cycle, so read your own posting rather than preparing to a pattern from a previous year.
Why is the English assessment weighted so heavily?
Because the work is client-facing in a way that a lot of fresher-level Indian IT work is not. Engineers in managed services and support write incident updates, join calls with client stakeholders in other countries, hand over between shifts, and document changes that other people rely on. Poor written or spoken communication is an operational risk in that setting rather than a soft-skills concern, which is why it is filtered at the assessment stage. The useful preparation is not vocabulary drilling: practise explaining a technical problem and its resolution out loud in plain, structured English, and practise writing three clear sentences describing what happened and what you did about it.
What package do freshers get?
Treat all figures as indicative and read the actual offer breakdown rather than a headline number. Volume fresher roles in this part of the industry broadly sit in the region of ₹3–4.5 LPA, with service desk and entry support roles typically lower and specialised digital, cloud or product-aligned tracks higher, and the specific number varying by drive, role family and whether you came through campus or off-campus. What moves compensation here faster than the starting band is what you do in the first two or three years — a genuine cloud or security certification with hands-on work behind it, or domain depth in something like insurance platforms, changes your position materially more than the entry number does.
Will I be doing development or support?
Both exist and you should find out which one you are being hired for, because it is the single most consequential thing about the offer. A meaningful share of fresher intake across this part of the industry goes into application support, production support and infrastructure operations rather than into new development, and that work is organised around incidents, service requests, changes and service levels. It is genuinely technical — you are debugging production systems that real businesses depend on, which teaches you things greenfield development does not — but the rhythm is different, the hours can be, and career progression runs through domain and certification rather than through shipping features. Ask directly at offer stage; a vague answer is itself information.
Are night shifts and rotational shifts really involved?
In managed services, infrastructure operations and support roles, yes, commonly — the clients are in other time zones and their systems have to be watched when they are working. Development roles are less likely to be shift-based but may still carry on-call or overlap hours with client time zones. This is normal for the industry rather than specific to this employer, and the honest advice is to decide what you can actually sustain before the HR round: night shifts have real health and social costs, and people who accept them under pressure and then struggle end up leaving within a year. If you are flexible, say so plainly, because it widens the roles you are considered for.
Is legacy technology a real part of the work, and is that bad for my career?
It is a real part of the portfolio, because the systems large enterprises depend on include long-lived platforms — mainframe environments, older enterprise applications, insurance and banking systems built decades ago — and someone has to run and modernise them. Whether that is bad for you depends entirely on how you play it. The honest risk is drifting for years on a stack with a shrinking market and no modern skills alongside it. The honest opportunity is that scarcity works in your favour: fewer engineers can work on these systems each year while the systems themselves are not going away, and people with both the legacy knowledge and modern cloud or data skills are genuinely valuable in modernisation work. If you land there, keep building current skills deliberately in parallel and set yourself a review date rather than letting five years pass by default.
Is there a service agreement or bond?
Service agreements are common in Indian fresher hiring and terms vary by role, track and cycle, so ask directly in the HR round for the duration, the exact penalty amount, whether it changes if the company terminates the arrangement, and what happens if you remain on the bench without allocation. Ask to read the document rather than accepting a verbal summary, and check the notice period and training-cost clauses specifically. One rule regardless of employer: never agree to your original certificates being retained as security, whatever justification is offered for it.
Which locations hire freshers?
The company has a large India delivery footprint across several cities, and the location you are offered depends on the account and the role family rather than on preference alone. For students from AP and Telangana this usually means being open to a metro posting, with the specific city set by which engagement you are allocated to. Ask in the HR round which location the role is for, whether it is fixed or account-dependent, and what the working model is, since delivery roles frequently require office presence tied to client requirements. Do not treat a preferred location as agreed unless it is in writing on the offer.
How does career progression actually work here?
Through two levers, and it is worth knowing them early because they are not the ones campus students assume. The first is certification with hands-on evidence — cloud platform certifications, security, or platform-specific credentials — which in a services organisation maps fairly directly to what you can be staffed on and therefore to what you are paid. The second is domain depth: an engineer who understands how insurance policy administration or banking settlement actually works is far harder to replace than one who knows a framework, because the framework can be learned in months and the domain cannot. Internal movement between tracks does happen, including from support toward engineering roles, but it rewards people who prepared for it deliberately rather than those who waited to be moved.
I am in the 2027 batch. What should I prepare?
Keep the standard mass-recruiter preparation running, because the aptitude and core-CS work serves every employer in this segment: aptitude as a steady habit, one programming language you can genuinely defend, data structures at a moderate level, and DBMS with real SQL practice rather than definitions. Then add the two things that specifically help here. Get comfortable with basic Linux and networking — a handful of commands, reading a log file, what DNS and TCP actually do — because most fresher candidates have none of that and it is directly relevant to support and infrastructure tracks. And work on spoken and written English deliberately: explain a technical topic out loud for two minutes, write three-sentence summaries of what you did, and get someone to tell you honestly whether it was clear. That is a scored section here and a career skill everywhere.
Keep preparing
- Aptitude shortcuts for placement exams — the first section of every test, including DXC Technology's.
- HR interview answers that work — the round after you clear the DXC Technology test.
- Communication round prep — essays, voice tests and email tasks.
- Fresher jobs in Hyderabad — where most DXC Technology postings in the Telugu states land.
- Free tools: check your eligibility, see the real in-hand salary, test your aptitude speed.