The base expectation for engineers is that you don't just build whatever you're asked.
You're supposed to push back on requirements, make sure you're building the right thing, uncover hidden unknowns, and act as a strong partner at least to product managers. As you go higher in levels you're supposed to work directly with stakeholders who don't even know what to ask for or how to solve their problems. They say "it hurts here" and your job is to figure out how to not make it hurt.
You cannot go above mid-level without this. Even juniors are expected to at least flag technical difficulties if the PM asks for something that would be too expensive to implement.
At senior and above you're expected to own OKRs, even entire products, and manage your roadmap. Especially when you get to L5, 6, 7 your job becomes "Make sure we are awesome in SomeArea". Nobody even knows what you do day to day. They care about outcomes. The details are up to you.
At mid-level I have seen people not get promoted because they only do what they're asked unquestioningly. This easily leads to failed projects/initiatives and ultimately kills companies.
At senior and above I have seen people get ~~fired~~ managed out for underperformance when they can't set a long-term vision, design a roadmap, and drive projects that may take months and years to implement.
A big part of the job is championing your technical vision of the product and advocating for that vision in product meetings, quarterly plannings, and overall making sure that as people work on individual projects/features they all drive towards your ultimate technical vision.
It's pretty fun :)
But maybe this is a silicon valley / bay area / tech culture thing? Hit reply.
Cheers,
~Swizec
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 ❤️