Software Diagnostics And Performance Test Engineer

SOTI; Ernakulam; On-site; INR 1,800,000 - 2,400,000; Full time

Job summary

SOTI is seeking an experienced Performance/Reliability Engineer to diagnose complex software issues across application, system, network, and infrastructure layers. You will analyze logs, profiles, and traces to identify bottlenecks and craft tests to validate fixes.

You will mentor others in debugging techniques, collaborate with developers to uncover root causes, and help optimize product performance and reliability.

Qualifications

• 5+ years of software engineering, performance engineering, systems engineering, reliability engineering, production troubleshooting, or a closely related discipline.
• Proficiency in Java, C++, C#, Python and ability to read unfamiliar code.
• Strong understanding of OS concepts and networking fundamentals.
• Experience diagnosing concurrency, latency, or scalability issues.

Responsibilities

• Investigate complex and ambiguous software failures and performance problems.
• Perform deep root-cause analysis across application, system, network, database, and infrastructure layers.
• Analyze logs, traces, and profiling data to identify bottlenecks and regressions.
• Design experiments and develop diagnostic scripts or small tools to accelerate investigations.
• Collaborate with developers to identify root causes and communicate actionable findings.
• Mentor engineers in systematic debugging and performance analysis.

Skills

Java

C++

C#

Python

Software debugging

Performance analysis

Root-cause analysis

Networking basics

Log analysis

Job description

Job Description:

SOTI is committed to providing its employees with endless possibilities; learning new things, working with the latest technologies and making a difference in the world.

SOTI does not charge any fees at any stage of the recruitment process. You can verify the authenticity of any SOTI job opportunities by visiting SOTI Careers. SOTI shall not be liable for any fraudulent recruitment activities carried out by unauthorized individuals or organizations.

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, orlong-running conditions.
• Understand product architecture and critical customer workflowsdeeply 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, rootcause, impact, and recommended corrective actions.
• Build and maintain diagnostic knowledge, troubleshooting methodologies, and internal technical documentation.
• Mentor other engineers in systematic debuggingand root-cause analysis.

Must-have qualifications

1. Technical

• 5+ years of software engineering, performance engineering, systems engineering, reliability engineering, production troubleshooting, or a closely related discipline, preferably in a product-based software company.
• Programming/debugging ability inat least one major language such asJava, C++, C#, Python, etc.
• Strong ability to read and understand unfamiliar application code.
• Demonstrated experience troubleshooting complex software problems.
• Strong understanding of operating-system concepts: processes, threads, memory, CPU, file I/O, sockets, synchronization, resource utilization
• Strong understanding of networking fundamentals: TCP/IP, HTTP/HTTPS, DNS, connection management, latency, timeouts, retransmissions
• Experience analyzing logs and traces across multiple components.
• Experience with application profiling and/or performance analysis.
• Hands-on experience creating, reviewing, and executing Performance Test Cases for complex software products.
• Experience diagnosing concurrency, latency, resource contention, or scalability issues.
• Ability to interpret performance test results, compare them with baselines, identify regressions, and connect findings back to product behavior or code-level causes.
• Ability to formulate hypotheses andsystematically validate them with evidence.

2. Behavioral

• Exceptional curiosity about how software systems work.
• Strong interest in learning the product deeply rather than treating testing as a black-box activity.
• Strong analytical and problem-solving skills.
• Comfortable working with incompleteor ambiguous information.
• Willingness to challenge assumptions.
• Persistence when the first explanation isn't the real root cause.
• Ability to communicate complex technical findings clearly.
• Comfortable collaboratingwith developers without simply handing problems back to them.
• Strong ownership of difficult investigations

#LI-AS2

Requirements: