We're adding two people to the platform team this quarter. Both roles are remote within the US, both are backfills rather than growth bets, and I'll answer the obvious question before it's asked: the band is published below.
The feed, triageable without reading it.
One colour per content type, carried on the spine of the card. A hiring post, a milestone, a piece of writing and an ad are four different things, so they stop looking like four copies of the same white rectangle.
Started something new. Seven months between roles, which I'd rather say out loud than quietly round off — a lot of people in my feed are in the middle of the same gap and the silence doesn't help any of us.
Your team is probably tracking this work in a spreadsheet. Ambletree replaces the spreadsheet with something that notices when a task is late.
We spent a quarter rebuilding our component library and the measurable win wasn't speed. It was that designers stopped inventing new greys.
Thirty-one greys went in. Six came out. Nobody has asked for the other twenty-five back, which tells you most of them were never decisions — they were someone's eyedropper at 6pm.
The profile, proof first.
The thing that demonstrates someone can do the job leads. The chronology still exists — it just stops being the headline act, because a list of dates has never been the reason anyone got hired.
Dara Okonjo
Staff product designer — design systems, and the arguments that come with them.
What I actually shipped
Three things, with numbersRebuilt the colour layer at Saltmarsh. Every token measured; nothing shipped below AA.
Was eleven. The win came from deleting choices, not from adding tooling.
Including the two that had forked it. Migration took a quarter and one very long document.
Where that happened
The short versionJobs that say the number.
Pay is stated, or its absence is drawn as a visible hole rather than quietly left out. The match score shows its working, because a percentage you can't interrogate is decoration with a decimal point.