
Structured interview questions
for engineering roles — without the gotchastied to a rubricbuilt for the rolein under a minute.
Assay generates the questions, the rubric, and the scorecard — built for the role and grounded in I/O psychology. $69 per role.
Built on science, not gut feel.
Every Assay output is grounded in industrial/organizational psychology — the science of what actually predicts performance at work. The structure of each question, rubric, and scorecard draws on decades of research on what makes an interview predictive, not on one person’s judgment of “what’s a good question.”
Interviews are broken.
Teams waste hours building one-off questions, end up with inconsistent signal, and fall back on gut feel.
Hours of prep, every cycle
Making one hire eats 30–40 hours of engineering time — and the questions, rubrics, and scorecards behind it get rebuilt from scratch every cycle.
Inconsistent signal
Different interviewers ask different things. The candidate’s score depends on who they got.
Decisions on vibes
Without a rubric, “hire / no-hire” is a gut call. Bias creeps in.
The wrong puzzles
Coding gotchas filter for what doesn’t matter, while real engineering skills go unseen.
How Assay works.
From role description to interview-ready in minutes.
- 1
Describe the role.
Title, key responsibilities, and what “good” looks like at your company.
- 2
Assay builds the guide.
Structured questions for each dimension, a leveled rubric, and a ready-to-use scorecard.
- 3
Run consistent interviews.
Every candidate gets the same questions, scored the same way. Decisions become evidence-driven.
What you actually get.
Every Assay output is built around the role you describe. Below are slices of what we generated with Assay for our own Senior Backend Engineer role — from the job description through the interview guide.
Senior Backend Engineer
Own the design and operation of the services behind our hiring platform: a Next.js application backed by Postgres and a Python analysis service. You’ll make schema, API, and reliability decisions that the rest of the team builds on.
What you’ll do
- Design and evolve Postgres schemas and the APIs over them, with row-level security as a first-class constraint
- Own reliability for a small fleet of containerized services — deploys, observability, and incident response
- Review code across the backend surface and raise the bar it sets
What we’re looking for
- Depth in a production Postgres — schema design, query performance, migration discipline
- Experience running containerized services in a small-team setting, where you are the on-call
- Judgment about when to build, when to buy, and when to delete
Senior Backend Engineer
We’re a small team building hiring tools that treat candidates like people and interviews like evidence. You’d be the engineer who owns the backend: the schemas, the services, and the calls that keep both honest. Small team, real ownership, no puzzle interviews — we’ll ask you to review code, not invert a binary tree on a whiteboard.
One price. Real outputs.
No subscription. No credits. Pay per role.
- One complete interview guide
- Structured questions across each dimension of the role
- A leveled rubric for every question
- A ready-to-use scorecard for interviewers
- Fully editable — tweak, share, and reuse