Remix.run Logo
djb_hackernews 8 hours ago

I work at a large software company, senior engineers here are essentially technical leads for a team or a subsystem. They are my equals when it comes to level, often getting paid a lot more than me for high performers.

I'm here to help the team make decisions, but I delegate as much of the opinion having to my senior engineers. To have an opinion they need a bunch of inputs, sometimes getting those inputs isn't as natural as the technical inputs, that's where I come in.

Senior engineers are still involved in cross cutting technical concerns but for any work that is bounded by our team I'd be working with them scope out the work as requirements or use cases we give to mid level or early career engineers on the team to disambiguate with the senior engineer as a consult/negotiate.

fleabitdev 8 hours ago | parent [-]

Just a misunderstanding, then - thanks for taking the time to clear it up, I appreciate it.

Strange that your company calls its tech leads "senior engineers", when every other company is going through title inflation! Hiring for those roles must be a pain.

taude 3 hours ago | parent [-]

I've never worked at a company that had a "tech lead" role as part of official HR levels. Junior engineers (couple levels) -> Senior Engineers (couple levels) -> Principle/Staff (couple levels) -> some form of really rare role of Distinguished.

Senior Engineers should definitely do what I think earlier comment thought of as "tech lead". Should be able to run juniors, solve cross-cutting needs, etc....