Engineering Lead/Manager

Role Overview We are looking for a hands-on Engineering Leader/Manager – Performance, Chaos Engineering & Security to take end-to-end technical ownership of performance engineering, system resilience, chaos testing, and security validation. The individual will be responsible for defining the technical approach, driving solution design, developing testing strategies and frameworks, and ensuring the reliability, scalability, and security of complex distributed systems. The ideal candidate combines strong engineering fundamentals with technical leadership, capable of translating system-level requirements into practical engineering solutions while collaborating with development, QA, DevOps, infrastructure, and security teams. Key Responsibilities

1. Technical Ownership & Engineering Leadership • Own the technical strategy, architecture, and execution of performance, resilience, chaos, and security engineering initiatives. • Define engineering standards, testing methodologies, technical frameworks, and implementation guidelines. • Evaluate existing systems, identify architectural bottlenecks and risks, and drive technical improvements. • Lead technical discussions, make design decisions, and resolve complex engineering challenges. • Work closely with cross-functional teams to align engineering outcomes with product and business requirements. • Provide technical guidance, review implementations, and ensure quality of engineering deliverables.
2. Performance Engineering & Scalability • Design and execute performance, load, stress, endurance, and scalability testing strategies. • Identify performance bottlenecks across application, API, database, infrastructure, and distributed-system layers. • Conduct profiling, latency analysis, throughput evaluation, resource utilization analysis, and root-cause investigations. • Establish performance benchmarks, service-level indicators, and measurable performance targets. • Build and maintain reusable performance-testing frameworks and automation. • Validate system behaviour under high concurrency, high-volume data processing, and peak-load scenarios.
3. Chaos Engineering & System Resilience • Define and own chaos engineering strategies to validate system reliability and fault tolerance. • Design controlled fault-injection experiments covering service failures, network disruptions, resource constraints, and dependency failures. • Validate recovery mechanisms, failover strategies, retry logic, circuit breakers, and graceful degradation. • Identify single points of failure and resilience gaps across distributed systems and cloud-native environments. • Develop repeatable chaos-testing frameworks and integrate resilience testing into CI/CD pipelines. • Analyse experiment outcomes and drive remediation with engineering teams.
4. Security Engineering & Quality Validation • Own technical validation of application and API security controls. • Assess authentication, authorization, access-control mechanisms, and security-related failure scenarios. • Collaborate with security and development teams to identify vulnerabilities and validate remediation. • Integrate security and quality checks into automated testing and delivery pipelines. • Ensure that security validation complements performance, reliability, and overall system-quality objectives.
5. Test Frameworks, Automation & Observability • Design reusable testing tools, automation frameworks, and engineering utilities. • Develop test harnesses, workload generators, synthetic data, and event-simulation capabilities where required. • Establish observability practices using metrics, logs, traces, dashboards, and alerting. • Use telemetry and diagnostic data to identify root causes and validate system behaviour. • Drive continuous improvement in test coverage, execution efficiency, reliability, and engineering quality.
6. Technical Delivery & Stakeholder Management • Own technical planning, execution, prioritization, and resolution of engineering dependencies. • Define acceptance criteria and technical exit criteria for performance, resilience, and security testing. • Communicate risks, findings, root causes, and recommendations to technical stakeholders. • Ensure actionable findings are converted into remediation plans and tracked through closure. • Mentor engineers and promote engineering best practices across teams. Required Skills & Experience • Strong experience in software engineering, quality engineering, performance engineering, reliability engineering, or a related technical discipline. • Proven ability to own technical design and delivery for complex applications or distributed systems. • Hands-on expertise in performance testing, bottleneck analysis, profiling, and scalability validation. • Practical experience with chaos engineering, fault injection, resilience testing, or distributed-system failure analysis. • Working knowledge of application/API security testing and security-control validation. • Experience building automation frameworks, custom testing utilities, or reusable engineering tools. • Strong understanding of APIs, databases, networking, concurrency, distributed systems, and cloud-native architectures. • Experience with observability tools and root-cause analysis. • Ability to lead technical discussions, make engineering decisions, and work across development, QA, DevOps, and security teams. Preferred Tools & Technologies Experience with relevant tools in the following categories is desirable: • Performance testing: k6, Apache JMeter, LoadRunner, or equivalent. • Application testing and diagnostics: Playwright, browser developer tools, API testing tools, and profiling utilities. • Chaos engineering: LitmusChaos, Chaos Mesh, or equivalent fault-injection frameworks. • Cloud and orchestration: Kubernetes, containers, and public-cloud environments. • Observability: Prometheus, Grafana, distributed tracing, and centralized logging platforms. • Protocols and event-driven systems: HTTP APIs, messaging systems, and MQTT or similar protocols, where relevant. • CI/CD and automation: Pipeline integration, scripting, and test automation frameworks. Equivalent tools and demonstrable engineering capability are acceptable. Technical Owner Expectations The successful candidate must demonstrate the ability to: • Own technical outcomes rather than only execute predefined test cases. • Translate complex requirements into architecture, implementation, and validation strategies. • Independently investigate and resolve cross-layer technical problems. • Balance performance, resilience, security, and delivery considerations. • Build scalable, maintainable, and reusable engineering solutions. • Drive technical decisions and collaborate effectively with multiple engineering teams. Talent Acquisition Screening Criteria During initial screening, validate:
7. Technical ownership: Has the candidate owned architecture, technical decisions, or end-to-end engineering outcomes?
8. Performance engineering: Can the candidate explain a real performance bottleneck investigated and resolved?
9. Chaos and resilience: Has the candidate designed or executed fault-injection or resilience experiments?
10. Security expertise: What hands-on experience does the candidate have with application/API security validation?
11. Automation: Has the candidate developed reusable frameworks or custom engineering tools?
12. Distributed systems: Can the candidate explain failure modes and performance issues across application, infrastructure, and dependency layers?
13. Leadership: Has the candidate guided engineers, driven remediation, and communicated technical risks to stakeholders? Important Hiring Consideration Prioritize candidates who combine strong hands-on engineering depth with end-to-end technical ownership. Confirm whether performance engineering and chaos engineering are the core requirements, with security as a supporting responsibility, or whether all three areas require equal depth. This distinction will materially affect candidate availability and screening criteria.