Date · Wednesday, 6 May 2026, 13:30 CEST
Hosted by · OPCW
Session page · UNOG learning
Speakers
- Damla Deniz Taskin · Associate Organisational Design Officer, OPCW · Bio
- Milan Jelenkovic · Head, Talent Acquisition, OPCW · Bio
A job description (JD) is a critical document that serves multiple purposes for both organisations and individuals. Understanding job descriptions is essential for everyone. In this session, HR specialists from the OPCW will explain the role and value of job descriptions, demonstrate how to interpret them through a live breakdown, and help you navigate them with ease. The session will also include practical tips on how to effectively position yourself for a specific JD.
Key takeaways
- Become a “marathon runner”: read the JD, break it down using the color-coded method (action verbs → context → working relationships → accountabilities), and then tailor your application to what you found.
- Job search has two phases with different purposes: scan efficiently in the preparatory phase to filter for fit; decode thoroughly in the active phase to craft a relevant application.
- Responsibilities in a JD are listed in order of importance. You don’t need mastery of all of them, focus on the core ones and think about how your past experience speaks to them.
- Recurring technical or legal terms in a JD are not noise. they define the operating framework of the role. Look them up; use them in your motivation letter and interview prep.
- Create a two-column comparison table: JD requirements vs. your profile. Cover education, experience, skills/competencies, and key duties and working relationships separately.
- Focused job search = higher job satisfaction. Exploratory job search = more offers. Haphazard = negative on both counts.
- OPCW does not use AI or ATS keyword filtering. Every application is read by a human. Authenticity and relevance beat keyword optimization.
Damla Deniz Taskin
Damla’s core contribution was a practical framework for engaging with job descriptions as an active, analytical exercise rather than a passive read-through. She opened by classifying job applicants into three archetypes: sprinters, who skim JDs and fire off one-size-fits-all applications; runners, who read the JD but tailor their CV based on assumptions rather than analysis; and marathon runners, who read, break down, and then tailor their application based on what the JD actually says. The entire session was an argument for becoming the third type.
She then described the two phases of a job search: a preparatory phase (scanning vacancies to decide whether to apply) and an active phase (working on the actual application). In the preparatory phase, she recommends scanning the title, the first two or three responsibilities, and the mandatory requirements to quickly assess fit. In the active phase, she introduced a color-coded method for breaking down a JD: first, highlight all action verbs under responsibilities, they reveal what the role actually does; second, ask “what?” to each action verb to uncover the domain and context of the work; third, highlight working relationships (look for phrases like “in collaboration with” or “in coordination with”) to understand who the role interacts with and at what level; fourth, identify accountabilities by looking for words like “ensure,” which signal what the role is ultimately responsible for delivering.
She also shared research on job search strategies: focused searches (targeting a specific role in a specific sector) tend to result in higher job satisfaction, while exploratory searches yield more offers. Haphazard searches, applying broadly with no clear plan, correlate negatively with both. She closed by recommending always saving a local copy of every JD, since vacancy notices can be taken down, and by pointing out that recurring technical or legal terms in a JD (she used Article 10 of the Chemical Weapons Convention as an example) are not incidental, they mark the core framework of the role and should be researched and referenced in the motivation letter.
Milan Jelenkovic
Milan provided the organizational and theoretical backdrop that gives Damla’s practical tools their grounding. He explained that job descriptions are the downstream output of a structured HR process: organizational strategy is translated into workforce implications, which leads to job design, which produces the JD. Understanding this chain of causation helps applicants read JDs not as bureaucratic forms but as expressions of what an organization needs.
He walked through the CIPD’s staged approach to recruitment, job analysis, job description, person specification, and stressed that if these foundational stages are done poorly, every downstream stage (recruitment, selection, performance management) is compromised. Job analysis, he noted, is described in HR literature as “the most fundamental of all HR activities” because everything else depends on it. The three main methods are observation of incumbents, interviews with them, and job analysis questionnaires.
His practical guidance focused on the application stage. He observed that candidates typically over-focus on the person specification (minimum requirements, education, experience) and under-focus on the duties and tasks section. His recommendation: create a two-column comparison table, JD requirements on one side, your profile on the other, covering education, experience, and skills/competencies, and then do the same exercise for the actual duties and working relationships. This forces you to articulate how your experience maps to what the role actually does, not just whether you meet the threshold criteria. He also noted that OPCW does not use AI or ATS keyword filtering, every application is read by a human recruiter, so relevance and authenticity matter more than keyword density.
Frameworks and models
| Name | What it stands for | How to use it |
|---|---|---|
| CIPD Staged Recruitment Model (context, no framework page) | Job analysis → job description → person specification, in sequence. Each stage depends on the quality of the one before. | Understand that a JD is the product of a structured analytical process. Reading it with that lens helps you decode what the organization is actually trying to communicate about the role. (Considered for promotion to a framework page but not promoted: this is HR-side theory, not a tool an applicant runs.) |
| Marathon Runner) | Three levels of engagement with a JD: skim + generic apply / read + adjust by assumption / read + break down + tailor precisely. | Use as a self-check: which category does your current approach fall into? The goal is marathon runner for every serious application. |
| Two-Phase Job Search | Preparatory phase (scan vacancies for fit) and active phase (build a tailored application), each with its own depth and steps. | Use to calibrate how much time to spend on a JD before deciding to apply, and how much once you have decided. |
| JD Color-Coding Method | Four-step breakdown: (1) highlight action verbs, (2) ask “what?” to identify domain/context, (3) highlight working relationships, (4) identify accountabilities (look for “ensure”). | Apply during the active application phase on a separate document. Use a distinct color for each category to make patterns visible across a long JD. |
| JD vs Profile Comparison Table | Two-column working sheet that maps the JD’s requirements and duties to your own profile, with explicit gap and transferable-skill rows. | Use after the colour-coded breakdown to force articulation of fit before drafting the cover letter. Most applicants build the requirements side and skip the duties side; the duties side is the load-bearing one. |
| Job Search Strategy Types (research finding, no framework page) | Focused (specific role/sector → higher satisfaction), exploratory (broad → more offers), haphazard (no plan → negative on both dimensions). | Choose deliberately between focused and exploratory based on your career stage and goals. Avoid haphazard. (Considered for promotion to a framework page but not promoted: this is a research finding to inform self-awareness, not a tool with operational steps.) |
Last updated 2026-05-10.