Inside Production Engineering at Jane Street

RESUMEN

En 30 segundos

Jane Street production engineers Mark, Liora, and Joseph explain their support rotations and software projects. They discuss triaging trading-system issues, working with application developers, improving shared tooling, and learning through mentorship.

1Two sides of the roleProduction engineers handle live support and develop software to improve the support infrastructure. The speakers say they spend about a third of their time on support rotation.
2First respondersOn rotation, an engineer is responsible for a portion of the infrastructure, responding to application issues and user questions during the trading day.
3Communication under uncertaintyThe work involves talking to developers and traders, making progress with incomplete information, and conveying what is known quickly and accurately.
4Projects alongside developersMulti-month deployments with application teams help reduce support burden, build engineering skills, and spread practices that make systems easier to understand.
5Shared support toolingProduction engineers also build alerting libraries, toil tracking and visualization, and incident management systems used across the firm.

Conclusiones

Production engineers divide their time between live support and software projects that improve support.
During a support rotation, engineers monitor systems, answer questions, and triage production issues.
The role calls for clear communication and action under uncertainty across technical and trading teams.
Multi-month projects with application developers provide mentorship and spread production engineering practices.
Internal tooling, including alerting and incident management, helps support teams across the firm.

TemasObservabilidad y fiabilidad Software engineering Careers

TEXTO COMPLETO

Lee el texto editado por capítulos

Ver transcripción

Solo la transcripción

Production engineering's two hats

The speakers introduce a role split between live support and software projects. Production support is treated as a first-class concern in a complex trading environment.

Mark, Liora, and Joseph introduce themselves as Jane Street production engineers working in New York and London. They describe two sides of the job: support work, where they actively resolve live issues, and project work, where they build software to improve the support infrastructure.

The engineers say production engineering treats support for applications as a first-class concern. Trading operations are complicated, and unusual problems can arise in production. They spend about a third of their time on active support rotation and the rest on software projects that make that support better.

Working on support

Engineers monitor systems, answer questions, and triage live problems. They describe the satisfaction of quick fixes and the importance of communicating under uncertainty.

During a support rotation, an engineer is responsible for a slice of Jane Street's infrastructure throughout the trading day. When an application has an issue or a user has a question, the engineer is a first responder who triages and works to fix it. Small fixes can produce quick wins, and internal users can immediately see the benefit.

The role teaches people to communicate quickly and accurately under uncertainty: they talk to developers about systems and to traders about business needs. Solving a live issue can feel like working on a puzzle without all the pieces. Engineers monitor system health, answer questions at their desks, and ask teammates for context when needed.

Projects, mentorship, and tooling

Outside the rotation, engineers work with application developers and build shared support tools. The speakers describe mentorship, direct feedback, and the opportunity to solve problems they have experienced.

Outside the rotation, production engineers write software to improve support. That generally means either working directly with application developers on the systems they support or building general-purpose support tooling. The team calls its multi-month projects with application developers deployments.

These deployments aim to reduce support work, provide software engineering mentorship, and spread practices that make systems easier to understand and learn. One engineer describes a first mentor who helped with adapting to Jane Street, learning OCaml, and understanding the system they built together.

Project work also offers room for initiative. The engineers describe solving problems they have experienced themselves and receiving direct feedback because their users work inside the firm. Their shared tools include alerting libraries, toil tracking and visualization, and incident management systems used across teams.