3 ms·
The proposed split here between product and infrastructure doesn’t map to my experience or skill set well. In my last job, I was lead of a team called Security
by labster 5y ago
The proposed split here between product and infrastructure doesn’t map to my experience or skill set well. In my last job, I was lead of a team called Security and Infrastructure, but the team was renamed by the CTO to Production Engineering. The tasks were substantially the same.
But it’s not just word choice bugging me — delivering for clients and writing good code are not orthogonal, even if there’s often a trade-off. Continually delivering for clients is enabled by a solid, well-factored, flexible base. System-level thinking needs both the how and the why.
- Bilal_io 5y agoWhen I read "product engineer" and "production engineering" I do not think they're the same.
- xmprt 5y agoProduction Engineer sounds like an engineer whose goal is to enable the rest of the engineering team to deliver products. You're not directly delivering the products. To me, the split between product and infrastructure is based on who your customers are. If your customers are other engineers within your company, then you're in infrastructure. If your clients are external then you're in product.