3 ms·

To me being a senior software engineer means that when your production system goes unstable from gremlins or cosmic rays or other mysterious sources of chaos an

To me being a senior software engineer means that when your production system goes unstable from gremlins or cosmic rays or other mysterious sources of chaos and the business that pays for your food is in jeopardy, there's nobody to pass the buck to. You just have to buckle down and figure it out or update the resume and start working on your excuses or apologies to newly unemployed coworkers and their families.

Vinnl 2y ago
Well, except for perhaps to a staff engineer. Or a senior staff engineer. Or a principal engineer. Or maybe a senior staff principal engineer? The VP of Engineering? The CTO?
- bux93 2y ago
  a vendor
  - zelphirkalt 2y ago
    Vendor is a trump card in this game. Surely no one can do better than a vendor, from which we buy a solution! Best of all, we can then shift the blame too! Our customers cannot use our product? It is the vendor's fault!
    - bravetraveler 2y ago
      Don't forget the venerable Financial Institutions and their cousin, Insurance
    - deleted 2y ago
      [deleted]
consf 2y ago
So is it not just about coding but also about owning the issues?
- spacephysics 2y ago
  To me senior means ownership above everything else. Owning a part of the system implies that you’ll do (or organize) the risk analysis of new features, cost-benefit of bug fixing, coding (or at least outlining the design), support via documentation, communicating to product owner/stake holders/support. Elevating from senior to staff (or principal etc) would be projects with larger scope, moving parts, and higher risk/reward. I think its easier to see a junior to senior (if say we have two buckets). After senior it gets tough. Does their role involve purely tech lead/coding? Or some managerial politics, pushing engineering culture/direction in whichever way is best for the company. Really depends on the company itself, which I think is why it’s hard to standardize. CTO at my own startup? Really a glorified senior dev with some communication and business mixed in. Upper senior dev at Netflix? Most likely masters or PhD level (not necessarily with the degree) understanding of some C.S. concepts that matter at that scale.

Vinnl 2y ago

Well, except for perhaps to a staff engineer. Or a senior staff engineer. Or a principal engineer. Or maybe a senior staff principal engineer? The VP of Engineering? The CTO?

bux93 2y ago
a vendor
- zelphirkalt 2y ago
  Vendor is a trump card in this game. Surely no one can do better than a vendor, from which we buy a solution! Best of all, we can then shift the blame too! Our customers cannot use our product? It is the vendor's fault!
  - bravetraveler 2y ago
    Don't forget the venerable Financial Institutions and their cousin, Insurance
  - deleted 2y ago
    [deleted]

consf 2y ago

So is it not just about coding but also about owning the issues?

spacephysics 2y ago
To me senior means ownership above everything else. Owning a part of the system implies that you’ll do (or organize) the risk analysis of new features, cost-benefit of bug fixing, coding (or at least outlining the design), support via documentation, communicating to product owner/stake holders/support. Elevating from senior to staff (or principal etc) would be projects with larger scope, moving parts, and higher risk/reward. I think its easier to see a junior to senior (if say we have two buckets). After senior it gets tough. Does their role involve purely tech lead/coding? Or some managerial politics, pushing engineering culture/direction in whichever way is best for the company. Really depends on the company itself, which I think is why it’s hard to standardize. CTO at my own startup? Really a glorified senior dev with some communication and business mixed in. Upper senior dev at Netflix? Most likely masters or PhD level (not necessarily with the degree) understanding of some C.S. concepts that matter at that scale.