u/BoysenberryOk1053

Realised our engineering brand is weaker than we thought because we cannot talk about delivery performance with actual numbers

Had an interview recently with a strong senior engineering candidate and they asked questions I honestly was not prepared for in enough detail. Things like deployment frequency, lead time for changes, and incident recovery metrics.

I gave high-level answers, but afterwards it hit me that we mostly operate on intuition rather than properly measured engineering performance. Internally we know where the bottlenecks are, but externally we cannot communicate operational maturity in a convincing way.

What surprised me is how much this affects hiring and company perception. Strong candidates increasingly evaluate engineering teams the same way buyers evaluate SaaS products, they expect measurable operational credibility, not just good culture and interesting work

reddit.com
u/BoysenberryOk1053 — 12 days ago
▲ 7 r/Cloud

Took over DevOps for a mid sized team last quarter and started mapping everything a single change touches before it reaches production. The number ended up being around twelve separate systems. Jira, GitHub, dedicated test tooling, SAST scanning, PR automation, CI/CD, Terraform, Slack approvals, AWS, CloudWatch, plus internal docs that are already half out of date. At this point it feels like every additional handoff introduces another place for delivery to slow down or fail.I’m not precious about any individual tool, I just want the path from written requirement to running service to stop looking like a Rube Goldberg machine.

reddit.com
u/BoysenberryOk1053 — 20 days ago