Come do the work, not the performance of work.

Own a product surface with a designer and a delivery lead. You will ship to production every week and stay for the operational path.

• — You have led delivery on a product that real operators use, not only a consumer app with a happy path.
• — You are fluent in TypeScript or a comparable typed ecosystem, and you can design an API that another team can live with.
• — You write, review, and document as part of the work. You are comfortable saying no to a slice that is not production-shaped.

Design complex software with engineers in the room. You will own flows, states, and a system — not a deck of screens.

• — You have shipped a design system or a dense product (ops, finance, health, logistics, or similar).
• — You prototype in the tools the team actually builds from, and you test with the people who will use the product.
• — You can defend an accessibility decision in a critique and in a pull request.

Keep a squad honest: scope, quality, and the date. You sit between the client’s reality and the team’s capacity.

• — You have run multi-month product work with engineers and designers, not a PMO theatre of status reports.
• — You can write a slice proposal, run a weekly demo, and escalate a risk while there is still time to act.
• — You are calm when a stakeholder wants the date and the scope and the unknown integration to all be fine.

Make production boring. Pipelines, environments, observability, and the paved road our product squads travel on.

• — You have run Kubernetes or an equivalent platform in anger, including the day it misbehaved.
• — You care about developer experience as much as uptime: the paved road should be the easy road.
• — You can talk to a product squad about trade-offs without hiding behind a ticket template.