An Inside Look at Jane Street’s Tech Internship with Jeanne Van Briesen, Matt Else, and Grace Zhang

Program Structure and Recruitment Trends

• Jane Street's internship program is structured to allow interns to work on projects across two distinct teams, providing broader exposure to the firm's infrastructure.
• The program begins with an OCaml boot camp, ensuring no prior functional programming knowledge is required and fostering a shared community among all interns.
• Recruitment sources have shifted significantly over the last decade; unlike 12 years ago when functional programming hype was the primary draw, the majority of current interns arrive without prior OCaml experience.
• The firm actively discourages candidates from using OCaml in interviews, as it is often ineffective for demonstrating general engineering aptitude compared to other languages.
• Outreach efforts like "Insight" target specific demographics, including women in STEM, non-core universities, and underrepresented minorities, to diversify the applicant pool beyond traditional feeder schools.

Internship Projects and Technical Impact

• Grace Yang worked on a manual order entry system, enabling traders to dynamically increase system-level risk limits during busy trading days, a feature previously restricted to slower code-review cycles.
• Matt Els developed a project for the RFQ (Request for Quote) Dev team, applying automated risk checks to manual trade requests to ensure consistency with fully automated systems.
• Jean Van Briesen redesigned the API for "InkerDOM," Jane Street's dynamic web app library, combining a simple and an advanced interface into a single, more usable model while writing a PPX (syntax extension) to simplify usage.
• Matt is currently leading the development of "Zeroprop," a new protocol specification system inspired by Protocol Buffers, designed to handle versioning and compatibility between different applications efficiently.
• A significant portion of intern projects land in production, with interns often seeing their work utilized by mentors or the firm shortly after their transition to full-time roles.

Onboarding, Tools, and Cultural Dynamics

• The internal tooling ecosystem is extensive and idiosyncratic, requiring a steep learning curve that is mitigated through formal classes on code review tools and libraries.
• The code review process is described as a high-investment interaction where senior engineers often act as co-authors, deeply understanding and rewriting code to provide detailed educational feedback.
• Despite the high bar, interns are trusted with core, critical systems (such as risk management) because the rigorous review process ensures safety even with limited domain context.
• The transition from intern to full-time involves a period of re-acclimatization, where familiar tools and codebases often require re-learning due to changes made during the intervening year.
• Team assignment for full-time roles is collaborative; mentors and recruiters often suggest teams based on observed preferences, though candidates can interview with multiple teams to make a final decision.

Challenges and Future Considerations

• A recurring challenge for new hires is "imposter syndrome," driven by the presence of highly competent colleagues and a steep learning curve regarding domain-specific finance concepts.
• Internal management struggles with the balance of providing timely, constructive feedback; the friendly culture sometimes leads to a lack of explicit progress updates for interns and new hires.
• Interns and full-timers differ in their preference for scheduling; while interns enjoy scattered social and educational breaks, full-timers often crave larger, uninterrupted blocks of time for deep coding work.
• Remote work has altered interaction dynamics, making spontaneous office conversations harder to replicate, though scheduled social meetups and opt-in sessions attempt to mitigate isolation.
• Prioritization for developers involves balancing immediate user feature requests, technical debt reduction, and long-term architectural initiatives, often requiring negotiation with trader teams to understand evolving business needs.