Behavioural signals for staff and principal roles

Dropbox’s public career ladder describes its staff engineers as setting “the multi-year, multi-team technical strategy” and its principal engineers as delivering results against a strategic company-level objective. Staff candidates hear the same “tell me about a time” questions as everyone else, but the answer has to show an organisation changing course, not one system.

The behavioural signals for staff and principal roles are direction, influence without authority, mechanisms that outlast you, judgement at scale and a clear account of your own role. Below are those signals, the ladders they come from and the path one direction took across five teams.

At staff level, the story is an organisation changing course

Dropbox publishes its engineering framework under an open licence. Its IC5 staff engineer influences “the roadmaps of other Dropbox teams” and exercises judgement “that favors the priorities of the wider engineering org rather than favoring locally optimal outcomes”. Its IC6 principal engineer delivers against a company-level objective and typically influences the technical strategy of a group. The framework also says there is more than one path to those levels. Its three archetypesstaff archetype: One of the shapes a staff engineer's role can take, such as a technical lead who guides one team, an architect who owns direction in a critical area, or a solver who takes on hard problems wherever they are., inspired by Will Larson’s book Staff Engineer, are a technical lead who guides one team’s approach, an architect responsible for direction in a critical area, and a solver who digs into hard problems wherever they are. Amazon writes narrative memos of one to six pages instead of slide decks, so writing that changes a decision is a staff skill there as well.

Five signals carry that work into a story:

• Direction: you framed a problem across teams and set a course that others followed.
• Influence without authority: leaders and teams you did not manage changed their plans.
• Mechanisms: a mechanismmechanism: Something you put in place that keeps producing a result without you, such as a review, a standard, a template or a guide that other people run and use. you built, such as a review or a standard, kept working without you.
• Judgement at scale: you can explain a bet, including one that failed, from the information you had.
• Your role: you can say exactly which parts were yours when many teams did the work.

Ananya, an invented staff engineer, moved five teams’ scheduled jobs onto one platform. Step through the path her direction took:

The drawing shows the whole scene; its 8 steps are listed below.

Every step as text

1. Frame the problem. Five teams ran about 140 cron jobs on their own servers, and 11 incidents in a year began with a job that failed silently or ran twice. Nobody owned scheduling as a whole, so Ananya spent a month listing every job, its owner and what it touched.
2. Write it down. She wrote a six-page proposal for one workflow platform with retries, alerts and a record of every run. Writing it first meant every team's lead read the same case before anyone argued about it.
3. Bring the leaders in. She presented it to the five teams' leads. Four agreed to try it; billing refused, because its month-end jobs move money and could not risk a new system.
4. The plan changes. Instead of escalating, she changed the plan: billing would move last, and its jobs would run on both systems for a full month-end first. The refusal was a real risk, so it shaped the design.
5. Start where it is safe. Two teams with the least risky jobs piloted the platform in the first six months. She paired with their engineers on the first jobs instead of moving the jobs herself.
6. Leave a mechanism. She wrote the migration guide the other teams used and set up a monthly review of failed runs. Both were built to work without her.
7. Step back. Over two years all 140 jobs moved, and incidents from scheduled work fell from 11 a year to 2. The platform team now runs the monthly review without her.
8. The whole path. Six stages, and in every one Ananya made a decision about work other people did. That is what a staff story shows: an organisation changing course, with her part in each step clear.

The behavioural signals for staff and principal roles live in those stages. Each one is a decision she made about other people’s work, and the last one is her stepping back.

A direction-setting story, told in full with its numbers Pro: opens with a Pro, Premium or Ultimate pass

In this part:

• Influence without authority: the moves interviewers listen for
• A failed bet, told with the decision record
• Your role when many teams did the work
• The hardest follow-up, prepared before the interview
• Practise: write two staff-level stories
• Interview questions
  • Tell me about a technical direction you set that several teams followed. How did you get them to follow it?
  • Tell me about a technical bet you made that did not pay off. What did it cost, and what did it teach you about your own judgement?
  • Tell me about a time two senior leaders disagreed about a technical direction and you helped them reach one decision.
• Key takeaways

1 diagram · 1 runnable example (JavaScript) · 3 interview answers · about 27 minutes

Opening this part with your pass…

This part opens with any MySmartCoPilot pass.

• Pro pass · 1 week · ₹79 · $2.99
• 30 days · ₹179 · $5.99
• 1 year · ₹1,699 · $45

One payment; a pass never renews. The price shown is the total you pay: no fees or charges are added at checkout.

Choose a passI have a licence key

It also opens every other in-depth part in Learn and every Pro tool. Sales are final, except where the law gives you a right to withdraw, for example in the EU and the UK (refund policy).

Terms in this lesson

decision record

A short document, written when a decision is made, that records the context, the options, the decision and its reasons, what is expected and what would make you revisit it.

mechanism

Something you put in place that keeps producing a result without you, such as a review, a standard, a template or a guide that other people run and use.

staff archetype

One of the shapes a staff engineer's role can take, such as a technical lead who guides one team, an architect who owns direction in a critical area, or a solver who takes on hard problems wherever they are.