A seed-stage engineering interview process should answer a small set of questions about the work, the person and the conditions for joining. Give each question an owner, collect evidence once and make the decision against the brief you agreed at the start.
Corellia recommends planning around two to three weeks for a candidate’s interview process, with the preparation completed before the first conversation. The timetable runs from the first candidate conversation to the hiring decision. Adapt it to the candidate’s availability and the role’s requirements.
In this guide
- Before week one: agree the brief and protect the time
- Week one: establish mutual fit and inspect relevant work
- Week two: test the work and meet the team
- Week three: resolve specifics and reach a decision
- Give useful feedback
- Printable checklist
- Questions founders ask
Before week one: agree the brief and protect the time
Preparation should resolve what you are hiring for before a candidate enters the process.
Write the role’s first meaningful outcomes, essential skills, decision authority and working arrangement. Agree the salary band and which package elements need approval. Use the founding engineer brief for an early individual contributor, or the leadership mandate guide if the role includes responsibility for people and strategy.
Then make a small assessment plan. Each stage needs a question, an interviewer and a way to record the evidence. A useful starting set is:
| Question | Evidence to seek | Owner |
|---|---|---|
| Does the opportunity fit what the person wants? | Motivation, scope, location and package discussion | Founder or hiring manager |
| Have they solved relevant problems? | Detailed walkthrough of delivered work | Technical interviewer |
| Can they approach the work we need? | Bounded work sample and discussion | Technical interviewer |
| Can we make decisions together? | Collaboration scenario and team conversation | Future manager and relevant colleague |
| Are the remaining terms understood? | Written package and outstanding questions | Hiring decision-maker |
This follows the principle of defining requirements before evaluating people. Greenhouse’s structured-hiring guidance similarly puts the role discussion and scorecard before interview planning. [Source 1]
Reserve interview and decision slots in advance. Assign a deputy if the decision-maker is away. A process that relies on finding spare time after each stage has no dependable schedule.
Send the candidate a short overview covering the stages, people, preparation, assessment format and contact person. Ask about adjustments they need to participate. For UK recruitment, Acas provides guidance on reasonable adjustments, consistent questions and communicating next steps. [Source 2]
Week one: establish mutual fit and inspect relevant work
The first week should determine whether there is enough alignment and relevant experience to justify a practical assessment.
First conversation: agree what both sides are considering
The hiring manager or founder should explain the product, the role and its immediate constraints, then ask what the candidate wants from a move.
Allow roughly 30 to 40 minutes in this proposed plan. Cover the actual working pattern and package early enough to identify a mismatch. Leave room for the candidate’s questions rather than using the whole conversation to describe the company.
At the end, summarise the next step and when they will hear back. If something needs checking, name it. Do not allow a practical question about attendance or scope to become an unspoken reason for rejection.
Work walkthrough: understand the person’s contribution
The technical interviewer should explore one relevant piece of work in depth, rather than test recall across a list of technologies.
Ask what the person owned, what alternatives they considered, what failed and how they knew the result was useful. Follow the evidence: if the project was collaborative, distinguish their decisions from the team’s. Give them room to describe work without sharing confidential material.
A proposed 45-minute conversation is enough to inspect one substantial example without turning it into a second general interview. If essential evidence is missing, identify the exact question that the next stage should resolve.
The interviewer should record evidence before reading anyone else’s feedback. Keep observations separate from conclusions: a description of a trade-off is more useful than simply writing that someone seemed senior.
Week two: test the work and meet the team
The second week should add evidence that the initial conversations could not provide.
Practical assessment: choose one relevant format
Use a bounded exercise that resembles a decision the engineer will actually face. For a product engineer, that might be diagnosing an unreliable workflow. For infrastructure, it might be prioritising a reliability improvement with limited information.
Choose a live session or a short prepared exercise, not both by default. In this plan, reserve 60 to 75 minutes for the exercise and discussion. Explain what will be assessed, which tools are allowed and how the candidate can prepare. If AI tools are permitted, ask the person to explain and verify the result.
Review the same criteria for every candidate: how they frame the problem, the quality of the reasoning, their handling of uncertainty and how they respond to new information. An elegant result without an explanation should not settle those questions.
If you need a longer trial, agree its scope and payment separately. For UK work trials, Acas explains that payment requirements depend on the circumstances, including whether the work goes beyond genuinely testing suitability. [Source 2]
Team conversation: show how work happens
The future manager and a relevant colleague should discuss a realistic collaboration problem and answer the candidate’s questions about the team.
Use one example: a customer commitment conflicts with a reliability concern, or the team disagrees about what to build next. Ask how they would establish the facts and reach a decision. Explain how your team handles similar situations, including who has authority.
Do not repeat the technical exercise or introduce a vague personality test. The purpose is to understand working behaviour and let the candidate assess the people they would join. A proposed 45-minute session keeps the discussion focused.
Check the assessment against the first five engineering hires you are planning. Someone’s contribution should make sense alongside the support and responsibilities that will actually exist.
Week three: resolve specifics and reach a decision
A third week should resolve genuine outstanding questions, rather than become a default extra round.
If the evidence is sufficient at the end of week two, make the decision then. If a specific concern remains, decide what would answer it. A short clarification call may be appropriate; another full interview with no new question is not.
Hold a decision meeting against the original criteria. Ask each interviewer to explain the evidence behind their recommendation. Distinguish a missing skill from a skill the role can support someone in developing. If the brief itself has changed, acknowledge that change instead of judging the candidate against an undisclosed requirement.
For an offer, confirm the approved terms, any conditions, a realistic start-date discussion and the owner of follow-up questions. Keep salary, bonus and equity distinct. The salary guide can inform the package conversation where the evidence matches the role.
Schedule any references or checks with the candidate’s knowledge and agreement where appropriate. Keep the process moving without asking them to resign before they have understood the written terms.
Give useful feedback
Candidate updates should state what has been decided, what remains open and when the next action will happen.
Corellia’s recommendation is to set an internal feedback deadline after each interview and send the candidate an update at the time you agreed. If the team misses that time, send a revised update rather than waiting for a perfect answer.
For a decline, keep the explanation relevant to the assessment and role. For example, distinguish a need for experience operating a system from a broad statement that the person is not technical enough. Do not share another candidate’s information or promise a detailed critique you cannot substantiate.
A recent company interview-process page shows one way of making expectations visible: candidates are told about meeting the team, scheduling flexibility and receiving updates. The useful lesson is to make your own commitments clear enough to follow. [Source 3]
Printable checklist
Use this checklist at the hiring kickoff and again before the decision meeting. A print-ready companion is supplied with this draft.
Role: ____________________ Decision owner: ____________________
Candidate contact: ____________________ Next update: ____________________
Before the first conversation
- [ ] Outcomes, essential skills and responsibilities agreed.
- [ ] Working arrangement and package approved for discussion.
- [ ] One assessment question and owner assigned to each stage.
- [ ] Interview and decision slots reserved.
- [ ] Candidate receives the process, preparation and adjustment contact.
After each stage
- [ ] Evidence recorded against the agreed criteria.
- [ ] Any open question has a named owner.
- [ ] No repeated assessment without a specific reason.
- [ ] Candidate receives the agreed update and next step.
Before an offer or decline
- [ ] Decision made against the original brief.
- [ ] Package and conditions checked by the responsible person.
- [ ] Outstanding candidate questions recorded and assigned.
- [ ] Written outcome and follow-up arrangements ready.
- [ ] Process notes stored appropriately.
Questions founders ask
Does every role need all these stages?
No. Combine stages where one conversation can produce the necessary evidence. Keep the assessment criteria clear even when the format is shorter.
What if a candidate needs more time?
Agree a workable schedule. A planned process should accommodate availability and adjustments rather than turn the timetable into a test of commitment.
Should we add another interview when the team is split?
Only if it answers a specific unresolved question. First check whether the disagreement is about evidence, the criteria or the role itself.
What if nobody can assess the technical work?
Bring in a credible technical assessor before starting the search. Agree the mandate with them so their assessment tests the role you need to fill.
Can the practical task use AI tools?
Yes, if the format and criteria allow it. State the policy in advance and assess explanation, verification and judgement as well as the output.
When should compensation come up?
Discuss the approved range and package structure in the first conversation. Use the final stages to resolve detail rather than reveal a major mismatch.
Sources
Sources checked 31 October 2026. The timetable, session lengths and checklist are Corellia’s recommended planning framework.
- Structured hiring guide: requirements, scorecards, interview planning and feedback responsibilities.
- Acas, interviewing job applicants: UK interview preparation, adjustments, next steps and work trials.
- Published company interview process: an example of explaining candidate communication and team access.
If you want to map this process to your next technical hire, Start a conversation.