Early-career hiring tests potential rather than track record, so it leans on timed assessments, aptitude tests, assessment centres and the projects you can explain. The formats differ by region, but every one of them rewards preparing in the order the funnel runs.
High demand22 min readGraduate Recruiter / Early Careers Talent Partner, Campus Recruiter / University Relations Lead, Assessment Centre Assessor, Engineering Manager hiring interns or new graduates, Training and Placement Officer at a universityUpdated 2026-10-10
Assumes you know: Enough programming to solve a short problem in one language without looking things up, One project, from coursework or otherwise, that you built a meaningful part of
Overview
What this area actually covers
Early-career hiring is everything that happens between a student deciding to
apply for a first internship and a new graduate signing a first offer. It covers
timed online coding assessments, numerical and verbal aptitude tests,
situational judgement tests, internship and co-op interviews, the graduate
scheme assessment centre with its group exercise and presentation, campus
recruitment drives, the one-page resume with no work history on it, and the HR
conversation about relocation, bonds and a first salary.
The defining property of this whole area is that the employer cannot assess you
on what you have done, because you have not done much yet, and both sides know
it. Experienced hiring asks "have you solved this before?". Early-career hiring
asks "can you learn, can you reason under time pressure, and will you be
pleasant and reliable to train?". Every format in this section is an attempt to
measure those three things cheaply and at volume, and once you see them that way
the formats stop looking arbitrary. An aptitude test is a cheap proxy for
reasoning speed. A group exercise is a cheap proxy for how you behave in a team.
A question about your final-year project is the only proxy anyone has for how
you make decisions when nobody is marking each step.
What people wrongly bundle in is the full experienced-hire loop. A new-graduate
candidate does not usually face a system design round, and preparing for one at
the expense of fundamentals is a common misallocation. The other misplacement is
treating early-career hiring as a lighter version of the normal process. It is
not lighter; it is different. The volume is far higher, the filters are blunter,
and the early stages are frequently automated, which means a candidate can be
removed by a score threshold before any human has read their name.
A third thing worth separating out is the difference between an internship as a
job and an internship as an extended interview. At many employers the summer
internship or placement year is the main route to a graduate offer, and the
conversation about a return offer starts on the first day rather than the last.
This section treats the internship itself, not only the interview for it, as
part of the hiring process, because that is how employers who run them treat it.
Now practise it
38 interview questions in Early Careers, Internships & Graduate Hiring, each with the rubric the interviewer is scoring against.
The section is divided by format rather than by region, because the same format
appears in several regions under different names, and a student in one country
applying to an employer headquartered in another will meet both conventions. A
UK student applying to a US technology company sits a US-style online
assessment; an Indian student applying to a multinational's graduate programme
may face a UK-style assessment centre. Read the subsection that matches the next
stage you are actually facing.
Subsection
What it is for
Online Assessments
Passing the automated coding screen that comes before any human
Aptitude & Reasoning Tests
Numerical, logical, verbal and situational judgement tests, done fast and accurately
Internships & Co-ops
Getting a first internship, doing well in it, and turning it into an offer
Graduate Schemes & Assessment Centres
The structured day of group, case, strengths and presentation exercises
Campus & New-Grad Hiring
Campus drives, career fairs, off-campus routes and comparing first offers
Projects & Your First Resume
Making coursework and side projects into evidence an interviewer can probe
Fresher HR & First Offers
The HR round, bonds, relocation, gaps and the first salary conversation
Online Assessments covers the timed coding test that many technology
employers now send before any interview: a fixed number of problems, a timer,
sample tests you can see and hidden tests you cannot. It exists as its own
subsection because the skill is partly strategic rather than purely technical,
and strategy is where well-prepared candidates still lose marks: spending forty
minutes on the hardest problem, polishing a passing solution instead of starting
the next, or submitting nothing for a problem where a brute-force answer would
have passed half the hidden cases. You will also find material on newer sections
where an AI assistant is provided inside the test, on "what does this code
print" questions, on proctoring set-up, and on whether a retake is worth it.
Aptitude & Reasoning Tests is the psychometric family: numerical reasoning
with percentages and data tables, time-speed-distance and work-rate problems,
syllogisms and seating arrangements, critical-thinking tests with their "true,
false or cannot say" answers, permutations and probability, and situational
judgement tests. It is separate from the coding screen because it is a different
kind of skill — mostly speed and accuracy on familiar problem types — and
because it is used across every region and many non-technology employers,
including banks, consultancies and public bodies. Every page there carries
worked examples with the arithmetic laid out so you can check it.
Internships & Co-ops covers the first- and second-year internship interview
where you have no experience to talk about, coding in a shared document with no
compiler, the co-op term and placement year, and what actually decides a return
offer. It is its own area because the internship is both a job and a long
interview, and the habits that earn a return offer — asking for feedback early,
making your progress visible, writing up what you did — are not the habits that
pass the interview to get in.
Graduate Schemes & Assessment Centres handles the structured graduate
programme route, strongest in the UK and Europe and common in Australia, the
Gulf and among multinationals in South-East Asia and India. The assessment
centre is a day, often run virtually now, of group exercises, case studies,
strengths-based interviews and presentations, preceded by a recorded video
interview. It is separated out because the scoring is explicitly behavioural and
observable, and candidates who treat it as a performance rather than a set of
observed behaviours tend to talk too much in the wrong exercises.
Campus & New-Grad Hiring covers the campus routes and the routes around
them: India's placement drives where an aptitude test, a technical round and HR
can all happen on one day; product-company new-graduate coding rounds; US and
Canadian career fairs; off-campus applications and referrals for anyone whose
university has no recruiting programme; and comparing two first offers when one
comes with a training bond. It is its own subsection because the logistics of a
season — many applications, many rejections, a calendar you do not control —
need a strategy of their own, including how to work out which stage you are
failing at.
Projects & Your First Resume is about turning what you have already built
into evidence. It covers explaining a final-year project end to end, a one-page
resume with no work experience, making a tutorial-heavy repository worth
discussing, and separating your contribution from a team's in a hackathon or a
group project. It exists separately because for most early-career candidates
this is the only material an interviewer can probe in depth, and it is where
honesty is tested hardest.
Fresher HR & First Offers covers the HR round as a graduate meets it: why
hire you over other graduates, whether you will relocate or work shifts or sign
a service agreement, negotiating a first salary with nothing to anchor on,
explaining a gap year or a repeated year, and the five-year question. It sits
last because it is usually the last conversation, and because the most common
mistake in it is either agreeing to everything or treating a fixed graduate rate
as negotiable when it is not.
Where it sits in a real business
Most organisations that hire graduates at any volume run early careers as a
separate function from experienced hiring, with its own recruiters, its own
calendar and its own budget. The reason is structural. Experienced hiring fills
one seat at a time when a manager needs it filled; graduate hiring fills a
cohort, decided a year or more in advance, that will start together, train
together and be placed into teams afterwards. That difference explains most of
what feels strange about the process: why applications open so early, why the
salary is often a fixed figure, why you may not know which team you will join,
and why the early stages are automated.
A cohort model also changes what you are being compared against. You are not
competing with the best possible candidate for one role; you are being ranked
against a pool of people at the same stage, and anyone above a threshold may be
offered a place. That is good news. It means the process is more forgiving of a
single weak moment than a one-seat hire, and more punishing of a missing stage,
because each automated filter is a gate you either clear or do not.
Loading diagram…
The edge to study is the first one out of the assessment. It is the only point
in the funnel where you are removed without a person ever considering you, which
is why it rewards a kind of preparation — timed practice, test-taking strategy —
that later stages do not. The dotted line at the bottom matters too: at
employers who run internships, the internship itself is the main input to the
next offer, so the funnel loops back on itself for anyone who gets in once.
Universities are part of this system as well, and in some regions they are a
large part. A careers service in the UK, a co-op office in Canada, or a training
and placement cell in India mediates contact with employers, sets rules about
how many offers a student may hold or when they must accept, and sometimes
controls which employers visit which students. If your university has such
rules, they bind you as firmly as the employer's do; read them before the season
starts rather than after your first offer.
How the formats differ by region
The same three underlying questions are asked everywhere, but the packaging
varies enough that a candidate prepared for one region's format can be wrong
footed by another's. These are broad patterns, not rules, and individual
employers vary within every region. Multinationals often run one global process
that looks like their headquarters' convention, whichever country you apply
from.
Region
Dominant early-career route
What the screen usually looks like
Distinctive features
United States
Summer internships leading to new-graduate offers
Online coding assessment, then one or more technical interviews
Recruiting for summer roles often starts in the preceding autumn; career fairs on campus
Canada
Co-op terms alternating with study, plus new-grad roles
Coding assessment or technical interview, often through a university co-op portal
Several work terms across a degree; co-op offices set application rules
UK and Europe
Graduate schemes and placement years
Aptitude tests, situational judgement, recorded video interview
Assessment centres; applications typically open around a year before the start date
Australia
Graduate programmes and summer vacation programmes
Aptitude or psychometric tests, video interview
Programme intakes usually start early in the year; assessment centres common
Gulf
Graduate and development programmes at large employers and multinationals
Aptitude tests, interviews, sometimes assessment centres
National workforce programmes prioritise citizens for some roles; eligibility varies
South-East Asia
Management trainee and graduate programmes, multinational new-grad roles
Mix of US-style coding assessments and UK-style aptitude tests
Varies widely by country and by employer's headquarters
India
Campus placement drives, plus off-campus and product-company hiring
Aptitude test, coding round, technical interview, HR, often in one day
Mass-recruiter drives at volume; service agreements and training bonds are common
Two consequences follow. First, check which convention an employer is using
before you prepare, not which country you are in; the invitation email and the
careers page almost always say what the stages are. Second, the calendar is the
most region-specific thing in the table and the easiest to miss. In regions
where applications open a year early, a student who starts looking in their
final spring can find most graduate schemes already closed, and the honest
advice is to find out your region's timing in your first or second year.
Mass-recruiter campus drives deserve one more sentence because they are the one
format that is genuinely India-specific. Large service and outsourcing employers
visit campuses and hire in large numbers, with an aptitude section that removes
most candidates, a technical interview on fundamentals, and an HR round that
often raises relocation, shifts and a service agreement. The cut-offs and the
section mix vary by employer and by year; the invitation is the only reliable
source.
Who does this work
On the other side of the table are graduate or early-careers recruiters, who
run the calendar, the campus relationships and the automated stages, and who
are measured on filling a cohort with people who accept and stay. They rarely
make the final technical call, but they decide the thresholds and the shape of
the process, and in assessment centres they often act as assessors themselves.
Assessors at an assessment centre are a mix of trained recruiters and
volunteers from the business: graduates from earlier cohorts, managers,
sometimes senior staff. Each assessor usually watches a small number of
candidates against a written list of behaviours and writes down what they saw.
They are not trying to pick a winner of the group exercise; they are trying to
fill in a form, and the form rewards specific observable actions.
Engineers and engineering managers conduct the technical interviews for
internships and new-graduate roles, often with a question bank and a calibrated
expectation of what a student should know. Many of them volunteered for the
campus season on top of their usual work. They will usually be kind, short of
time, and more interested in how you think aloud than in whether you finish.
In India and some other regions, a university's training and placement officer
coordinates the drive: which employers come, which students are eligible, which
day each employer gets, and sometimes how many offers a student may accept. That
officer is not assessing you, but their rules shape your season, and they are a
good source of information about how past drives at your institution ran.
Demand is high in the plain sense that every year a new cohort of students in
every region goes through these processes, and every employer that wants to
build its own talent pipeline runs some version of them. It is not a cycle that
disappears. The volume of hiring in any given year moves with the economy and
with each sector's confidence, and early-career hiring is often among the first
budgets to shrink in a downturn, so a hard season is not evidence that the
route has closed.
Three changes have reshaped the texture of the process. The first is
automation. Applying to many employers became easy, so employers receive far
more applications per place and push more of the filtering into automated tests
that run before a human looks. That makes the early stages more decisive than
they used to be and makes generic applications less useful.
The second is the move to virtual formats. Assessment centres, which were once
a day in an office, are now frequently run online, and recorded video interviews
— where you answer on-screen prompts with a short preparation time and no live
interviewer — have become a common early stage. The skills are the same, but the
set-up matters more: a quiet room, a stable connection, and practice speaking to
a camera without feedback.
The third is AI tooling. Some coding assessments now include sections where an
assistant is provided and the test measures how you use it: whether you
understand a repository before changing it, whether you verify what it
produces, and whether you can explain the change. At the same time, employers
lean more heavily on live conversation about your own projects, because that is
hard to outsource. Expect the questions about your project to go deeper than
they would have a few years ago. How a specific vendor scores any of this is not
something this site can tell you, and anyone who claims to know is guessing.
What makes it hard
The first difficulty is volume with no feedback. A student in an active season
may apply to dozens of employers, sit many assessments and hear nothing from
most of them. Rejection at an automated stage rarely comes with a reason, so it
is easy to conclude that you are bad at interviews when in fact you are failing
one specific gate — the aptitude section, say — and passing everything else.
The single most useful habit in this area is keeping a record of which stage
each application reached, because the pattern tells you what to fix.
The second is that the skills being tested are unfamiliar even to strong
students. Nobody teaches you to solve a data-table percentage problem in under a
minute, or to rank five plausible responses to a workplace dilemma, or to speak
for two minutes to a camera with thirty seconds' notice. These are learnable and
mostly mechanical, but they need practice under the real timer, and reading
about them is not practice.
The third is the honesty problem in projects. Most early-career candidates have
built things in groups, from tutorials, or with heavy help. The interviewer
knows this and is not looking for a solo masterpiece. What they are looking for
is whether you can say precisely what you did, what you decided, and what you
would change. Candidates who inflate a group project into a personal
achievement are found out by the second follow-up, because they do not hold the
details only a participant would hold.
The fourth is judgement about offers with almost no experience. A first offer
can come with a training bond, a relocation clause, a shift pattern or a
deadline, and a student who has never read an employment contract is asked to
decide quickly. The hard part is not the arithmetic; it is knowing which terms
are standard, which are negotiable, and which you should ask about in writing.
A sensible preparation order
The temptation is to prepare for the most interesting stage first — usually the
technical interview — and arrive at an aptitude test unprepared. Prepare instead
in the order the funnel runs, weighted towards the stages that remove the most
people, because a stage you never reach is a stage you prepared for in vain.
Loading diagram…
Look at the first box. It is first not because the resume is the most
important document but because every later stage draws on it: the project you
put on it is the one you will be asked to explain, and the claims you make on it
are the ones the technical panel will probe. Getting it honest and specific
early saves rework later.
Within that order, a few rules of proportion hold for most candidates. Spend
your earliest practice under timed conditions, because accuracy without speed
fails an automated test. Learn fundamentals — data structures, basic
algorithms, one language well, and the computer science basics your course
covered — to the point where you can explain them aloud, since early-career
technical rounds usually go wide rather than deep. Build a small bank of real
stories from university, part-time work, societies and projects before the HR
round, not the night before it. Leave the assessment-centre practice until you
know your route uses one, because if you are applying only to employers that run
coding loops it is wasted effort.
A FOUR-WEEK PLAN BEFORE AN APPLICATION SEASON
Week 1 Resume to one page. Pick one project and write a half-page
account: problem, your part, two decisions, one thing that
failed, what you would redo. Start a tracker of applications
with a column for the furthest stage reached.
Week 2 Timed practice. Two short aptitude or coding sets per day
under the real timer. Mark every mistake by type - arithmetic
slip, misread question, ran out of time - not just right or
wrong.
Week 3 Fundamentals aloud. One topic a day explained to someone or
to a recording: arrays and hashing, trees, recursion, a
database basic, an operating system basic. Write code in a
plain document without running it, then check it.
Week 4 Stories and offers. Six short stories from your own life,
each with what you did and what changed. Read one real
graduate contract or offer template if you can find one,
and list the terms you would want to ask about.
The plan is deliberately unambitious. Four weeks of consistent, timed, honest
practice beats a weekend of reading every guide on the internet, and the tracker
started in week one is what tells you, by the middle of the season, where to
spend the next four.
What interviewers and assessors actually score
Across every format, the scoring falls into a small number of families, and
knowing which family a stage is measuring tells you what to emphasise. A
candidate who treats a group exercise as a test of being right, or a coding
round as a test of finishing, is optimising for something nobody is writing
down.
Stage
What is scored
What is not scored, despite appearances
Online coding assessment
Hidden tests passed, sometimes code quality or time
How elegant your unfinished solution was
Aptitude test
Correct answers within the time, sometimes against a norm group
Showing your working
Situational judgement test
How closely your ranking matches the employer's preferred responses
The most heroic or self-sacrificing answer
Technical interview
Reasoning aloud, fundamentals, testing your own code, taking hints
Reaching the optimal solution in silence
Group exercise
Building on others, structuring, timekeeping, including quieter people
Airtime, or winning the argument
Case study or presentation
A clear recommendation, structure, risks named, time kept
Covering every document in the pack
Strengths or motivation interview
Specific, genuine examples and real knowledge of the role
A polished generic answer
Project discussion
Your own decisions, trade-offs, failures and what you would change
The size or impressiveness of the project
The right-hand column is the one to read twice. In nearly every row, the thing
candidates instinctively optimise for — speed in silence, airtime, heroism,
scale — is exactly what the scoring ignores, and the thing that is scored is a
behaviour you can choose to show on purpose.
One thread runs through the whole table: early-career assessors are scoring
trajectory. They know you will not be the finished article. What they want to
see is evidence that you learn quickly, take a hint without defensiveness,
admit what you do not know, and work well with people. A candidate who says "I
have not used that, but here is how I would find out" and then reasons sensibly
usually scores better than one who bluffs.
Why study it
Because the early stages remove most candidates, and they do so on skills that
are learnable in weeks. An aptitude section or a timed coding screen is not a
measure of your worth as an engineer; it is a gate with a technique, and the
gap between an unprepared attempt and a practised one is large. Very few things
in a career offer that ratio of return to effort.
There is a second reason. The habits this section builds — explaining your own
work precisely, separating your contribution from a team's, asking for feedback
before you need it, reading a contract before you sign it — are the habits that
make the first two years of a job go well. They are not interview tricks.
Who should not spend long here: if you already have two or more years of full
time work, most of this section is not for you, and the experienced-hire
sections will serve you better. If your route is a single employer with a known
process — a sponsored degree, a return offer already in hand — read only the
subsection for the stage you face. And if you are struggling with basic
programming, no amount of assessment strategy will help; spend the time on
fundamentals first and come back.
Your first hour
Build the tracker and the project page, because everything else in this section
uses them.
1. THE TRACKER (a spreadsheet, one row per application)
Employer | Route (internship, scheme, campus, off-campus)
Region convention | Date applied | Furthest stage reached
What the stage was (OA, aptitude, video, interview, AC, HR)
Outcome | Anything you noticed
2. THE PROJECT PAGE (half a page, written, then said aloud once)
The problem, in one sentence a non-specialist would follow
What you personally built, separated from the team's part
Two decisions you made and the option you rejected each time
One thing that broke or failed, and how you found out
What you would do differently with another month
Then take one timed practice test in the format your next application uses —
an aptitude set or a coding problem set — under the real time limit, without
pausing. Record the score, and next to it the reason for every mark you lost.
The test of the project page is whether you can talk for ninety seconds from it
without reading, and then answer "what would you change?" with something
specific rather than "I would add more features". The test of the practice
attempt is not the score; it is whether you can name the commonest type of
mistake you made. That type is what your next week of practice is for.
What this is not
It is not a lottery, even though it feels like one during a season of silence.
The automated stages are consistent, and a candidate who tracks where they fail
and practises that stage usually sees the pattern change.
It is not a test of how much you have built. A modest project you can explain
honestly is worth more than an impressive one you cannot defend, and
interviewers calibrate their expectations to a student.
It is not the same everywhere, and advice written for one region can mislead
in another. A US-centred guide may never mention assessment centres; a UK guide
may not mention co-op terms or campus drives. Check the format of the employer
in front of you.
It is not a place for shortcuts on assessments. Proctoring rules exist, they
are enforced, and the material in this section is about setting up correctly
and understanding the rules, never about getting round them. A flagged
assessment can end an application, and what happens after that is set by the
employer's own rules, which the invitation usually states.
And it is not the experienced-hire process with the difficulty turned down.
The panels expect less depth and more potential, less system and more
reasoning, and they reward candour about what you do not yet know more than
any other interview you will sit.
Prepare in the order the funnel runs, and keep a record of where each
application stopped: the pattern in that record is the most useful feedback
an early-career season will ever give you.