Skip to content
KubeForge

Expert-led live interviews

Technical interviews run by engineers who do the work.

A structured, role-specific interview conducted by an experienced infrastructure engineer, with a scorecard and written recommendation you can act on.

Every interview includes

  • An interview plan agreed with you before the first candidate
  • Role-specific questions and practical scenarios
  • Follow-up questions based on the candidate's answers
  • A scorecard against standard criteria
  • Written feedback and a hiring recommendation

What we cover

Interview rounds designed around the role

We do not use a generic question bank. Each plan is built from the role, the seniority and the technologies you run.

Role-specific design

A plan for a Platform Engineer looks different from one for an SRE or a Cloud Engineer.

Troubleshooting rounds

Talk-through scenarios: a failed rollout, a node going NotReady, a noisy alert, a slow pipeline.

Architecture rounds

Cluster topology, multi-tenancy, GitOps flows, observability design and failure modes.

Standard criteria

Every candidate is scored against the same rubric so results are comparable.

Calibrated to level

Expectations differ for junior, senior and lead engineers, and we score accordingly.

Consolidated reports

Interviewer notes, scores and recommendation, combined with lab results if used.

Duration

45, 60 or 90 minutes

Choose a format per role. Durations are configurable for your process.

45min

Focused screen

One troubleshooting scenario and targeted follow-ups. Suited to junior and mid-level roles or an early-stage screen.

60min

Standard interview

Troubleshooting round plus a design or operations discussion. The default for most mid and senior roles.

90min

In-depth interview

Troubleshooting, architecture and incident-leadership rounds. Suited to senior, lead and architect roles.

Evaluation criteria

A scorecard your hiring panel can compare

Each area is scored on a defined scale with written evidence. The recommendation explains the reasoning, not just the outcome.

  • Troubleshooting method

    Structured investigation, use of evidence, narrowing the problem space.

  • Technical depth

    Accurate understanding of the systems involved, beyond surface-level commands.

  • Architecture & trade-offs

    Sound design choices with clear reasoning about cost, risk and operability.

  • Operational judgement

    Safe change practices, blast-radius awareness, validation and rollback.

  • Communication

    Explains reasoning clearly, asks good questions, and is honest about gaps.

Process

From request to recommendation

  1. 01

    Send a request

    Role, seniority, technologies, number of candidates and preferred duration.

  2. 02

    Agree the plan

    We confirm the interview plan, rubric and an interviewer with matching experience.

  3. 03

    Interviews take place

    Scheduled with each candidate over video, in a time zone that suits them.

  4. 04

    Receive the report

    Scorecard, written feedback and a hiring recommendation for each candidate.

Request interviews

Tell us about the role

We will reply to confirm interviewer availability, the plan and pricing. Nothing is scheduled until we confirm with you.

Who are the interviewers?
Practising infrastructure engineers with production experience in the technologies being assessed. We match interviewer experience to the role.
Can our engineers observe?
Yes. A member of your team can join as an observer, or you can receive the report only.
Do you record interviews?
Only with the candidate's explicit consent and your agreement. By default we keep written notes, not recordings.
Required technologies *

We use these details only to respond to your inquiry. See our privacy policy.