How to Get Promoted in Your First Job as a Software Engineer

You shipped code in your first month. You got a "meets expectations" on your first review. You show up early, stay late when needed, and your PRs get approved without much fuss.

None of that is going to get you promoted.

The gap between "doing your job well" and "getting promoted" catches new grads off guard more than almost anything else in their early career. You were hired to do the job. Doing it is the baseline, not the differentiator.

At most big tech companies, the first promotion from entry-level to mid-level (Google L3 to L4, Amazon SDE I to SDE II, Meta E3 to E4) takes 1.5 to 2 years for solid performers. Top performers hit it in 18 months. Everyone else drifts past the 2.5-year mark wondering what they missed.

The difference between those two groups is rarely technical skill. It is how they spend those first two years.

Stop collecting tasks. Start collecting evidence.

New grads tend to say yes to everything. Bug fixes, code reviews, on-call rotations, documentation updates. It feels productive. Your calendar is full. Your commit history is green.

But when your manager sits down to write your promotion case, they need more than a long list of completed tickets. They need a story about impact. What changed because of your work? What would have gone wrong without it?

The engineers who get promoted early do fewer things, not more. They pick projects where the outcome is measurable: reduced page load time by 200ms, cut deployment failures by 30%, migrated a service that unblocked three other teams. Those are sentences your manager can put in a promotion document.

If you cannot describe your last month of work in one sentence that includes a number, you are probably spreading too thin.

Your manager is not tracking your career

This is the single hardest lesson for new grads. In school, the system tracked your progress. Grades, transcripts, GPAs. At work, nobody is maintaining your permanent record.

Your manager has 6 to 12 direct reports. They have their own goals, their own skip-level pressure, their own deadlines. They are not keeping a spreadsheet of your accomplishments. If you do not surface your wins, those wins did not happen.

Start a weekly log. Every Friday, write down what you shipped, what you unblocked, and what you learned. This takes ten minutes. After twelve months, you will have a document that writes your self-review for you. Without it, you will stare at a blank page trying to remember what you did in Q1.

The engineers on Reddit and Blind who complain about being "invisible" almost always share the same problem: they assumed their work spoke for itself. It does not. If this sounds familiar, the deeper problem is usually that you have not learned how to stop being invisible at work. Your manager cannot advocate for something they do not remember.

Get a sponsor, not just a mentor

Mentors give advice. Sponsors give you opportunities.

A mentor is someone you grab coffee with and ask about career paths. Useful, but limited. A sponsor is a senior engineer or manager who puts your name forward for high-visibility projects, mentions you in rooms you are not in, and pushes for your promotion when the time comes.

You do not ask someone to be your sponsor. You earn it by delivering on projects they care about, by being reliable when they need someone, and by making their work easier. When a senior engineer trusts you enough to say "give this to [your name], they will handle it," you have a sponsor.

Most new grads have zero sponsors and do not realize it matters. At companies where promotions go through committees (Google, Meta, parts of Amazon), your manager's recommendation is necessary but not sufficient. You need people outside your immediate team who can vouch for your work.

Talk to your manager about promotion before you think you are ready

New grads wait too long to have the promotion conversation. They think they need to be "almost there" before bringing it up. The conversation should happen in your first six months.

You are not asking to be promoted. You are asking: "What does the path to my next level look like, for me, on this team?" That is a planning conversation, not a negotiation. Knowing how to have a career conversation with your manager makes this feel less awkward and far more productive.

When you have this conversation early, two things happen. First, your manager knows you care about growth, which means they start looking for opportunities to put you on visible projects. Second, you get concrete criteria. Not "be more senior" but "lead a project end-to-end" or "show cross-team impact" or "present to the team at least twice this quarter."

Without those specifics, you are guessing at a target you cannot see.

Pick the right projects (not just the ones assigned to you)

Entry-level engineers take whatever is handed to them. That is fine for the first three months while you learn the codebase and the team's norms. After that, you need to start shaping your own work.

The projects that get people promoted share a few traits:

• They have measurable outcomes. If no one will ever know whether the project succeeded or failed, it will not help your case.
• They affect more than your immediate team. Cross-team work, shared tooling, or infrastructure improvements signal next-level scope.
• They require some degree of ambiguity. A well-defined ticket with clear acceptance criteria is junior work. Figuring out what to build, then building it, is mid-level work.

If your team does not have projects like this available, create them. Find a recurring pain point (slow builds, flaky tests, manual deployments) and propose a fix. The best promotion cases often start with someone identifying a problem nobody asked them to solve.

The timeline is real, but not fixed

At Google, L3 to L4 takes about two years for a solid performer. At Amazon, SDE I to SDE II is typically 1.5 to 2 years. Meta expects E3 to E4 in a similar range, with more urgency because E5 is the terminal level and the "up or out" pressure starts early.

These timelines got longer between 2024 and 2026. Hiring freezes, flatter org structures, and tighter promotion budgets mean fewer slots. Companies are promoting fewer people, not because the bar went up, but because the opportunities to demonstrate scope shrank as teams got smaller.

You cannot control the macro environment. You can control whether your case is ready when a slot opens. That means documenting wins, seeking feedback, and building sponsor relationships from month one, not month eighteen.

What the first two years should look like

Months 1 to 3: Learn and ship. Get familiar with the codebase. Ship small changes. Build trust with your team. Do not worry about visibility yet.

Months 4 to 6: Have the conversation. Ask your manager what the path to your next level looks like. Start a weekly win log. Identify one senior engineer whose work you respect and start collaborating with them.

Months 7 to 12: Take on a real project. Lead something end-to-end, even if it is small. Own the problem definition, the implementation, and the rollout. Document the outcome with numbers.

Months 13 to 18: Build your case. Your win log should have 30 to 40 entries by now. Start framing those wins in terms of impact, not activity. Talk to your manager about promotion timing. If you do not have a sponsor, figure out why.

Months 19 to 24: Close the gap. Get specific feedback on what is missing. If the answer is "more scope," find it. If the answer is "more visibility," present your work. If the answer is "not this cycle," ask what would need to change.

The gap nobody warns you about

The hardest part of your first promotion is not the work. It is the shift from "I did what was asked" to "I figured out what needed to happen and made it happen." That is the real line between junior and mid-level, and no amount of grinding tickets will get you across it.

You have to stop waiting for direction and start creating it. That does not mean ignoring your manager or going rogue. It means identifying problems, proposing solutions, and driving outcomes without someone spelling out every step.

If you are 18 months in and your manager still assigns you every task, you have a visibility problem, a trust problem, or both. Figure out which one, and fix it.