Book a strategy call
Back to glossary
Hiring Process

What is an interview?

Written by
Yotewo Team
Reviewed by
Last updated
October 26, 2026

An interview is a conversation used to assess whether an engineer’s experience, skills and approach match a role. It also gives the engineer an opportunity to understand the project, ask questions and decide whether the engagement meets their expectations.

What is an interview?

An interview is a conversation used to assess whether an engineer’s experience, skills and approach match a role. It also gives the engineer an opportunity to understand the project, ask questions and decide whether the engagement meets their expectations.

In staffing, interviews help both sides explore how they would work together before making a commitment.

What does an interview mean in staffing?

Interviews connect an engineer’s background with the practical requirements of your project. They explore what the engineer has done, how they approach problems and what they could take responsibility for within your team.

A staffing company may conduct interviews as part of its vetting process. Clients can then hold their own interviews to discuss the specific role, technical environment and working arrangements.

These conversations serve different purposes: vetting assesses an engineer’s capabilities, while client interviews explore suitability for a particular engagement.

What should a client interview process include?

At Yotewo, we recommend a maximum of three client interviews per engineer:

  • Short introduction: Introduce the project, discuss relevant experience and establish whether the role interests both sides.
  • Technical interview: Explore the engineer’s knowledge, problem-solving approach and experience with challenges relevant to the role.
  • Closing call: Align on responsibilities, working arrangements and expectations before moving forward.

Each conversation should answer a distinct set of questions. Plan what you need to learn at each stage so the engineer can prepare and your team can make an informed decision.

  • For example: a technical discussion might explore how an engineer investigated a difficult issue, considered alternative solutions and checked the outcome. Follow-up questions can clarify their personal contribution and reasoning.

Match the depth of the discussion to the role’s seniority. For positions involving wider ownership, explore how the engineer handles uncertainty, explains decisions and coordinates work with others across the wider project team.

Why do interviews matter?

Interviews help clarify whether an engineer’s experience matches the work you need completed. They also create space to discuss communication, collaboration and the level of independence the role requires.

For engineers, understanding the project’s goals, challenges and team structure helps establish realistic expectations. Both sides can raise questions about workload, priorities and responsibilities before the engagement begins.

A focused process also respects everyone’s time. Additional conversations are most useful when they address a specific unresolved question.

How can you make interviews effective?

  • Define the role: Agree on essential skills, responsibilities and the level of ownership required before interviewing.
  • Prepare the engineer: Share the interview format, topics and any preparation needed in advance.
  • Ask relevant questions: Explore examples connected to the work the engineer would actually perform.
  • Use consistent criteria: Ask the same core questions and assess answers against agreed expectations for the role.
  • Explore the reasoning: Ask what the engineer decided, why they chose that approach and what they learned.
  • Allow questions: Give engineers time to understand your team, project and expectations.
  • Agree on next steps: Explain what happens after the interview and provide timely feedback.

Avoid repeating the same assessment across several calls. When multiple colleagues are involved, agree who will cover each topic and record observations against the role requirements.

How Yotewo approaches interviews

We offer engineers from mid-level upwards. Our vetting process has five stages, with the final three conducted as interviews: one technical interview and two non-technical interviews.

You can also interview engineers for your own project. There is no limit on the number of client interviews, although we recommend a maximum of three per engineer.

Share your role requirements and the topics you want to cover so discussions can focus on what matters to your team.

FAQ

How many interviews can I run?

Unlimited, but we recommend a maximum of three interviews per engineer: a short introduction, a technical interview and a closing call to align on expectations.

How many interviews do you run?

Our vetting process has five stages. The last three are conducted as interviews: one technical and two non-technical. These are separate from any interviews you conduct for your project.

What is the difference between technical and non-technical interviews?

Technical interviews explore engineering knowledge and problem-solving. Non-technical interviews explore areas such as communication, collaboration and working expectations. Both can use examples from previous projects.

What should I cover in the closing call?

Confirm responsibilities, availability, working hours, communication arrangements and what successful delivery would look like. Address any remaining questions about the engagement before agreeing on next steps.

Does every interview need a practical task?

No. Choose the format around what you need to assess. A discussion of previous work may be useful; a practical exercise can help when you need to observe a relevant skill.