Engineering, data, design-adjacent and infrastructure roles hired at intern, fresher or graduate level.
Not senior engineering hiring scaled down. The assessment methods that work for a candidate with five years of shipped work do not transfer to someone with three university projects.
Early-career technical hiring in India has more candidates and worse signal than almost any other category. Every CV lists the same stack, the same three projects and a similar set of certificates. The differentiator is not on the paper, so a process built around reading CVs is reading noise.
What works is straightforward and widely known, and still not widely done: give candidates something realistic to build or debug, and watch how they think about it.
When this is the right hire
Compared with hiring experienced engineers only:
the work is learnable, you have engineers who can review code and mentor, and you want a team that will still be here in three years. Entry-level technical hiring also forces the documentation and review discipline that senior-only teams quietly skip.
nobody has review capacity. An unreviewed junior engineer produces code the team will pay for later, and the debt exceeds the salary saved.
How to do it well
- 1Decide which roles genuinely work at entry level
Application development, QA, data analytics, support engineering and web development do. Architecture, security response and platform ownership generally do not.
- 2Replace CV ranking with a practical
A timeboxed task on a realistic problem, reviewed by an engineer who gives one line of feedback. This is the assessment.
- 3Test reading, not just writing
Give them unfamiliar code and ask what it does and where it breaks. Reading code is most of junior engineering work and almost nobody assesses it.
- 4Drop the algorithm quiz unless the job is algorithms
Competitive-programming filters select for people who practised competitive programming. If that is the job, fine; otherwise it is a proxy for nothing you need.
- 5Structure the interview and score independently
Technical panels anchor as hard as any other, and the most senior engineer in the room sets the score for everyone if you discuss first.
- 6Move fast
Early-career technical candidates receive multiple offers and accept the fastest credible one. Two weeks end to end is achievable and it wins candidates.
What to pay
Early-career technical pay in India varies more by company type than by candidate: product companies, GCCs, services firms and startups occupy visibly different bands for the same skill. Decide which band you are competing in and pay it properly rather than paying a services-firm rate and interviewing like a product company. Candidates know the bands — the numbers are discussed openly in student communities — and a mismatch between your process and your offer is noticed immediately.
How to assess
- A realistic build or debug task, timeboxed to two or three hours, reviewed by an engineer.
- Code reading: hand them something unfamiliar and ask what it does and how it fails.
- How they debug when the obvious cause turns out to be wrong — method rather than luck.
- Whether they can say "I do not know" about the boundary of their own knowledge.
- Public work where it exists — a repository, a deployed project, a written explanation of something they built.
What goes wrong
Selects for people who practised for the quiz, and loses strong engineers who built things instead.
Nobody at entry level has all eight, and you lose candidates who have the three that matter.
Most junior work is understanding existing code. Assessing only writing tests the smaller half of the job.
The candidate accepted somewhere else at round three. Length is not rigour.
You get code nobody reviewed, and the debt outlives the saving several times over.
Questions employers ask
Which technical roles work at entry level?+
Application and web development, QA and test automation, data analytics, support engineering and junior data engineering all work well with review capacity in place. Architecture, security incident response and platform ownership generally do not — they require judgement built from having been wrong before.
How do you assess a developer with no work experience?+
Give them something realistic to build or debug, timeboxed to two or three hours, and have an engineer review it. Then ask them to read unfamiliar code and explain it. Between them these cover most of what junior engineering work actually consists of.
Should we use competitive programming problems?+
Only if the job is algorithmic. Otherwise you are selecting for people who practised for that specific format, and losing engineers who spent the same time building and shipping things — often the ones you would rather have.
How fast should a technical hiring process be?+
Two weeks end to end is achievable and it wins candidates. Early-career technical candidates typically hold several processes at once and accept the fastest credible offer, so length costs you the candidates you assessed most favourably.
Do we need senior engineers to hire juniors?+
You need review capacity, which is not quite the same thing. Someone must review the code, answer questions and set the standard. Without that, junior hires produce work the team pays for later, and the cost exceeds the salary difference.
Related
Free tools for this
No signup. Nothing here asks for your email first.