Methodology
Hold up a mirror: how we built role expectations for the industry's leading companies
One of the most valuable things you can do for your career is to assess yourself honestly against a clear definition of your role — or the role you want next. So we built a catalog of engineering role expectations from publicly available materials, and a tool to assess yourself against them in about ten minutes.
Why benchmarks matter
Most engineers only see their own company's expectations — if their company has written any down at all. That makes two important questions hard to answer: Am I performing at my level? and What does the next level actually look like? Comparing yourself against how leading companies define the same role gives you an external reference point that your annual review can't.
The pattern behind every engineering ladder
Read enough job ads and career frameworks and a consistent arc emerges, no matter the company:
- Junior is about delivering with support. You deliver to the standards of the team with generous help, and nobody expects you to be fully independent yet. The core skills are fundamentals, learning velocity, and asking for help early.
- Mid-level is about growing independence. You need less and less support. You own features end-to-end, unblock yourself, and are trusted to deliver without close supervision.
- Senior is about supporting others — while still doing the work. You remain a hands-on individual contributor, but a growing share of your value is indirect: mentoring, raising the bar in code review, shaping decisions, and taking accountability for outcomes beyond your own tasks.
(Beyond senior, the arc continues: staff and principal roles are mostly indirect value — accountability across teams, strategic allocation of your own attention, and operating calmly in high-uncertainty, high-consequence domains. We're starting with junior, mid, and senior.)
How we build each benchmark
- Gather public sources. Job advertisements from the company's own careers pages and LinkedIn, published career frameworks and engineering ladders, and company engineering blogs.
- Extract competencies. We map the language in those sources onto a shared competency library — the same competencies across all companies, so results are comparable.
- Set expected proficiency. Each competency gets an expected level on a five-point scale adapted from the Dreyfus model of skill acquisition: Novice, Advanced Beginner, Competent, Proficient, Expert.
- Review by humans. Every role is reviewed before publishing, and every published role links its sources.
What we are not claiming
These are our interpretations of public materials — not internal rubrics, not leaked documents, and not endorsed by the companies named. Real promotion decisions involve context no public source captures. Treat these benchmarks as a structured mirror, not an oracle: the value is in the honest self-reflection they prompt, and in seeing which areas the industry consistently emphasises at each level.
Try it
Pick a company and a level, rate yourself against each expectation, and get a summary of how you measure up — including where you're ahead and where the biggest gaps are. It takes about ten minutes.
Free to take. Built by Find Grow & Keep, the evidence-based career companion.