Hiring a software engineer in 2026 is rarely blocked by lack of applicants. It is blocked by pipeline quality: vague role specs, non-technical screening, too many parallel interviews, and offer stages that drift.
Whether you run hiring internally or work with an IT recruiting partner, the same five-stage model applies. Breakdowns happen when each stage is owned by a different quality bar — or when nobody owns seniority calibration early.
This guide maps the modern IT hiring process from role brief to first working day, with realistic timelines and a comparison to volume-agency patterns. For how to evaluate recruiters themselves, see What a Good IT Recruiting Partner Should Do.
Stage 0 — Role definition (before sourcing starts)
Most failed hires begin here — not in the interview room.
Engineering brief vs generic job description
A JD written by HR often lists technologies without context. An engineering brief answers:
- What will this person own in the first 90 days?
- What level of autonomy — execution, design leadership, or cross-team coordination?
- Must-have skills vs learn-on-the-job skills
- Team composition today (ratio of senior/mid, gaps you are filling)
Seniority band — not title inflation
“Heavy on senior” reqs in a heated market produce mismatches: over-leveled hires who churn, or reqs that block strong mid-level engineers who would execute better. Calibrate competencies, not LinkedIn titles. (We explore market distortion in Senior Gold Rush and the Forgotten Mid-Level Engineer.)
Employment path — decide early
Before sourcing:
- Permanent hire onto your payroll — remote EU or direct employ where you have entity
- Nearshore employ through a partner when you lack a local entity — same recruitment journey, different payroll path after offer
Confusing perm hire with staff augmentation creates rework at offer stage. Route temporary vendor capacity to outstaffing; route long-term headcount to IT Recruiting.
Owner: Hiring manager + CTO/EM · Typical duration: 2–5 days for a focused brief
Stage 1 — Sourcing
Sourcing is more than posting on a job board.
Effective channels for senior and mid-level engineers:
- Trusted networks and referral paths — lower noise than open boards
- Active search targeted by stack, geography, and level
- EU nearshore markets (e.g. Poland) when UK, Nordics, or Western Europe buyers need timezone-aligned talent
Open boards alone attract high volume and high variance. Senior candidates often are not actively browsing — they respond to credible outreach with a clear role and respect for their time.
Owner: Recruiter or partner · Runs in parallel with: Stage 2 screening of inbound pipeline
Stage 2 — Technical screening
This is the highest-leverage stage — and the one most often delegated to non-engineers.
Who runs it
Engineers evaluate code, design thinking, and domain fit. HR may coordinate scheduling and compliance; they should not be the technical pass/fail gate.
Artifacts that work
Pick one or two — not all four:
- Live technical conversation — problem solving, trade-offs, past systems
- System design discussion — appropriate for senior and strong mid levels
- Focused take-home — time-boxed, production-relevant, reviewed by engineers
- Pairing session on a realistic snippet
Document pass/fail criteria before interviews start. “We know good when we see it” does not scale across interviewers.
Output per candidate
Written notes: strengths, risks, suggested probes for client interviews, level recommendation. Candidates who fail here should not reach your calendar.
Owner: Partner engineers or internal screeners · Typical duration: ongoing weeks 1–2
Stage 3 — Client evaluation
Your team interviews finalists only — not everyone who applied.
Shortlist size: 2–4
Two to four vetted candidates is enough for:
- Comparison without manager exhaustion
- Faster scheduling and debrief
- Strong candidate experience (finalists know they are serious contenders)
If you are interviewing more than four for one role, screening upstream failed.
Two-way evaluation
The best hires are mutual choices. Candidates should meet their future peers and ask hard questions about roadmap, tech debt, and growth. Encourage it — it reduces early churn.
Owner: Hiring manager + team · Typical duration: week 2–3
Stage 4 — Offer and close
Offers fail when compensation, level, and start date were never aligned with market reality.
Benchmarking
Use local/nearshore data at city level — not generic regional averages. D-Factor publishes gated salary benchmarks for budgeting (request via IT Recruiting — Java nearshore rates as a starting point).
Notice periods and competing offers
EU notice periods can add weeks. Parallel processes need transparent timing — ghosting finalists damages your employer brand in small markets.
Closing checklist
- Written offer aligned to agreed level band
- Start date accounting for notice
- Equipment and access plan drafted
- Payroll path confirmed (client employ vs partner employ if applicable)
Owner: Hiring manager + HR/People + partner · Typical duration: week 3–4 to signed offer
Stage 5 — Onboarding
Recruiting success is measured at month six, not day one.
Minimum viable onboarding for remote/nearshore perm hires:
- Day-one access, buddy assignment, architecture overview
- 30/60/90 expectations documented — not improvised
- Regular engineering leadership touchpoints for nearshore FTEs (visibility reduces “ceiling” attrition)
- Payroll and compliance complete before start — no “we’ll fix contract later”
Owner: Engineering manager · First working day: often ~2 months from initial brief when notice and setup included
Timeline at a glance
| Stage | Typical week | Milestone |
|---|---|---|
| 0 — Role definition | Week 0 | Signed brief, level band, employment path |
| 1–2 — Source + screen | Weeks 1–2 | Finalists identified |
| 3 — Client interviews | Weeks 2–3 | Preferred candidate |
| 4 — Offer | Weeks 3–4 | Signed offer |
| 5 — Onboarding | Weeks 4–8+ | First working day (~2 mo total) |
Timelines compress with prep work and a clear bar. They expand when the brief changes mid-search or every applicant bypasses technical screening.
Generic agency vs engineer-led path
| Dimension | Volume agency | Engineer-led recruiting |
|---|---|---|
| Screen owner | HR / recruiter keywords | Peer engineers |
| Shortlist size | 8–15 CVs | 2–4 finalists |
| Technical notes | Rare or generic | Required per finalist |
| Failure mode | Interview becomes first filter | Bad fits removed upstream |
| Candidate experience | Mass outreach | Curated, respectful process |
| Time-to-offer | Looks fast (many names early) | Honestly ~3–4 weeks |
| Best for | High-volume generic roles | Specialist engineering hires |
How D-Factor maps to this pipeline
Our IT Recruiting journey mirrors the stages above:
- Alignment — stack, seniority, employment path, timeline
- Targeted sourcing — network + active search across Europe
- Engineer-led vetting — CTO-curated bar, five-stage partner quality upstream
- Client evaluation — 2–4 finalists with assessment notes
- Offer & onboarding — perm on your payroll or nearshore employ when you lack a local entity
Same recruitment engine for every path — only the employment mechanics after offer differ.
Hiring a specialist role now? Share your engineering brief — we align on level and timeline before the first candidate reaches your team. Start at IT Recruiting →