Aurum
Download

Individual Contributor Career Path

A deliberate route from senior to staff and principal without managing people: the right archetype, scope that matters, technical strategy and writing, influence across teams and a plan you review.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Then open the Marketplace in the app, search for Individual Contributor Career Path, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🧭 Career Growth

Individual Contributor Career Path

Growing as a senior individual contributor toward staff or principal roles without moving into people management.

  1. Decision to stay on the individual contributor track
  2. Reading the IC ladder above senior
  3. Choosing the staff archetype that fits you
  4. Senior to staff scope self-assessment
  5. Telling your manager you want the staff path
  6. Business priorities to technical problems map
  7. Weekly calendar plan for senior IC work
  8. Study of three staff-level people you admire
  9. Development plan toward the next IC level
  10. Weekly technical writing block
  11. Monthly audit of where your time went
  12. Design review slot for other teams
  13. Cross-team peer conversations each month
  14. Quarterly review of your technical bets
  15. Mentoring two people below your level
  16. Reading pipeline for senior IC craft
  17. Learning from incidents across the organisation
  18. Quarterly scope check with your manager
  19. Peer feedback on your influence
  20. Writing a design document others can approve
  21. Writing a technical strategy that gets used
  22. Influence without authority across teams
  23. Sequencing multi-quarter technical work
  24. Running an architecture review to a decision
  25. Business and cost literacy for senior ICs
  26. One-page briefs for senior leaders
  27. Facilitating a contested technical decision
  28. Pruning work that sits below your level
  29. Choosing your first staff-scope project
  30. Letting go of the critical path
  31. Technical vision for your area
  32. Owning a cross-team problem nobody owns
  33. Internal growth or an external staff title
  34. Staff-scope project kickoff
  35. Presenting a technical strategy to leadership
  36. Taking an organisation-wide proposal to decision
  37. Leading an architecture day for several teams
  38. Staff-level interview loop preparation
  39. Principal path outside software engineering
  40. Senior IC in a company with no ladder above senior
  41. Returning to the IC track after managing
  42. Unofficial tech lead without the title
  43. Staff scope on reduced or flexible hours
  44. First staff engineer at a growing startup
  45. Owning an engineering standard across the organisation
  46. Helping shape the IC ladder itself
  47. Sponsoring the next generation of staff ICs
  48. Build, buy or partner analysis for a platform
  49. Staying hands-on at principal level
  50. Five-year IC career plan to principal and beyond

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Decision to stay on the individual contributor track

Somewhere around the senior level most people are nudged toward management, often because it looks like the only way up. Making the choice on purpose, by comparing what you enjoy on a good week with what managers and staff engineers actually spend their days on, stops you drifting into a role you did not want or refusing one out of habit.

First tasks

  • List the tasks from the last two months that energised and drained you
  • Ask one manager and one staff engineer what fills a typical week
  • Write a one-page comparison of both paths against your list
  • Record the decision and the condition that would make you revisit it

Reading the IC ladder above senior

Above senior, ladders stop describing better work and start describing wider work: scope across teams, ambiguity handled, direction set. Reading the staff and principal descriptions closely, and asking how many people hold each level, tells you what the jump really requires and how rare it is at your employer.

First tasks

  • Find the current ladder pages for senior, staff and principal roles
  • Highlight the scope words that change between each level
  • Ask HR or your manager roughly how many people hold each IC level
  • Check whether the IC ladder has been revised this year @recurring(yearly)

Choosing the staff archetype that fits you

Staff-level people tend to work in recognisable shapes: the tech lead who steers one area, the architect who owns direction across several, the solver who goes where the hardest problem is, and the right hand who extends a senior leader's reach. Naming the shape that suits your strengths and your organisation's gaps gives your growth a target you can describe in one sentence.

First tasks

  • Write a short description of each of the four staff archetypes
  • Name one person you know who works in each shape
  • Ask two senior colleagues which shape the organisation lacks most
  • Write your chosen archetype as a one-sentence role statement

Make it yours.

Install Individual Contributor Career Path, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.