Software Diagnostics & Performance Engineer

What you will do

• Investigate complex and ambiguous software failures and performance problems.
• Perform deep root-cause analysis across application, system, network, database, and infrastructure layers.
• Analyze application logs, system logs, stack traces, thread dumps, heap dumps, metrics, traces, and profiling data.
• Analyze network traffic and protocols to identify latency, connectivity, retransmission, timeout, and communication issues.
• Investigate issues that occur only under specific workloads, concurrency levels, configurations, environments, or long-running conditions.
• Understand product architecture and critical customer workflows deeply enough to reason about failure modes.
• Learn the product in depth, including core workflows, customer usage patterns, deployment models, and performance-sensitive areas.
• Design experiments to isolate variables and prove or disprove hypotheses.
• Develop diagnostic scripts, instrumentation, and small tools when necessary to accelerate investigations.
• Perform exploratory testing and deliberately challenge system assumptions to discover weaknesses and failure modes.
• Investigate performance degradation, scalability limitations, resource exhaustion, latency spikes, and throughput bottlenecks.
• Create meaningful Performance Test Cases based on product architecture, customer workflows, expected load patterns, scalability goals, and known risk areas.
• Review Performance Test Cases created by other engineers to ensure coverage, clarity, workload relevance, data validity, and alignment with product behavior.
• Execute Performance Test Cases, analyze results, identify bottlenecks or regressions, and communicate findings with clear evidence and recommended actions.
• Correlate evidence across multiple components of distributed systems.
• Work with developers to identify the actual root cause rather than simply identifying the component where the symptom appeared.
• Clearly communicate technical findings, evidence, root cause, impact, and recommended corrective actions.
• Build and maintain diagnostic knowledge, troubleshooting methodologies, and internal technical documentation.