Title levels on the ladder: principal, senior manager, distinguished, lead split (WP A)

from_title matches a title twice, for the highest people level and the
highest individual grade. A people level wins on its own rung; a grade
above that rung lifts it one rung (Principal Engineering Manager is a
senior manager). Senior Staff is principal, Senior Principal, Distinguished
and Technical Fellow are distinguished; Associate Director, AVP and Senior
Manager are senior managers. lead is now a team lead only (Team Lead, Shift
Lead, Supervisor, Teamleiter); Tech Lead, Lead X and X Lead(er) are staff.
A slash names two levels, so Senior/Staff is staff.

- Jobylon "lead" maps to staff; Recruitee maps student_college, manager,
  senior_manager and executive.
- extract's prompt describes the ladder and its two tracks; enum from LEVELS.
- prep VERSION 2, so the next prep maps every open role again.
- Migration 25 clears seniority_model where it is staff, lead, manager or
  director, so extract reads those roles again, and sets roles.seniority to
  the first filled of model, stated and title.
- The coverage test of tests/test_seniority.py passes; its xfail is gone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Opus 5.5 committed 2026-09-30 13:11:26 +02:00
1 parent ae978594b4
commit 322db49773
16 files changed
+328 -137

No files matched your search

+22 -10
View File
@@ -72,16 +72,28 @@ Fields:
("Berlin", "Greater London"). '' if none is named.
- country: ISO 3166-1 alpha-2 code of that place ("DE", "GB"), or ''.
- remote: "remote", "hybrid" or "onsite" only when the posting says so, else ''.
- seniority: exactly one of {", ".join(s for s in SENIORITIES if s)}, for every
posting; never ''. This is the one field where you decide rather than
extract. Judge the level of the person hired from the title and the text (or
the short teaser when there is no text), weighing years of experience,
scope and who the role reports to. `stated` is the level the job board
itself gave and `title_level` the one a word in the title suggests. Both
are hints: boards use different vocabularies and many state nothing, so
overrule them when the posting says otherwise. When nothing says, choose the
likeliest level for that kind of title; most postings are for individual
contributors, not managers.
- seniority: exactly one of {", ".join(LEVELS)}, for every posting; never ''.
This is the one field where you decide rather than extract. The levels are
one ladder; from staff up each rung has an individual-contributor level and
a people-lead level of equal weight:
intern, junior, mid, senior: no track.
staff (Staff, Tech Lead, "Lead Engineer", "Marketing Lead") |
lead (Team Lead, Supervisor) or manager (manages a team).
principal (Principal, Senior Staff) |
senior_manager (Senior Manager, manages managers, Associate Director).
distinguished (Senior Principal, Distinguished, Technical Fellow) |
director (Director, Head of a function).
exec (VP, C-level, Managing Director).
Choose a people level only when the hire manages people; a Product,
Account or Project Manager is an individual contributor. Judge the level of
the person hired from the title and the text (or the short teaser when
there is no text), weighing years of experience, scope and who the role
reports to. `stated` is the level the job board itself gave and
`title_level` the one a word in the title suggests. Both are hints: boards
use different vocabularies and many state nothing, so overrule them when
the posting says otherwise. When nothing says, choose the likeliest level
for that kind of title; most postings are for individual contributors, not
managers.
- salary_min, salary_max: yearly gross amounts as integers, or null. A stated
monthly figure is multiplied by 12; an hourly or daily rate is null. A single
figure is both min and max.