> Markdown version of [/jobs/ext/2508726-load-test-engineer](https://www.wearedevelopers.com/jobs/ext/2508726-load-test-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Load Test Engineer

- **Company:** CYREX, INC.
- **Location:** United States (Remote available)
- **Experience:** Experienced
- **Contract:** Permanent contract
- **Skills:** Amazon Web Services, Distributed Systems, Protocol Buffers, Hypertext Transfer Protocols (HTTP), Apache JMeter, Python (Programming Language), PostgreSQL, Load Testing, Open Source Technology, Software Engineering, Test Data, TypeScript, WebSocket, Real Time Systems, ReactJS, Gatling, Backend, Codebase, Front End Software Development, Terraform, Grpc, Golang
- **Published:** August 11, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=04cc248e73bdbc1e

## About the Role

* 4+ years of software engineering experience, with meaningful ownership of what you shipped.
 * Strong Python skills. This is the core language for the role.
 * Hands-on cloud experience, ideally with AWS, including infrastructure as code and containers , and an understanding of what happens technically and financially when infrastructure is scaled aggressively.
 * Enough breadth to confidently maintain a typed backend and React frontend you didn't originally build, even if neither is your primary specialism.
 * A practical understanding of distributed systems and their failure modes, including timeouts, back-pressure, connection limits, resource contention, and the difference between a system that is slow and one that is actually failing.
 * The communication skills to lead a technical session with a customer, explain what you're seeing clearly, and make sound engineering recommendations.
 * Excellent spoken and written English.
 * Experience with performance or load-testing tools such as Locust, k6, JMeter, Gatling, or tooling you've built yourself is a strong advantage.
 * Experience with games, real-time systems, or high-traffic consumer platforms is also useful, but not required.

## Description

We're looking for an engineer who is genuinely comfortable moving across a stack and equally comfortable working directly with a customer. You write strong Python. It's the language of our test scenarios and much of the tooling around them, so it's where you'll spend most of your development time. But you're not attached to staying in one language: keeping the platform healthy means being willing to work in Go, TypeScript, Terraform, and AWS as the situation demands. You're comfortable working in codebases you didn't write. A mature platform benefits from careful, well-scoped changes rather than unnecessary rewrites. You can step into unfamiliar code, understand how it works, diagnose the actual problem, fix it properly, and ideally leave things a little better than you found them. You find systems under stress interesting. When something starts falling over at high concurrency, your instinct is to understand exactly why. You're comfortable digging through metrics,
traces, logs, and application behaviour until you can explain what is actually happening, and you know the first explanation is not always the right one. You can also communicate that reasoning clearly to customers. Not in a sales sense, but as an engineer: explaining what a latency curve is telling their team, challenging a test scenario that won't answer the question they think it will, and staying calm and methodical when a live test produces an unexpected result. Our customers are technical. They rely on our judgement as much as they rely on our tooling. Finally, you're pragmatic about the less glamorous parts of performance engineering. Test data, account pools, flaky protocol clients, awkward environments, and reproducing behaviour that only appears under load are not distractions from the job, they are the job. The engineers who do well here enjoy solving those problems too. The stack Test engineering: Python, using open-source load-testing tooling that we
extend heavily Platform backend: Go, PostgreSQL Frontend: React, TypeScript Infrastructure: AWS, infrastructure as code, containers Protocols: HTTP, WebSockets, gRPC, protobuf, and occasionally bespoke binary protocols


## Related Videos

- [Scaling: from 0 to 20 million users](https://www.wearedevelopers.com/videos/676-scaling-from-0-to-20-million-users)
- [Exploring the Power of gRPC-Gateway for Writing RESTful Services](https://www.wearedevelopers.com/videos/2072-exploring-the-power-of-grpc-gateway-for-writing-restful-services)
- [Go with the Flow: Stop the Leaks Before Your Memory's a Waterfall!](https://www.wearedevelopers.com/videos/100073-go-with-the-flow-stop-the-leaks-before-your-memory-s-a-waterfall)
- [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock)
- [Super scaling for the Super Bowl: How to survive 30 million users hitting your backend in 30 minutes](https://www.wearedevelopers.com/videos/100356-super-scaling-for-the-super-bowl-how-to-survive-30-million-users-hitting-your-backend-in-30-minutes)
- [The user in the eye of the Cargo1492 storm](https://www.wearedevelopers.com/videos/96-the-user-in-the-eye-of-the-cargo1492-storm)

## Related Articles

- [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)
- [The 8 Best Code Testing Tools](https://www.wearedevelopers.com/magazine/402-the-8-best-code-testing-tools)
- [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated)
- [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)