how it works
Technical screening, explained plainly.
A short document on how referred.tech screens engineers, why we record every interview, and why that recording gets reused instead of thrown away.
One interview. Recorded, not repeated.
Most technical hiring makes engineers prove the same thing over and over, to a different stranger, on a different whiteboard, every single time. We think that's a waste of everyone's attention.
So we do it differently: every engineer in our network sits one real technical interview with us. We record it. That single conversation becomes their standing signal—shown to every employer we think it's relevant for, not filed away after one rejection.
Interview once. Get considered many times.
We explore strengths, not run a standardized test.
We push back against the standardized interview. There's no fixed script and no universal rubric applied the same way to everyone. Each conversation goes wherever an engineer's real strength is — a system they designed, a hard tradeoff they made, something they debugged under pressure — because that's where the signal actually lives.
Engineers are shaped by their experience, not interchangeable. We're not looking for a generic engineer-shaped resource who can pass a standard test — we're looking for pointy people: people with a sharp, particular strength, and the right specific experience for the problem you're facing.
Do the work once. Let it open more than one door.
You sit one focused screen with us, on your schedule. We turn it into a structured writeup plus the recording itself, and—with your permission—put it in front of every role in our network that actually fits what you're good at.
No repeating your life story to five different recruiters. No re-proving the same fundamentals every time a new opportunity comes up.
Watch the interview. Skip the re-screen.
Instead of a stack of resumes and a prayer, you get a short list of engineers who've already passed a real technical conversation—recording included, so you can judge the signal yourself instead of trusting a summary.
Most teams that work with us drop an entire internal screening round. Your own interviews become about fit and motivation, since basic competence is already established.
Fair questions, straight answers.
- Why record the interview instead of sending notes?
- A recording is the primary source. Notes are our summary of someone's judgment—the recording lets you form your own.
- Isn't reusing one interview across employers impersonal?
- For the engineer, it's the opposite: one good conversation instead of five nearly-identical ones.
- What if a role needs something more specific?
- The recorded interview is the baseline. A role with unusual requirements gets a short, targeted follow-up—not a full re-screen from zero.
- How do you keep this from turning into algorithm puzzles anyway?
- Each screen is built around real work for the role's level and stack, and practicing engineers periodically review the screens to keep them honest.
- Isn't one interview format still kind of standardized?
- The fact that a conversation happens is consistent — the content isn't. There's no fixed set of questions or a rubric graded the same way for everyone. Each interview follows that engineer's specific strengths and experience, because that's what actually predicts fit for a given problem — not a repeatable score.