4 ms·
I think the article is reasonable but it suffers from the imprecision of "senior" as many things do. What is a 'senior' engineer in a startup, or at a mid-size
by ChuckMcM 8y ago
I think the article is reasonable but it suffers from the imprecision of "senior" as many things do. What is a 'senior' engineer in a startup, or at a mid-size private company, or a large public company? All of those companies have "senior engineers" but they aren't easily swapped out for each other.
These are my definitions, at a startup a senior engineer is one that is broad enough in their experience to have gone deeply into one area and at least lightly into several others. They understand what technical debt it and when to use it, and when to avoid it. What is more, they can communicate what needs to be done to a more junior engineer.
In a mid-size private company a senior engineer knows all of the forces that are being applied to their area of expertise, they know what the cost constraints are on the solution, they know what the time constraints are. They understand the area fully and can review other's work and participate productively in design reviews and product planning sessions. They can be an axis of excellence by leading by example and surfacing things that need to be fixed early.
At a large publicly traded company a senior engineer is one who can relate the business to the engineering effort to insure that they are doing the engineering that is needed and more importantly they are not doing engineering that is not needed. To paraphrase, "With great resources comes great re-invention." Large well funded engineering teams tend to re-invent the wheel because they can, not because they need to. And as a result can become mired in self inflicted complexity. It is the role of the senior engineers to see to it that it doesn't happen.
Very different jobs.
- sethammons 8y agoWhy should not all those be together and be the bar for senior starting at the start-up layer? I think the only big difference is working/navigating in a small or large org, no?
- seren 8y agoIf you look at the both extreme, large public company and a start up, in the former case, you already have customers, a viable business model, and a legacy product. As an engineer, your first requirements would be to "not break things" going forward. Sure you want to gain some market share from competitor but you already have some momentum, otherwise your job would not exist. So you need to upgrade or add features to your product in a controlled way. Your 20 years customer might not want to have to learn a new interface just because you can deliver it. At a start up, even if you have your first customers, you want to deliver a product or more features as quickly as possible starting from scratch. Possibly, you also want to be able to pivot totally if the first idea does not stick. It is great if you can do well in both environment, but usually, this is different skill set, and I would even say personal inclination. You'll likely have a hard time to convince a start up engineer to work on COBOL code base on a mainframe.