Senior Engineer II, Proxy

Description

The company builds browser security for people and AI agents. Its platform stops attacks arriving through web, document and email channels before they get to the person using them, and a newer product extends that protection to the AI agents working beside each employee.

Large global firms, including Fortune 500 companies and government agencies, rely on the company, and top-tier investors back it.

You would join the team that runs the ingress proxy, the main entry point into the product for most users. Customers increasingly want one set of controls covering both people and agents, and the proxy is where that starts. Your choices will shape both security and performance.

The team is small, gives people room to make their own calls, and keeps process light. Expect to own features from design through production and to help decide how the system evolves. The culture rewards ownership, direct communication, cross-team work and high standards.

Responsibilities

• Help extend the proxy to handle agent traffic.
• Take features from design through to production.
• Own the full lifecycle of the services you build, working alongside teammates who know the system well.
• Help decide how the system changes over time.
• Work with your team and other teams to learn what customers need and tighten requirements, then build, review and ship changes.

Requirements

• 5+ years of experience building and running production systems.
• Hands-on work building and maintaining production systems, leaning toward languages that give strong safety guarantees in critical software.
• Working knowledge of HTTP and TLS.
• You care about correctness, scalability and maintainability, not only shipping.
• You have tuned latency and throughput in networked software using profilers and efficient concurrency models under heavy load.
• You have built secure systems, modeled threats, mitigated vulnerabilities and protected data integrity across distributed environments.
• You have built and run high-concurrency async services in production and understand backpressure, cancellation and the failure modes of non-blocking I/O.
• You have modernized legacy systems while they stayed live, moving traffic over in stages and refactoring toward sturdier designs. You weigh language trade-offs in favor of long-term maintainability and security.
• You have used fuzzing, property-based tests and integration tests to check correctness under failure.
• You can explain and defend architecture decisions to a team and share secure development practices.
• You use LLMs selectively to speed up your work and check their output for correctness, maintainability and fit with the architecture and wider engineering goals.
• Experience in Rust or Go is strongly preferred.