I was talking to a coworker the other day and mentioned that for us tech lead is a role, not a title, and comes with no extra pay. He blue-screened. Why would you do that? 🤨
Indeed. Why would you do that?
- Bigger better problems
- Slope
- Luck surface area
Opportunity likes to dress in dirty overalls and look like work. Plus tackling new challenges is fun.
Bigger better problems
As a tech lead you get to solve bigger better problems. Instead of pre-chewed agile stories that slice and dice a project into digestible chunks, you get to do the chewing.
Product owner not sure if their ideas are feasible? You get to chat.
Product owner struggling to break down a project? You get to help.
Head of engineering not happy with current tooling looking for alternatives? You get to do the research and join the calls.
Big new initiative with uncertain staffing, fuzzy requirements, and spanning multiple teams? You get to clarify requirements, define which teams are needed, establish a roadmap, and figure out how all these teams can work together.
A lot of that happens "in the room", you don't decide on your own. This can be months before a project hits anyone's sprint.
Slope
A little bit of slope beats a lot of y-intercept.
You increase slope by doing hard things. Work at the edge of your ability, press haaaard at the wall, keep pressing. And then it moves.
Boop.
What used to be hard now feels easy. Your new default.
Plateaus happen when you work on autopilot. True in relationships, true at the gym, true in your career. You need bursts of extra effort balanced with recovery to advance.
Peak Performance is my favorite book exploring this concept in great detail.
Luck surface area
Your luck is a function of what you do and how many people know about it.
By being "in the room" you increase both factors. You get the opportunity to do more meaningful/impactful/cool/interesting work and more people know about it.
Coordinating with many teams automatically gives you more visibility across the company. Steering big initiatives makes you more visible to leadership. The bottom axis.
And you get to make a bigger impact. Like when I spotted a smöl tweak that solved a big performance problem, but if I wasn't "in the room", I wouldn't even know we were talking about it. The left axis.
But why?
Career capital my friend.
You can leverage these things later.
Cheers,
~Swizec
Continue reading about Why take a bigger role for no bump in pay
Semantically similar articles hand-picked by GPT-4
- On becoming tech lead
- Reader question: Work at a big international or a local studio?
- When to join and leave a company, project, or trend
- The role of a senior+ engineer
- What you can expect from the Senior Mindset Retreat
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️