Senior Software Engineer (Rust) - Proxy Services

The Role

The Senior Software Engineer (Rust) - Proxy Services will own the conversion of Securly's web filtering proxy business logic from C++ to production Rust — maintaining behavioral parity across a high-throughput proxy that handles HTTP/HTTPS traffic for millions of students daily.

A modern, memory-safe Rust proxy is already underway at Securly. When you join, the initial Rust proxy is in production and your mission is the next phase: integrating and converting the existing C++ business logic into production Rust. This means reading C++, reasoning about behavior, and re-implementing it correctly — including HTTPS tunneling, TLS interception, JavaScript injection into HTML responses (the ACP-48 shim pattern), and Redis-based policy lookups. Precision and behavioral correctness are non-negotiable.

At L5, you are not just a skilled implementer. You own the conversion strategy, define the phasing and testing approach, surface architectural risks to the L6 lead, and raise the Rust competency of the broader proxy team.

What You'll Do

• Own the C++ to Rust conversion strategy: define the porting sequence, identify behavioral risks, and establish the testing approach that gives confidence in parity before cutover.
• Read, debug, and deeply understand existing C++ proxy business logic, then port it to production Rust with full behavioral parity.
• Build and maintain forward proxy operations: HTTPS CONNECT tunneling, TLS interception, HTTP/1.1 and HTTP/2, header manipulation, connection pooling.
• Implement JavaScript content script injection into HTML responses (ACP-48 shim pattern) — enabling proxy-side injection for customers not served by the Chrome extension.
• Integrate Redis-based real-time policy lookups; handle Redis failure modes gracefully; document degraded-mode behavior and validate it under load.
• Profile and benchmark proxy performance under high-concurrency load; use flame graphs to validate changes; maintain a written performance baseline document.
• Identify gaps in the existing C++ codebase where behavior is unclear or likely incorrect — treating the port as an opportunity to improve, not just replicate.
• Mentor junior Rust engineers on ownership models, async patterns, and systems-level debugging.
• Collaborate closely with the Proxy Hardening engineer on shared infrastructure and production issues.

Skills & Requirements

Who You Are

• You are the engineer who reads crash dumps for fun. Memory safety, ownership models, and undefined behavior are topics you have strong opinions about.
• You have ported or rewritten production systems before and understand that behavioral parity is significantly harder than it appears.
• You can navigate a large legacy C++ codebase without documentation. You treat it as archaeology, not an obstacle.
• You take correctness seriously — you do not ship a port until you are confident it behaves identically to what it replaced, and you have the test coverage to prove it.
• You define the plan, not just execute it. You produce written conversion strategies, risk registers, and performance baseline documents.
• You make other engineers better. You are sought out for Rust code reviews and junior engineers ship better code after working with you.

What It Means to Be L5 at Securly

L5 at Securly is a Staff Engineer. You are the technical owner, not just an implementer.

• Drive technical direction for your initiative end-to-end: from architecture to production, with minimal oversight from your engineering manager.
• Identify and resolve ambiguity in requirements, system boundaries, and design tradeoffs without waiting for a fully-formed spec.
• Mentor L3/L4 engineers on the team: code reviews, design feedback, pairing, and raising the bar for what production-quality work looks like.
• Partner with your L6 technical lead and the Distinguished Engineer on architectural decisions, surfacing tradeoffs clearly rather than deferring them upward.
• Contribute to cross-team engineering standards: you are expected to influence practices beyond your immediate squad.
• Translate technical context into clear written artifacts that non-engineers (PM, Support, Leadership) can act on.
• Participate in on-call rotation and own the full incident lifecycle for your system: detection, diagnosis, resolution, and retrospective.

About Securly

Benefits