Don't feed the troll 🧌 saying Steve doesn't know what he is talking about. This article is pretty non-controversial. I'm surprised the troll decided to react to it
1 week ago | 8
Saw a similar post on linkedin several days ago. Nice copy pasterino. Used AI to rewrite it? Still obvious! Bye!
1 week ago | 2
A Life Engineered
Here are the 3 things I look for in seniors and above.
They bring clarity to chaos. When projects are messy and requirements are unclear, they cut through the noise. They ask the questions that expose hidden assumptions and turn vague goals into actionable plans.
They elevate everyone around them. They teach, not just critique. They foster discussions and make the whole team smarter. They share knowledge in ways that stick and help others level up their own capabilities.
They own the outcome—not just the code. They care about whether the feature actually solves the problem, not just whether it works as specified. They think about user impact, business metrics, and long-term maintainability.
If you're already doing these things, you're more senior than you think.
I've seen people with "Junior" titles who operate at senior levels and people with "Senior" titles who still think like juniors.
The difference isn't years of experience or lines of code written.
It's about how you approach problems, how you work with others, and what you take responsibility for.
The best part is that these behaviors are learnable. You don't need permission to start bringing clarity, elevating teammates, or caring about outcomes.
Are you already operating at a senior level without the title? Which of these resonates most with your current role?
For more insights on advancing your tech career: alifeengineered.substack.com/
#SeniorEngineering #TechCareers #CareerAdvancement #TechLeadership #SoftwareEngineering
1 week ago | [YT] | 223