Latest Interviews

Solving Puzzles in Production with Liora Friedberg

Liora Friedberg, Ron Minsky

Jane Street's production engineers serve as the first line of defense for its trading systems, balancing active live support with long-term projects to enhance reliability and manage a broad mental model of interconnected infrastructure. Through a blame-free culture and specialized training involving incident simulations, the team rigorously analyzes high-severity events to drive system improvements while leveraging custom tools like Oculus for precise observability and alert management. Recruiting efforts identify candidates with strong debugging instincts and communication skills who can navigate the unique pressure of minimizing opportunity costs during financial disruptions.

How to Use OCaml's Coercion Operator

camels

This session explores standard OCaml's subtyping and coercion mechanisms, emphasizing how the `:>` operator enables compile-time type checks without runtime overhead or data reallocation. The discussion details value inclusion principles for polymorphic variants, recursive subtyping relations, and the specific constraints imposed by private type abbreviations to enforce invariants. While confirming that list coercions remain free at runtime, the presentation notes upcoming analysis of variant annotations and object types in future sessions.

Unfolding the Mystery of Curved-Crease Sculpture with Origami Theorists from MIT

Martin Demaine, Eric Demaine

MIT researchers Eric and Martin Demaine collaborate as origami theorists to synthesize mathematical geometry with physical sculpture, operating on the principle that fun fuels superior artistic execution. Their bidirectional workflow transforms unsolved mathematical problems into interactive artworks like the "Solve Me" sculpture, which embeds hidden research challenges within complex, visually deceptive paper designs. By creating these impossible geometries, the duo simultaneously generates new mathematical puzzles and drives future research trajectories at the frontier of known solutions.

OCaml's New Proposed "include functor" Syntax | OCaml Unboxed

Goldfirere

Jane Street is developing an "include functor" feature for the OCaml compiler that allows modules to directly include functor results based on their own preceding definitions. This innovation eliminates the need for cumbersome intermediate wrapper modules and manual reordering, streamlining the implementation of repetitive patterns like reverse array iteration. A working compiler version supporting this syntax is currently available for testing, with plans to upstream the feature to the mainstream OCaml distribution.

From the Lab to the Trading Floor: Designing for Expert Users with Erin Murphy

Erin Murphy, Ron Minsky

Erin Murphy discusses her evolution from creating data visualization portals at NASA's Jet Propulsion Laboratory to implementing formal UX processes at Jane Street, where she addresses the unique needs of technical experts requiring high information density and keyboard-driven workflows. By prioritizing functional clarity over consumer aesthetics, Murphy leads initiatives that transition complex legacy tools into web-based interfaces while leveraging informal, ad-hoc user observations to maintain design agility within a rapidly scaling engineering environment. Her approach emphasizes recruiting domain-expert designers who can partner with engineers to solve high-complexity problems, ultimately aiming to bridge the gap between graphical usability and the composability of command-line interfaces.

Programming with OCaml's Local Mode | OCaml Unboxed

Jane Street Doe Camel

A Jane Street team member demonstrates practical limitations of the OCaml "Locals" region-based memory management system while optimizing the `best_of_prime_widgets` function to avoid heap allocation. To resolve type mismatches where local lists must escape their regions, the implementation employs a custom zero-overhead `global` wrapper type alongside a recursive map function annotated with `exclave` constraints. Although the solution successfully maintains local allocation for list structures while treating elements as global, the speaker identifies these manual workarounds as sharp corners requiring future improvements through mode polymorphism.

Regions with OCaml's Local Types | OCaml Unboxed

Jane Street researchers introduce a `regional` variant within the OCaml compiler's `locals` feature that treats function parameters as variables permitted to escape their enclosing region exactly once. This mechanism enforces strict type constraints on return values while enabling critical stack allocation optimizations in recursive tail calls and loop iterations. By defining regions around function and loop bodies, the system prevents $O(N)$ space complexity for local data without compromising the language's type safety guarantees.

Exploring the Hidden Secrets within OCaml’s Local Function Types | OCaml Unboxed

Jane Street's OCaml compiler branch enforces strict region safety by automatically inferring hidden `local` annotations on partial applications of functions with local arguments, preventing closures from escaping their intended stack scope. This mechanism triggers compilation errors when such intermediate closures are passed to standard functions like `List.map`, as they attempt to store local data in global heap structures, though these issues can be resolved by fully applying the function or utilizing explicit type expansions. Consequently, the team is considering syntax modifications to function definitions to make these constraints more explicit and prevent accidental region escapes during currying.

Pitfalls with Tail Calls and Locals in OCaml | OCaml Unboxed

Goldfirere

Jane Street researchers developed a "local mode" for their OCaml compiler to optimize memory allocation on the stack, but discovered that standard tail call optimization causes "local value escapes" errors when recursive closures capture variables from a region that ends immediately before the call. To address this, the team introduced a "regional" sub-mode that permits specific values to escape one region boundary, allowing tail-recursive functions to maintain $O(1)$ stack space without explicit `non-tail` annotations, though passing these values through intermediate functions can strip this status and force $O(n)$ allocations. The developers acknowledge that current workarounds like explicit annotations or variable indirection are cumbersome for practical use, prompting a push for better compiler heuristics to automate safe tail calls in future upstream releases.

Stack Allocation with Locals in OCaml | OCaml Unboxed

I

Jane Street is developing an open-source "local mode" branch for the OCaml compiler that reallocates data onto a specialized local stack to eliminate mark-and-sweep garbage collection pauses. By enforcing strict regional scoping where values cannot escape their lifecycle, this architecture enables constant-time deallocation and prevents the cache invalidation and stop-the-world latency inherent in standard heap allocation. The initiative aims to significantly boost low-latency performance by removing the overhead of garbage collection while maintaining memory safety through a novel mechanism called "exclaves."

OCaml Locals Save Allocations | OCaml Unboxed

goldfirere

Jane Street demonstrates how a specialized OCaml compiler reduces memory allocation by introducing the `local` keyword, which restricts value lifetimes to specific function and loop regions. This approach requires replacing standard library functions like `list.iter` with custom implementations that explicitly label arguments as `local` to prevent value escapes, achieving a 50% reduction in word allocations in benchmark tests. Further refinements with the `exclave` keyword and strict type inference drive allocation overhead to near-zero, thereby minimizing garbage collection latency for the experimental feature planned for future upstream integration.

Inferring Locality in OCaml | OCaml Unboxed

The OCaml compiler utilizes an internal allocation discipline that infers local versus global modes for variables and parameters to enable stack-based memory usage and reduce garbage collection overhead. This system prioritizes local inference for arguments while defaulting return values to global to ensure maximum compatibility, with integers serving as a special case that can safely cross mode boundaries under specific annotations. Although this framework enhances performance, current limitations such as standard library functions lacking locality awareness and the need for explicit type signatures to trigger safety checks continue to shape its practical application.

Understanding OCaml Locals as a Mode (with Sub-Moding) | OCaml Unboxed

I

This presentation introduces local and global modes in OCaml as a type system extension that governs memory lifetime and escape properties rather than value structure. The speaker details how these modes enforce safety by preventing local values from escaping their declaration scope while establishing a sub-mode relationship where global values can safely be treated as local. Additionally, the talk outlines four distinct, incompatible function arrow types that strictly regulate argument and result modes to prevent unintended memory escapes, with future work proposed to automate these annotations.

Annotating OCaml Variables and Returns with local_ | OCaml Unboxed

Jane Street is developing an experimental OCaml feature set that enforces strict region constraints through `local` annotations to optimize memory usage and eliminate escaping values. The system introduces the `exclave` keyword to terminate function regions early, enabling specific allocations in the caller's scope while preventing mutable references from capturing local data. Current implementation faces known pitfalls regarding return position rules and compiler error precision, with further refinements planned to address these sharp edges.

Introducing the OCaml Local Mode | OCaml Unboxed

camels

Jane Street is refining the OCaml compiler's type system to introduce a "local mode" feature that enforces function parameters to remain within their execution scope, thereby preventing value escaping. This mechanism guarantees the isolation of mutations and facilitates safer resource management in callback patterns by ensuring local arguments cannot be stored or returned. While the feature remains experimental within the Jane Street branch, it aims to optimize allocation behavior for latency-sensitive code before potential upstream integration.