Free tools Windows power users keep installed
One-click scans. No signup required.
To improve your chances of promotion, agree with your manager on what the next level requires, then demonstrate those contributions through meaningful outcomes over time. Strong technical work matters, but public engineering frameworks also weigh factors such as scope, execution, collaboration and sustained impact. The exact bar, review process and availability of a role vary by employer.
What usually supports a promotion in tech?
Promotion is often framed as recognition for work already performed at the next level, rather than a reward that automatically grants new responsibilities. Dropbox Engineering says promotions recognize “demonstrated, sustained impact at the next level.” Square similarly says that increased scope and responsibilities come first, with promotion recognizing them afterward. These are employer-specific approaches, not a universal rule.
In practice, that means showing what changed because of your work—not only listing tasks completed, technologies learned or hours spent. The relevant outcomes depend on your role and level: they might involve a more reliable service, a better user experience, a delivered project, stronger team practices or a difficult technical decision made well.
How do I find out what my company expects?
Ask your manager to describe the next-level bar in terms you can observe and act on. Broad feedback such as “show more leadership” is hard to use until you know what leadership would look like in your role. Ask for examples of decisions, outcomes, scope or collaboration that would demonstrate it.
#1 Best Overall
Dropbox Engineering emphasizes regular, active conversations between employees and managers about short- and long-term development. GitLab’s handbook recommends career-development conversations at least quarterly. Those are examples of company practices; your employer may have a different cadence or process.
- What specific expectations distinguish my current level from the next one?
- What work or behaviors would count as evidence for each expectation?
- How and when are promotion decisions made, and who reviews them?
- Does the role or level I want exist on my team, and are there organizational constraints?
- When should we check progress and adjust the plan?
Ask your manager to turn general feedback into examples and opportunities. If the answer remains vague, request a concrete example of what is missing and a date to revisit it.
What evidence should I build?
Start with the dimensions your employer actually uses. Sourcegraph’s engineering framework names impact, scope, execution and teamwork, and says technical growth alone is not sufficient for promotion there. Square describes a process that uses a promotion packet and peer feedback. These examples show why technical skill is important but may not, by itself, establish readiness.
Show impact and scope
Explain the problem, who it affected and what improved. Clarify your own contribution, the decisions you made and how the work’s scope compared with your current responsibilities. A list of completed tickets rarely communicates those things on its own.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Show execution and judgment
Give examples of how you moved work forward: how you handled uncertainty, trade-offs, delivery risks or changing requirements. Connect those actions to the result rather than presenting process as an end in itself.
Show how you work with others
Document collaboration, feedback, mentoring or improvements to shared team practices when those are relevant to your level and role. Do not assume that promotion requires becoming a manager or taking on a high-profile project. Dropbox’s framework update describes an effort to recognize varied contributions, including operational and documentation work.
Keep a concise evidence record
Maintain notes as work happens so you can discuss progress accurately and prepare any formal submission. For each example, record:
- The problem or goal.
- Your contribution and the decisions you owned.
- The result for users, the business or the team.
- Collaborators and relevant feedback.
- Which agreed next-level expectation the example demonstrates.
This record is useful for regular manager conversations and, where required, a promotion packet. It should capture evidence, not inflate routine activity into a claim of impact.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHow do promotion processes differ between companies?
Public career frameworks are useful illustrations, not a substitute for your employer’s actual policy. They vary in criteria, review mechanics and whether a suitable role or budget must be available.
| Employer or framework | What its published material says |
|---|---|
| Dropbox Engineering | Promotion principles emphasize sustained next-level results and regular manager conversations. A separate framework update says the company sought to recognize a variety of contributions, including operational and documentation work. |
| GitLab | The handbook recommends quarterly career-development conversations and distinguishes coaching for future preparation from the promotion process that documents completed contributions. It says certain senior moves require a position of need. |
| Sourcegraph | The engineering framework describes expectations using impact, scope, execution and teamwork, and says technical growth alone is insufficient for promotion eligibility there. |
| WHOOP Engineering | Its promotion principles emphasize sustained impact and note that departmental budget approval is relevant. |
| Square | Its published framework describes evidence in a promotion packet, peer feedback and structured panel review, alongside engineering and engineering-management paths. |
| American Society of Civil Engineers (ASCE) | Its 2022 grade guidelines describe general abilities, multiple tracks and variable progression; the descriptions are not minimum requirements. |
Before a review cycle, ask what evidence is considered, who participates in calibration, whether peer input is gathered, what dates apply and whether the move depends on an opening or budget. Ask separately whether any gap is about your demonstrated skills or about an organizational constraint. A constraint is not proof that you are ready, but readiness alone may not create a role or funding.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Is there a standard timeline or checklist?
No universal timeline or cross-company checklist is established by these examples. Square says its framework does not set a strict minimum experience requirement for each level; ASCE says engineers progress at varying rates and its grade descriptions are general abilities rather than minimum requirements. Dropbox and WHOOP emphasize sustained impact, but those company principles do not define a standard duration for the technology industry.
Use the timeline and criteria your company actually applies. Treat a framework as a guide to discussion, not a guarantee that completing a fixed number of tasks or spending a particular number of years will result in promotion.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11What if the criteria are unclear or the opportunity is blocked?
Ask for concrete examples, agreed next steps and a date to review them. GitLab’s distinction between preparation coaching and formal promotion documentation is useful here: feedback intended to prepare you should help you develop, while a promotion review evaluates contributions already made. Confirm that you are receiving actionable coaching before a cycle rather than discovering expectations only during the decision.
Promotion systems can also have clarity problems. In Dropbox’s account of a survey of 106 engineering career-framework respondents, more than a quarter said the criteria did not reflect their day-to-day work, and more than a fifth said next-level expectations were unclear. Dropbox did not state the survey year in the available account; those figures describe its respondents, not technology workplaces generally.
If the bar keeps shifting, feedback remains nonspecific or no viable role is available, ask your manager to name the obstacle and whether it can change. You can then consider whether another team or employer offers a clearer path, weighing that choice against your own priorities. Changing jobs is not a guaranteed shortcut to promotion.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
