Co-Founder / CTO (Rust)

We're looking for a technical co-founder to own the infrastructure layer of perfscale — the distributed test execution engine, the metrics pipeline, and the systems that let a single engineer run 1M requests/sec without managing servers.

The core of what we're building is written in Rust. If you care deeply about systems programming, correctness under load, and the craft of building infrastructure that other engineers trust their production systems to — this is the role.

What you'll own

• Test execution engine — Distributed coordination of k6, Locust, and JMeter agents; scheduling, isolation, resource management
• Metrics pipeline — High-throughput ingestion, aggregation, and real-time streaming of test metrics (p99, RPS, error rate) to dashboards and exporters
• Agent runtime — The Rust binary that runs on customer infrastructure (VPC runners), manages test lifecycle, and phones home to the control plane
• API & data layer — REST/gRPC API, time-series storage, result querying
• Architecture decisions — You decide the tech stack, make the hard trade-offs, and set the engineering culture

What we're looking for

• Rust proficiency — You've built production systems in Rust, you understand ownership/lifetimes intuitively, and you have opinions about async runtimes (Tokio, async-std) and when to use them
• Distributed systems experience — You've built or operated systems where failures are expected: network partitions, agent crashes mid-test, partial metric delivery
• Performance engineering mindset — You think in terms of p99, backpressure, and syscall overhead. You've profiled under load and know what flamegraphs are telling you
• Product instinct — You've built something engineers use and you understand that DX is not secondary to performance; it's the product
• Bonus: experience with eBPF, WASM runtimes, or building language runtimes/sandboxes

What we offer

• Equity: 5–15% — co-founder stake with full technical ownership
• Competitive salary once revenue supports it
• Full remote, async-first, no sprints, no standups
• Greenfield architecture — you're not inheriting a 10-year-old codebase
• The technical problem is genuinely hard: multi-tenant test isolation, sub-second metric aggregation at scale, agent coordination under unreliable network conditions

The stack today

• Agent / execution engine: Rust (Tokio)
• Control plane / API: Go
• Frontend: Next.js (TypeScript)
• Infra: Kubernetes, Postgres, InfluxDB, Redis
• CI/CD: GitHub Actions

The architecture is intentionally simple at this stage — we optimise for correctness and developer velocity, not premature abstraction.

How to apply

Send a note to [jobs@perfscale.su](mailto:jobs@perfscale.su?subject=Application: Co-Founder / CTO Rust) — tell us about a system you built in Rust that you're proud of and what was hard about it. GitHub profile welcome but not required. No whiteboard puzzles.