Bureau of Software PersonnelForm DEV-24A
BUREAU OF SOFTWARE PERSONNELNO. II-BRIDGE
Subject translates 'the API is fine' into actionable requirements without visible effort. Keeps a private tally of meetings that ended in an actual decision; the count is disappointing. Roughly half the team's output routes through one sentence the subject once said in a hallway. Claims to dislike meetings; attends all of them.
The Bureau files this classification from a 30-item forced-choice examination. Nothing on this page describes you — it describes the type, so you can decide whether the description is worth filing. The examination is free and takes six minutes.
I.Documented strengths
- Converts two arguing seniors into one decision before lunch
- Writes the summary email everyone forwards instead of writing their own
- Makes engineering legible to the business without making the engineers wrong
II.Known limitations
- The calendar ate the deep work, and the subject personally scheduled the feedings
- Must claim credit in writing for work that is, by design, invisible
- Occasionally mistakes being understood for being agreed with — expensively
III.Recommended assignments
Product engineering, tech-lead roles, cross-team initiatives, customer-facing engineering.
IV.Why this type fits the role
- The bottleneck in cross-functional work is almost never the code. It is the sentence, and this is the archetype that writes it.
- Tech-lead roles are measured in decisions per week, which is precisely the subject's demonstrated output.
- Customer-facing engineering shortens the distance between a complaint and a fix, which is where most roadmap failures actually originate.
- The subject makes engineering legible to the business without making the engineers wrong — a rare and expensive capability.
V.What drains this type
- A heads-down solo backlog removes the translation layer the subject is actually made of. Performance will drop and the cause will be misfiled.
- Organisations that meet in order to avoid deciding are hostile to this archetype, because the subject's output is a decision.
- Pure-depth individual-contributor tracks have no audience, and this archetype produces nothing at all without one.