Reqa runs either a Conversation or a Practical Case and gives you a clear report: what the candidate demonstrated, what supports those conclusions, and what still needs checking.
Role brief
Backend Engineer
// Practical case
Design an idempotency mechanism for a distributed payment system.
Interview excerpt
#14 · 02:16
“With Temporal in Go, the main challenge was activity idempotency…”
See in the interview →Linked evidence
“I went with an idempotency key stored in the database…”
Trade-off · High confidence
PDF report
Thomas M. · Backend Engineer
What the evaluation establishes
Solid on API design and data consistency in the database.
« I went with an idempotency key stored in the database to prevent the same operation from being processed twice. »
Hands-on experience observed; autonomy on complex migrations still to confirm.
This criterion was not covered during this evaluation.
Still to verify — ability to secure a migration without interruption.
Follow-up question — How would you secure a data migration without service interruption?
Still to verify — ability to secure a migration without interruption.
Follow-up question — How would you secure a data migration without service interruption?
Shows the candidate's background, experience, and stated skills.
A Conversation or Practical Case gathers technical evidence against the criteria you want to observe.
Shows what is established, what supports it, and what still needs checking.
Start from the role and what you actually want to observe.
Backend Engineer — criteria
Use a Conversation to dig into real experience, or a Practical Case to observe reasoning in context.
Conversation
Practical Case
or
Reqa links conclusions to the evidence collected and makes clear what still needs checking.
Each evaluation uses one primary format. Choose it based on what you want to observe; both produce the same structure of conclusions and evidence.
Reqa explores the candidate's decisions, trade-offs, consequences, and how their reasoning changes when the context changes.
Reqa — Why did you choose this approach?
Candidate — We had considered dual writes, but…
Reqa — What made you rule that option out?
The candidate works through a job-related situation, makes a decision, and explains how they justify it against the constraints.
Situation
Your payment service may replay an operation after a restart. How would you prevent it from being processed twice?
The report separates what is established from what is not. For each conclusion, you can see the evidence supporting it and return to its source.
See a sample reportWhat the evaluation establishes
A status and qualitative conclusion for each criterion.
What supports the conclusion
A quote or other evidence collected during the evaluation.
The original context
The linked passage lets you return to the material behind the conclusion.
What still needs checking
The report may state what remains uncertain and provide a follow-up question.
SAMPLE REPORT
API design and data consistency mastered on this project.
I went with an idempotency key stored in the database to prevent the same operation from being processed twice. »
Exact evidence
« I went with an idempotency key stored in the database to prevent the same operation from being processed twice. »
Trade-off · High confidence
Source · interview excerpt
— Interview, minute 12: "… stored in the database, and we check it at the start of every run."
This criterion was not covered during this evaluation.
Still to verify — Ability to secure a zero-downtime migration.
Follow-up question
How would you secure a data migration without service interruption?
What the evaluation establishes
A status and qualitative conclusion for each criterion.
What supports the conclusion
A quote or other evidence collected during the evaluation.
The original context
The linked passage lets you return to the material behind the conclusion.
What still needs checking
The report may state what remains uncertain and provide a follow-up question.
SAMPLE REPORT
Conclusion
API design and data consistency mastered on this project.
Exact evidence
I went with an idempotency key stored in the database to prevent the same operation from being processed twice. »
Source · interview excerpt
— Interview, minute 12: "… stored in the database, and we check it at the start of every run."
This criterion was not covered during this evaluation.
Still to verify — Ability to secure a zero-downtime migration.
Follow-up question — How would you secure a data migration without service interruption?
01 · Tool used
02 · Reqa digs deeper
Why this choice? What changes under a new constraint?
03 · New evidence
The answer adds more material.
04 · Conclusion
The report incorporates the new evidence.
Depending on the context, documentation, research, or AI tools may be allowed. Reqa does not infer competence from their use alone; it digs into what the candidate can explain, control, and adapt.
The tool is not the evidence.
Reqa sits before the in-depth technical interview, whether you are hiring for your own team or for a client.
Before bringing in a consultant or technical expert
Recruiters get a structured first technical read before involving an expert or presenting the candidate to a client.
Before involving your engineering team
Reqa prepares a first technical read when only a few people can handle early technical interviews.
Import your DOCX template and the candidate's CV as PDF or DOCX. Reqa structures the information in your format, lets you review and adjust the content, then exports the profile as DOCX or PDF after the anonymisation step.
See a sample profileYour organisation's DOCX template provides the structure for the generated document.
Information extracted from the CV is placed into the profile before approval.
The workflow lets you prepare the client-facing version before export.
Thomas Martin
Backend Engineer
Professional experience
EDUCATION
Skills
Review
AnonymisationThomas Martin
Backend Engineer
Professional experience
EDUCATION
Skills
ReviewAnonymisationReady to review and send.
Reqa structures the evaluation
Your team decides
Reqa structures the evaluation and its report. It does not decide who to hire.
Important conclusions can be linked back to the evidence supporting them.
The report gives your team material to review, not an automated hiring verdict.
A criterion that was not evaluated is not presented as a weakness.
Starter and Pro for technical evaluations. Solo for Competency Profiles. Enterprise for custom requirements.
For getting started with technical evaluations.
For teams hiring regularly.
For producing Competency Profiles.
Competency Profiles are the main Solo offer. There is no recurring evaluation allowance; 5 evaluation credits are included to try Reqa.
For specific volumes and requirements.
Indicative pricing · Preferential pricing guaranteed for beta partners
No. Reqa runs before the in-depth technical interview. It handles a first technical round and gives your team a report showing what is established, what supports those conclusions, and what still needs checking.
PRIVATE BETA
Reqa is currently available by invitation. Beta partners receive guaranteed preferential pricing.
Invitation only.