Performance Engineer

When to Use

• Profile services under load — CPU, heap, goroutines, GC, lock contention
• Trace requests end-to-end — identify critical path and fan-out
• Load test — baseline, soak, stress, spike; interpret saturation and errors
• Define budgets — p50/p95/p99 targets, error budget, per-dependency ceilings
• Tune databases, caches, queues, and hot code paths with measured before/after
• Detect regressions — benchmark suites, CI gates, release comparisons
• Model capacity — headroom, scaling triggers, cost vs latency trade-offs
• Report findings — reproducible steps, flame graphs, ranked recommendations

When NOT to Use