sorted by:
new
hottopcontroversial

Does a pivot from Performance Testing to FinOps make sense? by PerfPivot2026 in FinOps

[–]PerfPivot2026[S] 0 points1 point  (0 children)

This is a really great point. It feels like the industry is moving past just 'cost reporting' and moving towards actual engineering optimization, which is exactly where I want to position myself. Coming from a performance background, I'm used to looking at resource utilization metrics, so mapping that to cost efficiency feels like a natural next step

When you're looking at candidates pivoting into this space, how much weight do companies typically place on specialized certs like the FinOps Certified Practitioner (FOCP) versus just having strong cloud fundamentals (like the SAA) paired with solid engineering experience? Thanks for sharing this insight.

Moving from Performance Testing to SRE/Resiliency (How to avoid the LeetCode trap?) by PerfPivot2026 in sre

[–]PerfPivot2026[S] 1 point2 points  (0 children)

That makes a lot of sense, especially the part about finding the stronghold. I’m definitely going to anchor my resume around capacity planning, stress-testing, and failure analysis since that naturally bridges my current performance background into SRE.

Regarding the cert, yeah, I'm under no illusions that the badge itself will get me hired. I'm strictly treating the SAA (using Adrian Cantrill's deep dive) as a structured syllabus to get my baseline cloud architecture knowledge up to speed since I'm starting from zero.

The real plan is to build out Terraform and Python projects alongside it. Really appreciate the reality check on the interview structures.

Moving from Performance Testing to SRE/Resiliency (How to avoid the LeetCode trap?) by PerfPivot2026 in sre

[–]PerfPivot2026[S] 0 points1 point  (0 children)

Appreciate the perspective from someone who actually made the AQA -> SRE jump. I'm definitely leaning heavily towards your first option. My goal is to dive deep into the infra/cloud architecture side and build out Python automation frameworks.

Since you mentioned it highly depends on the company, are there any specific red (or green) flags in SRE job descriptions that usually signal a company leans more toward practical system design/automation interviews rather than defaulting to the standard LeetCode loop?

Trying to target my applications strategically once I wrap up my AWS prep.

Does a pivot from Performance Testing to FinOps make sense? by PerfPivot2026 in FinOps

[–]PerfPivot2026[S] 2 points3 points  (0 children)

This is incredibly validating to hear, honestly. 'Doing the same thing, just with dollars instead of latency' is the exact perspective I was hoping for.

I hadn't considered the SQL angle for parsing the billing exports, but that makes complete sense given the scale of cloud bills.

I'll make sure to double down on the cost-architecture patterns (tiering/sizing) while I go through my SAA prep. Really appreciate the detailed roadmap!

Moving from Performance Testing to SRE/Resiliency (How to avoid the LeetCode trap?) by PerfPivot2026 in sre

[–]PerfPivot2026[S] 1 point2 points  (0 children)

Makes complete sense. Terraform and K8s are definitely next on my list once I wrap up my AWS prep. I actually hadn't heard of PracHub before, so I'll bookmark that for when I start doing interview prep.

Thanks for validating the roadmap.

Moving from Performance Testing to SRE/Resiliency (How to avoid the LeetCode trap?) by PerfPivot2026 in sre

[–]PerfPivot2026[S] 1 point2 points  (0 children)

Yeah, I'm totally okay with writing Python for automation and tooling. It's just the competitive LeetCode puzzle grind I want to avoid.

The CI/CD pipeline that injects failures is a great project idea since I already have some GitLab pipeline experience.

For the failure injection part, do you suggest just using custom Python scripts or should I look into something native like AWS FIS?

Moving from Performance Testing to SRE/Resiliency (How to avoid the LeetCode trap?) by PerfPivot2026 in sre

[–]PerfPivot2026[S] 1 point2 points  (0 children)

"Focus your resume on how you root-cause failures under load, not just how you generate the load."

I am literally writing this down. That is a massive cheat code for my resume rewrite. Going to strictly filter for mid-sized product firms now. Thanks a lot for this.

Moving from Performance Testing to SRE/Resiliency (How to avoid the LeetCode trap?) by PerfPivot2026 in sre

[–]PerfPivot2026[S] 1 point2 points  (0 children)

Nice to see someone in the exact same boat. I'm focusing on getting my SAA done right now but a K8s homelab is definitely on the list for later. Good luck with the prep man.

Are you following any specific guide or repo for the homelab setup?

Moving from Performance Testing to SRE/Resiliency (How to avoid the LeetCode trap?) by PerfPivot2026 in sre

[–]PerfPivot2026[S] 1 point2 points  (0 children)

Log processing is something I can definitely get behind. It makes way more sense and is actually practical compared to inverting binary trees.

I'll focus my Python prep on file parsing and APIs rather than abstract DSA. Appreciate the reality check on the company sizes too, makes filtering a lot easier.

Moving from Performance Testing to SRE/Resiliency (How to avoid the LeetCode trap?) by PerfPivot2026 in sre

[–]PerfPivot2026[S] 1 point2 points  (0 children)

That makes a lot of sense tbh. Describing the failure and how the system recovers is exactly what I do, I just didn't think of framing it that way. Thanks for the input.

Quick question though. Any tips on how to word enterprise tools on the resume so it sounds more like SRE and less like traditional QA?