In 30 seconds
Ezio, a Linux engineer at Jane Street, describes the mix of operations, projects and software used to maintain and scale the firm’s Linux platform. He also discusses collaboration, starting a Pride community group and the importance of learning before trying to change things.
- 1The Linux platformThe team manages monitoring, performance, scaling, troubleshooting and related infrastructure such as storage.
- 2Theory and troubleshootingEzio values operating-system theory alongside practical terminal skills for diagnosing problems.
- 3Building a Pride communityColleagues and HR supported the formation of a group that holds social events and works on workplace issues.
- 4Questions are welcomeEzio learned that colleagues readily admit what they do not know and ask for explanations.
- 5Listen before changing thingsHe advises newcomers to learn how and why the organization works before forming suggestions.
Takeaways
- Linux engineering combines operations, projects, troubleshooting and software automation.
- Understanding operating-system principles helps engineers form hypotheses and solve unfamiliar problems.
- Stating confidence and discussing mistakes support collaborative decision-making.
- Community groups can connect employees and help address practical needs.
- New hires benefit from asking questions and taking time to listen and learn.
Read the edited text by chapter
Linux engineering at Jane Street
Ezio introduces the team’s operational and project work. He explains how technical knowledge and clear communication help with urgent problems.
I’m Ezio, a Linux engineer in Jane Street’s London office. I joined in 2020.
Linux engineers have different mixes of operational work and projects. My team manages a substantial part of the technology infrastructure: the Linux platform, including monitoring, performance, scaling and troubleshooting, as well as related areas such as storage. We also write and maintain software to automate, scale and troubleshoot that work.
One skill I bring is simplifying complexity and connecting people. In a fast-paced environment we process a lot of information, so distilling what matters and communicating it to the right people helps, especially during urgent troubleshooting.
Knowledge of Linux and operating-system theory has helped me beyond everyday terminal use. Operational work matters, but so does formulating hypotheses and investigating what has gone wrong. Experience at both large technology companies and small startups also helps me understand colleagues’ needs and communicate in terms they use.
Culture and community
Ezio describes humility, accountability and social activities. He recounts starting a Pride group and an improvement to insurance support.
I describe the culture as humble and accountable. People often state their level of confidence so others can contribute their opinions and help reach better decisions. They also discuss and take ownership of mistakes, keeping the focus on solving problems; there is room for fun at work and at social events too.
Learning about community groups gave me the opportunity to start a Pride group, something I cared about. An open culture and personal connections made it easy to find interested colleagues, and HR and other people at Jane Street supported the group early on.
The group has social gatherings such as lunches, dinners and drinks. One colleague also worked with the private health insurer to secure explicit support for trans people in the coverage. Community groups, including Pride, are global and present across the New York, London, Amsterdam, Singapore and Hong Kong offices.
Collaboration and advice for newcomers
Work can involve informal conversations or formal cross-office design discussions. Ezio advises new hires to ask questions, listen and learn.
Collaboration can be informal or formal. Sometimes we walk to a colleague’s desk, talk at lunch or meet over coffee; other work calls for shared design documents and calls across offices and time zones. A consultative, inclusive approach helps bring different opinions into the discussion.
When I joined, I wish I had known how normal it is to ask someone to explain what you do not understand. Coming from other companies, I felt pressure to know everything and be productive immediately, so I often researched alone. In the office I saw how readily people ask questions and admit they need to learn more.
My advice to new hires is to take time to listen, absorb and understand before forming opinions and suggesting changes. Talk to colleagues and learn what the firm does, how it works and why. There is no need to arrive knowing everything or prove productivity from day one.
More from this channel
1:48:29EN
1:36:37EN
1:05:45EN
1:25:00EN
1:16:29EN
27:39EN