Why this matters
Most candidates skim the posting once and then prepare "in general". They burn time on topics that never come up and miss the ones that surely will. A job description is the employer's priority list. If you can read it, you prepare with precision.
What to extract
Stack and tools. Every named technology is a potential topic. If the role lists Postgres, expect questions on indexes, transactions, query plans. Write down the whole stack and mark what you know cold versus only superficially.
Wording about the team and process. "Fast-growing team" → expect questions about working under ambiguity and onboarding. "Close work with product" → prepare stories about working with stakeholders.
Seniority of the role. A senior posting means questions about decision-making, tech debt, and influence on others. Mid-level is about autonomy. Note the verbs — "design", "mentor", "own" — they signal your scope of responsibility.
Repeated words. If "reliability" or "scaling" appears three times, it is the team's pain. Prepare a relevant story.
Turn it into a plan
- List the 5-7 most likely topics in descending order.
- For each topic, write one point you want to make sure you land.
- For each "soft" phrase, pick a story from your experience.
Checklist
- Whole technical stack written down
- Weak spots flagged for review
- Signals about team and process identified
- A story matched to each signal
- A list of questions for the employer ready (see separate guide)