Getting Started
Analysing Job Descriptions
Learn how to analyse a job description in five steps so you can understand exactly what the interviewer is looking for. This guide helps you identify key skills, action verbs, examples to prepare, and any red flags before your interview.
Introduction
When preparing for an interview, the job description (JD) is your most valuable guide. By analysing it carefully, you’ll know how to shape your answers to match what the interviewer is looking for.
We’re going to cover 5 steps to extract key information from a JD:
Identify the key skills
Look for action verbs
Rewrite the JD in your own words
Prepare skills examples
Find red flags
To see these steps in action, let’s use an example job description for the role of Software Engineer.
Job Description (Example)
Software Engineer
What you’ll be doing:
Designing and building scalable backend systems and APIs
Collaborating with cross-functional teams including Product and Data
Writing clean, maintainable, and well-tested code in Python
Working in a fast-paced environment where priorities can shift quickly
Owning features from idea to production
What you’ll need:
3+ years of backend development experience
Strong knowledge of Python and SQL
Experience working with distributed systems or cloud infrastructure (e.g. AWS, GCP)
Ability to work independently and take ownership of projects
Strong communication skills and the ability to explain technical ideas clearly
Step 1: Identify the Key Skills
Almost every JD focuses on a mix of technical skills, soft skills, work style and business context. Highlight the most important skills for each category.
Technical Skills | Soft Skills | Work Style |
|---|---|---|
|
|
|
Step 2: Look for Action Verbs
Most responsibilities in the JD start with action verbs. These verbs hint at:
the type of work you’ll be doing
the type of interview questions to expect
Verbs | You'll be… | Prepare… |
|---|---|---|
Design, develop, implement | Building systems, processes, etc… | Deep technical questions — systems/code walkthroughs |
Collaborate, partner, facilitate | Working with other teams or roles | Teamwork and communication stories (behavioural) |
Own, lead, deliver | Taking responsibility from start to finish | Examples of ownership and initiative |
Optimise, improve, refactor | Improving existing systems or processes | Stories about improving performance, scaling or efficiency |
Mentor, support, coach | Guiding junior teammates | Examples of teaching, mentoring or giving feedback |
Step 3: Rewrite the JD in Your Own Words
Pick 3–5 key bullet points and rephrase them in simpler English. This helps you clearly understand what the role involves and prepares you to talk about responsibilities naturally.
For example, "Work closely with cross-functional teams to delivery features on time."
I'll need to work with people from other teams to make sure deadlines are met.
Step 4: Prepare one example per skill
For each key skill identified in Step 1, write a short story:
What was the situation?
What did you do?
What was the result?
For example, for Python:
Notes:
Recently refactored a messy pipeline
Added unit tests and followed PEP8 style guidelines
Pipeline is now easier to maintain and for new members to jump into
Step 5: Watch out for red flags
Job descriptions can give you clues about company culture.
If a role says you need to “work under pressure”, this might mean the team often has urgent deadlines or a stressful environment.
Use the interview as an opportunity to ask questions and understand what these phrases really mean.
Red flag | What it could mean | What to ask |
|---|---|---|
Work under pressure | Frequent urgent deadlines, possible overtime | Can you tell me how the team managers tight deadlines? |
Fast-paced environment | Constant change, unclear priorities | How do you prioritise tasks when things move quickly? |
Self-starter | Minimal support, no onboarding | What kind of onboarding is in place for new starters? |
Get full access to English for Tech Interviews
Any questions? Get in touch