Best practices · Career
Engineering Career Growth Best Practices
Opens with creditsA practical guide to growing from junior to senior engineer and beyond, checked against public career ladders such as the Dropbox Engineering Career Framework and the GitLab handbook. It covers how ladders describe each level, what scope and impact mean, ownership, working with your manager, using feedback, collecting promotion evidence, choosing projects, and the staff and manager paths.
What you will learn
8 chapters · about 24 min
1Understand how career ladders workMost companies describe each level in writing. Read yours, learn what changes between levels, and stop guessing what senior means.4 practices · 4 min
2Grow your scope and impactImpact is the currency of every ladder. Learn what it means where you work and aim your effort at it.4 practices · 3 min
- Own outcomes, not tasksOwnership is the trait every ladder describes at senior levels. Practise it early, on whatever you are given.4 practices · 3 minOpens with credits
- Work with your manager on your growthYour manager is your strongest advocate, but only for work they know about and goals they understand.4 practices · 3 minOpens with credits
- Seek and use feedbackFeedback is how you find the gaps you cannot see yourself. Ask for it specifically, receive it calmly and act on it.4 practices · 2 minOpens with credits
- Build the evidence for a promotionPromotions recognise sustained work at the next level. Collect the evidence as you go, not the week before the review.4 practices · 3 minOpens with credits
- Choose projects that grow youThe work you take on shapes the evidence you can show. Choose deliberately when you have a choice, and shape the work when you do not.4 practices · 3 minOpens with credits
- Choose between the staff and manager pathsAbove senior, most companies offer two parallel paths. Learn what each one actually involves before you choose.4 practices · 3 minOpens with credits
About this guide
These engineering career growth best practices are for software engineers who want to move from junior to mid-level, from mid-level to senior, and eventually decide between a staff path and a management path. Growth rarely comes from simply doing more tickets faster. It comes from taking on larger and more ambiguous problems, owning outcomes instead of tasks, and making the people and systems around you better.
The guide is checked against public engineering career ladders, mainly the Dropbox Engineering Career Framework, which publishes what it expects at every level from IC1 to IC7 along with its promotion principles, and the GitLab handbook, which documents individual contributor and management tracks in the open. Where those sources say something specific, such as Dropbox describing promotions as "evidence, not faith", the guide quotes it and links the source.
The first chapters explain how ladders work and what scope and impact actually mean, because most career confusion starts there. Later chapters cover ownership, working with your manager, feedback, building the evidence for a promotion, choosing projects, and the staff and manager paths. Technical leadership of a team is covered in more depth in the tech lead best practices guide, so this guide links to it rather than repeating it.
Each chapter ends with a short quiz. The advice applies whether you work at a startup in Karachi, a product company in Lahore, a bank in Dubai or a remote team spread across Europe. Titles and level numbers differ between companies; the underlying expectations are remarkably similar.
Common questions
How long does it take to grow from junior to senior engineer?
There is no fixed timeline, and it varies by company and person. Dropbox publishes typical time in level: 1.5 to 2 years at L1, 2 to 3 at L2 and 2 to 4 at L3, with L4 described as a career level for many engineers. Added up, that is roughly five and a half to nine years from L1 to L4 at a typical pace, but scope and impact matter more than time served.
What is the difference between a mid-level and a senior engineer?
Mostly scope and ambiguity. Ladders describe mid-level engineers delivering defined projects, and senior engineers autonomously owning larger goals, solving ambiguous problems that need prioritisation, and making their team better. Senior engineers also influence work beyond their own team.
Do I need to become a manager to grow my career?
No. Most mid-sized and large tech companies have parallel tracks: staff, principal and higher roles for engineers, and a separate management track. Management is a different job rather than a promotion, and many engineers grow for their whole careers without managing people.
What is a brag document?
A running record of your work and its impact, kept through the year and shared with your manager before reviews. It typically covers goals, projects, collaboration and mentorship, design and documentation, and what you learned. It helps because people forget much of their work by review time.
What are the staff engineer archetypes?
Will Larson describes four common shapes of staff work: Tech Lead, Architect, Solver and Right Hand. Dropbox mapped these archetypes to its levels in its 2023 framework update. Which ones exist depends a lot on company size.
Does glue work like documentation and on-call count toward promotion?
Increasingly, yes. Dropbox updated its framework in 2023 partly so that ownership, difficult decisions and maintenance work such as on-call and documentation get more credit. It counts most when you describe its effect, and when its balance with project work is discussed openly with your manager.
Sources (7)
Checked against these, last on 13 October 2026.
- Dropbox Engineering Career Framework, Dropboxdropbox.github.io/dbx-career-framework/
- What is Impact?, Dropboxdropbox.github.io/dbx-career-framework/what_is_impact.html
- Promotion Principles, Dropboxdropbox.github.io/dbx-career-framework/promotion_principles.html
- Promotion Guidelines, Dropboxdropbox.github.io/dbx-career-framework/promotion_guidelines.html
- Our updated engineering career framework, Dropbox Tech Blogdropbox.tech/culture/our-updated-engineering-career-framework
- Engineering Career Development, GitLab Handbookhandbook.gitlab.com/handbook/engineering/careers/
- Get your work recognized: write a brag document, Julia Evansjvns.ca/blog/brag-documents/
Related on Sefism
Picked from the other libraries by shared topics.
Roadmaps
See allCheat sheets
See allBest practices
See all- Tech Lead Best PracticesTech lead best practices for engineers stepping up: define the role, set direction with design docs and ADRs, plan and unblock delivery, run healthy code review, grow people, handle incidents.
- Technical Writing Best Practices for EngineersTechnical writing best practices for developers: write for your audience, clear sentences, scannable structure, design docs, READMEs and docs, PR descriptions, async updates and blog posts.
- How to Learn a New Programming Language or FrameworkBest practices for learning a new language or framework fast: set a goal, start with official docs, build small projects, practise deliberately, use spacing, read real code, learn with AI wisely.
Checklists
See all- First 90 Days in a New Developer Job: ChecklistWhat to do before day one, in week one and by day 30, 60 and 90 in a new developer job: setup, codebase, first PR, your manager, questions and feedback.
- Career Switch into Tech ChecklistMove into software from another field step by step: choose a direction, follow a learning plan, build proof of skill, use your previous domain, network, plan your runway and target a first role.
- LinkedIn Profile Checklist for DevelopersCheck your LinkedIn profile section by section: photo, headline, About, Experience, Featured, Skills, custom URL, Open to Work, posting and privacy.
Career questions
See all- How do I go from mid-level to senior software engineer?Senior is less about years and more about scope: you own ambiguous problems, make sound technical decisions others rely on, and make the people around you more effective. Pick work with real uncertainty, write down your decisions and trade-offs, invest in others, and make that impact visible to the people who decide promotions.
- How do I deal with a toxic manager or workplace as a developer?First separate a hard environment from a harmful one. Protect yourself by documenting incidents, setting clear boundaries in writing and raising issues through the right channel. Try one or two honest fixes, but if the pattern continues or affects your health, plan a calm exit rather than enduring it indefinitely.
- What should I do when I disagree with a senior engineer or tech lead?Disagree early, privately where possible, and with evidence rather than opinion. Make sure you understand their reasoning first, frame your concern around the shared goal, offer a concrete alternative, and accept the decision once it is made. Disagreeing well builds trust; silence or going around them does not.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com