tbh none of this sounds like "senior engineer" qualities, and leans more toward "working at larger companies/in larger teams." From my perspective at startups/S

tbh none of this sounds like "senior engineer" qualities, and leans more toward "working at larger companies/in larger teams." From my perspective at startups/SMBs: > “I’ll Just Fix It” Yes please. Diving into unfamiliar areas of code and being able to fix problems outside of your wheelhouse is critically important. This doesn't mean stepping on people's toes or subverting processes e.g. design/code review, but just being willing to take ownership and not just shrug and say "not my problem". > You’re expected to build fences. Again, this is a big business thing and not a senior engineer thing. As a senior engineer in a team of 250 there are more barriers, but a senior engineer in a team of 20? You shouldn't be building very many fences. > Working Nights and Weekends This is a cultural thing that comes from the top. Goes beyond the scope of just senior engineers but I'll say that in my experience, if you're at a startup nobody is going to complain about you working nights and weekends. Again, this is a "large company" thing where slow and steady is more important than fast results. > Asking a Lot of Questions Dumb. I mean yes, if you're a senior engineer and asking questions like "what's a for loop" you'll raise eyebrows, but all of the best engineers (and managers for that matter) I worked with at Amazon etc all asked questions. In fact asking questions--extremely pointed and insightful questions--was basically all Jassy did in AWS meetings when I was there. Anyway this article is mainly crap, IMO.