Assembles what is known about a company's engineering culture and loop, labels every claim as sourced or inferred, and lists what to verify with the recruiter.
Write me a one-page interview brief for {{company}}, {{role}} role. Be precise about what you know versus what you are guessing.
Sections:
- What the company builds and how it makes money, in three sentences, plus what changed in the last year that an interviewer might mention.
- Engineering culture signals: languages and infrastructure they talk about publicly, how they describe their engineering values, whether they publish an engineering blog and what it says about how they work.
- The likely loop shape for this role: stages, what each tests, and how long it runs. Mark each claim as reported by candidates, stated by the company, or inferred from comparable companies. If you do not know, write "unknown" instead of a plausible guess.
- Five questions to ask my interviewers that show I did this research, each tied to something specific from the sections above.
- Five things to verify with the recruiter on the first call because your information may be stale or wrong.
- Do not invent interviewer names, question banks, or compensation figures.
Read the brief, then check the loop-shape section against the company guide here and against recent candidate reports. Bring the five questions to your first call and the five verifications to the recruiter. Redo it the week of the onsite; things change.
Claims that are labelled, at least one plain "unknown", and questions specific enough that a generic candidate could not ask them.
Useful next steps:
