Roles
What a listing asks for, and what it is actually screening for.
Every role page is the same four things: the requirements that keep appearing, what each one is really testing, a sentence that would genuinely prove it, and the requirement nobody writes down. Written from real listings, not generated from a template.
Backend engineer
Backend listings are written as a stack and read as a set of problems. The language is negotiable far more often than the listing admits; what is not negotiable is evidence that you have kept something running that other people depended on.
5 requirements →Data engineer
Data engineering listings read as a tool list and screen as a judgment test. The tools change every two years; the thing a team is buying is somebody who has been woken up by a pipeline that failed silently and designed so it could not happen again.
5 requirements →Frontend engineer
A framework is the easiest thing on a frontend listing to satisfy and the least useful thing to screen on. What distinguishes candidates is whether they have shipped something to people whose phones and connections they did not control.
5 requirements →Platform engineer
Platform listings name tools because tools are easy to name. What they are buying is somebody who makes other engineers faster without becoming the person every change has to go through.
5 requirements →Analytics engineer
The job exists because two dashboards disagreed about revenue. What a listing screens for is whether you can make a number mean one thing across a company — which is a political skill as much as a technical one.
4 requirements →Product manager
No role is harder to evidence from a CV, because the deliverable is a decision and the decision is invisible. The way through is to name the decision, the evidence you had, and what happened.
4 requirements →Product designer
Design hiring is moving away from the polished case study, because the polish is now free. What survives is the reasoning — and reasoning is a sentence with a date, not a Dribbble shot.
5 requirements →Engineering manager
An engineering manager’s output is the team, which makes it the hardest role to evidence and the easiest to overstate. The useful proof is always about a specific person or a specific decision.
5 requirements →
Reading the list is step one. Proving it is step two.
Tell the agent what you have done and every sentence becomes a claim with a date. Then match yourself against a real listing and read what is still unmet.