Two-Phase Job Search

Dimension: Choice · Type: Stage

A separation between two activities that look similar but are not: scanning vacancies to decide whether to apply, and working on a specific application. Each phase has its own purpose, its own depth of engagement, and its own checks.

Introduced by Damla Deniz Taskin (OPCW) at the Breaking Down Job Descriptions session of the UN Inter-Agency Career Week 2026, on 6 May 2026. Damla framed the two phases as the structural reason that breaking down JDs is “crucial in both phases” but for different purposes.

The framework

When to use it

  • When you find yourself spending too much time on JDs you eventually do not apply to, or too little time on JDs you do apply to.
  • When you are calibrating how to read a vacancy notice without committing hours to it before the fit decision is made.
  • When you are designing a weekly job-search routine.

What you need

A working list of open vacancies. An honest sense of your current career direction (which kinds of roles you would say yes to if offered).

Phase 1, preparatory

Purpose. Decide whether the role is worth a tailored application.

Depth. Light. You are looking for fit signals, not preparing to apply.

Steps.

  1. Read the title and the organisation. Does it match the kind of role you have decided to pursue?
  2. Read the first two or three responsibilities. What does the role actually do?
  3. Read the mandatory requirements honestly. Do you meet the eligibility gates (years of experience, education, languages)? If not, stop.
  4. Read the location and any relocation implications. Does it work for your life right now?
  5. Estimate fit using the Seventy Percent Fit Threshold. Above the threshold and within eligibility: move to phase two. Below: log the role for later if it represents a direction you want to grow into; otherwise drop it.

Time per role: 5 to 10 minutes.

Phase 2, active

Purpose. Build a tailored, well-aligned application that has a real chance of progressing.

Depth. Deep. This is marathon-runner mode (see Sprinter, Runner, Marathon Runner Typology).

Steps.

  1. Save a local copy of the JD. Vacancy notices can be removed from the web; the local copy is your reference for the rest of the process.
  2. Run the JD Colour-Coded Breakdown on a separate document.
  3. Build the JD vs Profile Comparison table.
  4. Pull relevant entries from your BASIC Achievement Bank and map them to JD responsibilities.
  5. Draft the CV bullets and cover letter using R-CAR for the achievement statements.
  6. Run all three layers of the Third Eye Principle.
  7. Submit, save the submitted version, and log the application date and reference number.

Time per role: a few hours to a full afternoon.

Worked example

An applicant has 14 open vacancies on their tracker. They block one hour for phase one across all 14.

  • Six fail the eligibility gates (insufficient years of experience or wrong language profile). Drop.
  • Three are below the 70% fit threshold and not aligned with their target direction. Drop.
  • Two are below the threshold but represent roles they want to grow into. Logged for skill-building, not applied.
  • Three pass both gates and the threshold. Move to phase two.

They allocate three half-day blocks across the week, one per role, for phase two. Each application gets its full marathon-runner treatment. Three quality applications submitted in seven days.

Pitfalls

  • Skipping phase one and going straight to phase two on every vacancy. The result is either burnout (too much tailoring effort) or sprinter-mode applications (when burnout sets in).
  • Spending too long on phase one, treating it as if it were phase two. Phase one is a 5-to-10-minute scan. If you are reading the JD for half an hour without deciding, you are stalling on the fit decision.
  • Treating “I will tailor it later” as a phase one outcome. The output of phase one is a yes or no, not a maybe.
  • Not saving the local copy. A vacancy notice taken down mid-process leaves you without the source document for the rest of the application work.

When not to use it

When you are doing pure exploratory research on a sector or a target organisation, with no specific role open. That is upstream Direction work, not job search.

How I use it

Personal note pending. Davide to fill.


Notes compiled by Davide Piga. Last updated 2026-05-09.