Most people read job descriptions the wrong way — they scan it, feel either confident or overwhelmed, and move on. This guide teaches you to read a JD like a strategist: extracting what actually matters, identifying your genuine fit, and building evidence for every requirement before you walk in the room.
After working through this guide, you will know exactly which parts of a JD are critical, which are negotiable, what the employer is really looking for behind the listed requirements — and how to match your own experience to what they need, even when it doesn't look like an obvious fit.
The difference is what you do next.
01 / 07
THE PROBLEM
Why job descriptions mislead most candidates
A job description is a wish list written by a committee, filtered through HR, and approved by someone who has never done the job. Reading it literally will either inflate your confidence or destroy it — neither of which is useful.
Most job descriptions are written by HR professionals or hiring managers working from a template. They list every possible skill they could want, every qualification that would be ideal, and every responsibility the previous person in the role handled. Very rarely does the person they hire tick every box.
THE RESEARCH FACT
Studies consistently show that men apply for roles when they meet 60% of the requirements. Women and younger candidates typically only apply when they meet 90–100%. The people who get hired are not the ones who meet every requirement — they are the ones who can best demonstrate the requirements that actually matter. This guide teaches you to identify which ones those are.
The second problem is that most candidates read the JD once, conclude they are either a great fit or not a fit, and stop there. They do not ask the more important question: for each requirement, can I give a real, specific example? That gap — between "I have this skill" and "I can prove I have this skill" — is where most interviews are won or lost.
WHAT THIS GUIDE TEACHES YOU
How to break a JD into what is essential versus what is negotiable. How to read the language an employer uses to understand what they really value. How to map your own experience — including experience that doesn't look obvious — to what they need. And how to talk about that mapping confidently in the interview room.
THE MOST COMMON MISTAKE
Reading the JD once, deciding "I'm qualified" or "I'm not qualified," and moving on. A JD is not a checklist to evaluate yourself against. It is a document to decode — to understand what the employer actually needs versus what they think they want to list.
02 / 07
UNDERSTANDING THE DOCUMENT
The anatomy of a job description
Every JD has the same basic structure — but not every section carries equal weight. Here is what each part is actually telling you.
Below is an annotated example of how to read a typical JD. Each line is labelled with what type of requirement it actually represents.
EXAMPLE JD — FINANCE EXECUTIVE, OIL AND GAS COMPANY
RESPONSIBILITIES — read carefully
Prepare monthly management accounts and variance analysis
Core duty
Support budgeting and forecasting processes
Core duty
Liaise with external auditors and manage audit process
Experience needed
Contribute to process improvement initiatives
Nice to have
Support ad hoc financial analysis as required
Catch-all — ignore weight
REQUIREMENTS — most important section
Degree in Accounting, Finance or related field
Essential
Minimum 3 years relevant experience
Often negotiable
Proficiency in Microsoft Excel
Essential
Experience with ERP systems (SAP preferred)
"Preferred" = nice to have
Strong analytical and communication skills
Always listed — prove it
Ability to work independently and in a team
Always listed — prove it
CULTURE SIGNALS — read between lines
"Fast-paced environment"
High workload, expect pressure
"Self-starter who can work with minimal supervision"
Manager may be hands-off
"Strong team player"
Collaborative culture expected
THE KEY INSIGHT
The responsibilities section tells you what you'll do. The requirements section tells you what they think they need. The culture signals — usually embedded in phrases throughout the JD — tell you what it's actually like to work there. All three sections require different reading strategies.
WHAT "PREFERRED" ACTUALLY MEANS
Any requirement labelled "preferred," "desirable," or "an advantage" is genuinely optional in the hiring manager's mind. They listed it because it would be nice — not because they will reject you without it. Focus your energy on the requirements with no softening language. Those are the non-negotiables.
03 / 07
THE METHOD
The 5-step JD decoding method
This is the process to work through every time you find a role worth applying for. It takes 20–30 minutes done properly. It is worth every minute.
1
Read the whole JD once without a pen
Get the overall picture first. What kind of company is this? What does this role seem to be about? How do you feel after reading it — energised or drained? That feeling is data. Don't analyse yet — just absorb.
2
Separate essential from desirable
Go through the requirements section and mark each one: Essential (no softening language), Preferred (says "preferred," "desirable," "an advantage"), or Hidden filler ("strong communication skills," "team player" — everyone lists these, they mean little on their own). Focus your preparation on Essentials only.
3
Identify the top 3–5 things they actually need
Look for repetition — if something appears in both the responsibilities AND the requirements, it is clearly important. Look for specificity — the more specific a requirement, the more it matters. Ask yourself: if I could only demonstrate 3 things in this interview, what would make them say yes? Those are your top 3–5.
4
For each essential requirement — find your evidence
This is the most important step. For every essential requirement, you need a real, specific example from your own experience. Not "I have experience in X" — a story: when did you use this skill, what was the situation, what did you do, what happened? If you cannot find an example, that is a genuine gap worth acknowledging.
5
Read the culture signals and decide if it fits you
Look for phrases that describe the work environment: "fast-paced," "self-starter," "collaborative," "results-driven." These are signals about what it is actually like there. Ask yourself honestly — does this environment suit how I work? A bad culture fit will make you miserable even if you get the job. This step is often skipped. Don't skip it.
HOW LONG THIS SHOULD TAKE
20–30 minutes for a thorough decode on your first few attempts. With practice it gets faster. The Decoder Workspace in Section 7 of this guide is designed to help you work through these steps for any role you are preparing for.
04 / 07
ADVANCED READING
Reading between the lines
What a JD says and what it means are often two different things. This page teaches you the language patterns to watch for and what they signal about the role and the company.
Once you can read the explicit requirements, the next skill is reading the implicit ones — the things an employer communicates without saying directly. These signals tell you what kind of person they are really looking for, what the culture is actually like, and sometimes, what problems they are trying to solve by hiring someone.
What the JD says
What it usually means
What to prepare
"Fast-paced environment"
High workload. Deadlines are real. You may be under-resourced.
A STAR example of working under sustained pressure without dropping quality.
"Self-starter" or "minimal supervision"
The manager may not be hands-on. You will need to figure things out independently.
A STAR example of taking initiative without being asked. Show you can operate without hand-holding.
"Wearing multiple hats"
The role may be broader than the title suggests. Small team, high expectations.
Show range. Multiple examples across different skill areas. Adaptability is the key quality here.
"Exciting opportunity" or "dynamic team"
May signal frequent change, uncertainty, or a team in flux. Interpret carefully.
Ask directly in the interview: "What does the team look like right now and what are its biggest challenges?"
"Stakeholder management"
You will deal with difficult people who have conflicting priorities. This is a warning and a requirement.
A STAR example of managing up, sideways, or across — not just managing down.
"Detail-oriented"
Errors have real consequences in this role. They have had problems with this before.
A STAR example where your attention to detail caught something important or prevented a problem.
"Strong communication skills"
Always listed, but the weight varies. Check whether it appears in Responsibilities too — if so, it matters more.
Prepare an example where communication was genuinely central to an outcome, not just incidental to it.
Salary range is missing
Either they are flexible, they don't know yet, or they want to see your expectations before revealing theirs.
Research the market rate for this role in Brunei before the interview. Come with a range ready.
THE QUESTION BEHIND THE JD
Behind every JD is a problem the company is trying to solve. Someone left. The team is growing. A project needs specific expertise. A function is struggling. The best candidates understand this and position themselves as the solution — not just as someone who meets the requirements. Ask yourself: why does this role exist right now? What problem am I being hired to solve?
05 / 07
YOUR EXPERIENCE
Mapping your experience to the JD
This is where most candidates go wrong. They know what they have done, and they know what the JD requires — but they never explicitly connect the two. This section shows you how.
The mapping process has three steps: identify the requirement, find your evidence, and then articulate the connection clearly. The last step is the one most people skip — they assume the interviewer will make the connection. They won't. You have to make it for them.
THE GOLDEN RULE OF MAPPING
Never assume the interviewer will connect your experience to their requirement. If the JD asks for "experience managing stakeholder relationships" and your example involves coordinating between departments — you must say explicitly: "This is directly relevant to your stakeholder management requirement." Make the connection verbal. Every time.
Here is how a mapping table looks when done properly for a candidate applying to a finance role:
JD Requirement
Your evidence
How to frame the connection
Match
Prepare monthly management accounts
Produced monthly P&L and variance reports for a BND 15M contract for 3 years
"I've done exactly this — monthly management accounts including variance analysis against budget, for a major contract. I can show you the process I built."
Strong ✓
Experience with ERP systems (SAP preferred)
Used Zoho Books and built Power BI dashboards connected to the API. No SAP experience.
"I haven't used SAP specifically, but I've worked extensively with cloud accounting systems and built integrated reporting. I'm confident the transition would be fast."
Partial ~
Minimum 3 years relevant experience
8 years in finance and operations across oil and gas
Let the CV speak. Confirm in the interview: "I have 8 years of relevant experience across finance and operations."
Strong ✓
Strong analytical skills
Built a financial model for a potential acquisition, conducted due diligence for M&A
"Strong analytical skills — I'd point to the financial modelling work I've done for M&A evaluations as the clearest evidence of that."
Strong ✓
Degree in Accounting or Finance
No specific finance degree — degree in a related field
"My degree is in [field], but my professional experience and the depth of financial work I've led speaks directly to the technical requirements of this role."
Partial ~
WHAT THE TABLE SHOWS YOU
A "Partial" match is not a disqualifier — it is a preparation signal. For every partial match, you need a prepared bridge: how you acknowledge the gap honestly while redirecting to what you do bring. Interviewers respect candidates who are self-aware about gaps far more than candidates who pretend gaps don't exist.
TRANSFERABLE EXPERIENCE IS REAL EXPERIENCE
If you have done something similar in a different industry, different company, or different context — it counts. The skill is the same. The wrapper is different. Your job is to name the skill, give the evidence, and explicitly connect it to what they need. "I haven't done this in oil and gas specifically, but I've done it in [context] — the underlying skill is identical and here's what I did."
06 / 07
HANDLING GAPS
When you don't fully match — what to do
Almost nobody fully matches a JD. The question is not whether you have gaps — it is how you handle them. This page gives you the exact language to use.
There are three types of gaps a candidate might face: a missing qualification, a missing experience, or a missing skill. Each requires a different approach.
THE RIGHT MINDSET
A gap is not a disqualifier — it is a data point. The interviewer is trying to assess risk. Your job is to reduce their perceived risk by being honest about the gap, showing what you bring instead, and demonstrating that the gap is bridgeable. Hiding a gap or pretending it doesn't exist creates far more risk than acknowledging it directly.
Type of gap
What not to say
What to say instead
Missing qualification e.g. degree they asked for
"I don't have that degree but I'm a fast learner." (Too vague.)
"I don't hold that specific qualification, but I've been doing this work for [X] years and my track record in [specific area] speaks directly to what you need in this role."
Missing industry experience e.g. never worked in oil and gas
"I haven't worked in this industry but I'm keen to learn." (Sounds like a risk.)
"My background is in [industry], where I did [specific thing]. The financial/operational/technical skills are directly transferable — and I've done significant research into how they apply in your context."
Missing years of experience e.g. they want 5 years, you have 2
"I only have 2 years but..." (The word "only" undermines you.)
"I have 2 years of experience, but in that time I've [specific achievement that signals above-average depth]. I'd like to show you what that looks like in practice."
Missing specific tool or system e.g. SAP, specific software
"I haven't used SAP." (Full stop — leaves the gap open.)
"I haven't used SAP specifically, but I've worked extensively with [similar tool] and built [specific capability]. Learning new systems quickly is something I've demonstrated — I picked up [tool] in [timeframe]."
THE ONE GAP YOU CANNOT BRIDGE
If a requirement is genuinely essential — a license, a mandatory qualification, a specific certification required by law — do not apply without it. These are non-negotiable regardless of how strong your other credentials are. Every other type of gap is manageable with the right framing.
WHEN TO RAISE A GAP
Proactively, before they find it — not defensively after they ask. Raising it yourself signals confidence and self-awareness. "I want to be transparent about one area — I don't have [X]. What I do have is [Y], and here's why I believe that covers what you actually need." This approach consistently performs better than hoping they won't notice.
07 / 07
DECODER WORKSPACE
Decode your target JD here
Work through this for every role you prepare for. Fill in each section before you write a single answer in your Answer Bank.
THE ROLE
STEP 1 — FIRST IMPRESSION
BEFORE ANALYSING
After reading the JD once — what is your gut feeling? What excites you? What concerns you? Write it here before you start breaking it down analytically.
STEP 2 — THE TOP 5 THINGS THEY ACTUALLY NEED
HOW TO IDENTIFY THEM
Look for requirements that appear in both the responsibilities AND requirements sections — that repetition signals importance. Look for specificity. Ask: if I could only demonstrate 3–5 things in this interview, what would make them say yes?
STEP 3 — MAP YOUR EXPERIENCE TO EACH REQUIREMENT
HOW TO USE THIS SECTION
For each essential requirement, write the evidence you have — a real example, project, or situation. Then write exactly how you would connect it verbally in the interview. Be specific. "I have experience in X" is not evidence. A real example is evidence.
Match strength:
Match strength:
Match strength:
STEP 4 — CULTURE SIGNALS
WHAT TO LOOK FOR
Go back through the JD and find the phrases that describe the environment or type of person they want. Write them here and note what they signal to you.
STEP 5 — MY GAPS AND HOW I'LL BRIDGE THEM
BE HONEST HERE
A gap you acknowledge and prepare for is far less dangerous than one you ignore. For each gap, write how you will address it honestly in the interview — using the language from Page 6 of this guide.
BEFORE YOU GO INTO THE INTERVIEW
Review this workspace the night before. Your goal is to be able to connect at least one real example to each of the top 5 requirements you identified. If you can do that, you are more prepared than most people who walk into that room.