In collaborative projects, the person who announces the result gets the most credit. If someone else speaks first, add on with specific details about your contribution. Simply hoping your work will be noticed is a failed strategy.
Managers are often focused on reporting results, not giving credit. A simple prompt, like "Today's the day you should write the message saying good job team," is often all that's needed to ensure your team's work is recognized. Don't assume they'll do it unprompted.
After a product manager announces a launch, follow up with a technical note explaining the "how." Frame it as sharing interesting underpinnings with leadership. This positions you as a valuable expert without undermining the original announcement.
Simplify your achievements for maximum impact, even if it's a slight embellishment. For instance, say "I was the first engineer on Prime Video" even if it wasn't called "Prime" yet. Most people claim too little, hoping for cosmic fairness that never comes. Claim more until it risks your reputation.
When you pitch a new idea, don't just present the concept. Clearly state, "I am excited to build it." This frames you as the default owner. If your manager then gives it to someone else, they must actively make the decision to disappoint you, which is a powerful deterrent.
Managers often make practical, not just, decisions. They will appease pushy, high-value employees to prevent them from leaving, often at the expense of "nice" employees who won't complain. To protect your interests, you must show that disappointing you comes with a cost.
The best defense is a good offense: be so busy with valuable projects that you can't take on more. If that fails, become a "porcupine" by showing friction and pushing back. A manager will almost always choose to assign undesirable tasks to the path of least resistance—the compliant "squirrel."
Instead of being assigned undesirable tasks, volunteer for them. Go to your manager and say, "I'll spend the next two weeks on maintenance because I'm on your side. After that, I want to work on X." This transforms you from a victim into a proactive team player and lets you negotiate for your next project.
Don't just do your job well; actively seek out and solve your manager's biggest pain points. Ask them, "What are your three biggest problems? Which one's worst? I want to work on that." The person who repeatedly solves the leader's most pressing issues becomes the obvious choice for promotion.
For managers who avoid direct conversations about career growth, you can leverage AI. Feed their emails, Slack messages, or public writing into a large language model and ask for a strategy to discuss a promotion with their specific personality type. AI is excellent at personality typing and crafting communication strategies.
If a manager decides they want an employee gone, they have many tools. They can assign a stream of undesirable tasks, deliver a constant barrage of negative feedback, and micromanage them into quitting. HR's job is to protect the company, which often means siding with a manager in good standing.
To push back on grunt work without being confrontational, use humor and framing. Tell your manager they only get a few "shit work tokens" per month. This reframes the dynamic, makes them conscious of the cost of their ask, and is hard to argue against without them looking like a jerk.
The hardest person to fire is mediocre but well-liked. There's no "smoking gun" for poor performance, and their social capital makes managers hesitant. Conversely, while a disliked high performer may be critical, management is already looking for ways to reduce dependency on them.
If you suspect a peer might undermine you, get to your manager first. Say, "Some people here take shots at each other. I don't do that, so I'm counting on you to judge me by my work, not what others say." This inoculates you. When the peer later attacks, the manager sees it as the exact behavior you warned about.
Faced with a massive headcount request for "25 marketing people," Jeff Bezos rejected it. He forced the team to break it down into small, specific units (e.g., "2 people for PR"). This atomized request exposed lazy thinking and allowed him to scrutinize the justification for every single hire, killing empire-building.
When a project tanks, the headcount is at risk. A savvy manager immediately moves those engineers to a promising project. Then, they report to leadership, "Project A failed, but good news: I've moved the team to Project B, which is now moving twice as fast." This prevents headcount clawbacks by creating new value.
In a competitive internal environment, hiring is a race. Companies might budget for 1000 hires but allow 1500 roles to be opened, closing them once the budget is filled. Managers who prioritize hiring quickly fill their teams, while those who wait until Q4 find the budget is gone. Playing offense is key.
Effective networking isn't forced conversations at mixers. It's providing value. One engineer became widely known by organizing bulk ski ticket purchases for the company. This created hundreds of low-stakes, positive connections based on a shared interest, which he could later leverage professionally.
At a mature company like Amazon, hyper-growth is over and promotions are slow. The fastest path to the top is to absorb skills and the resume brand for two years, then leave for a smaller, high-growth company where your "big tech" expertise is a rare and valuable asset, allowing you to leapfrog levels.