July 22, 2026
Share on
Citadel’s NXT is a specialized two-year initiative that accelerates the growth of early-career engineers. By combining hands-on business projects, structured mentorship and unprecedented access to senior leadership, NXT transforms exceptional talent into the driving force behind our technological innovation.
Today, Citadel NXT members and alumni make up roughly a quarter of our engineering workforce.
At Citadel’s NXT offsite, engineers from across the firm gathered to answer a practical question: How do you grow quickly in an environment where expectations are high and impact is immediate?
Moderated by Suzanne Daly, COO of Fixed Income and Macro Engineering, the panel brought together engineers working on distributed risk systems, enterprise data platforms, equities datasets and post-trade infrastructure. While their areas of expertise differed, their experiences pointed to a consistent pattern: Career growth is driven by how quickly our engineers learn to connect technical work to real outcomes, not by the time spent in a role.
That’s because our engineers build systems that directly influence trading, risk and capital allocation, often in real time.
“Growth at Citadel comes down to impact,” Daly said. “The people who accelerate fastest take ownership, stay curious and don’t wait to be told what to do.”
The culture at Citadel plays a critical role in shaping this dynamic. Engineers are not expected to have all the answers up front, but they are expected to learn quickly and are surrounded by people who help them do that.
The fastest way to grow is to work on high-stakes problems with immediate, material outcomes.
Mubai from Enterprise Data Engineering found this out firsthand by stepping into a system that sat directly in the pricing workflow for options. The system touched traders, operations and multiple downstream consumers, each relying on accurate outputs to do their jobs well.
“It was a critical project to replace a brittle pricing process. If one run was wrong, it could affect downstream pricing across the system,” she said. “I took ownership of the project, and it built strong relationships across trading, ops and risk teams.”
Working closely with stakeholders and receiving context directly from people using the system made Mubai’s learning curve more manageable and the work less intimidating.
A background in finance isn’t necessary to succeed at Citadel. What matters is a willingness to learn and how you use the people around you.
Andy from Central Risk Services described building infrastructure to distribute risk and P&L calculations. When outputs did not align, the issue was not in the infrastructure alone.
“The numbers didn’t make sense. They were off by orders of magnitude,” he said. To fix it, he had to learn financial concepts he had never worked with before.
“I had to dig into how FX pricing works and how positions are stored. There wasn’t someone who could just tell me the answer,” he explained.
That process involved collaborating with domain experts and iterating through questions until the system made sense.
Hrvoje from Post-Trade Engineering described a similar approach.
“What made me successful early was working shoulder to shoulder with business partners… asking a lot of questions,” he said.
He added that understanding takes time.
“I don’t usually get it right the first time, but if I ask it differently, I figure it out,” he said.
Financial context is learned on the job, through systems and people who are invested in helping you understand.
Because engineers work closely with stakeholders, learning and building happen simultaneously.
Wistan from Equities Engineering built a talent intelligence platform by embedding directly with a subject matter expert.
“I asked to sit next to him and iterate throughout the day,” he said. “You see what frustrates them, what matters, and you can adjust quickly.”
This collaborative environment reduces the gap between technical implementation and real-world use. It also helps engineers learn the domain quickly.
At Citadel, colleagues are partners in building systems, not gatekeepers of knowledge.
Although you are not expected to be an expert on day one, you are expected to think critically and contribute.
Andy described sharing his perspective on cloud infrastructure early in his career.
“I had a strong view on how we should organize our clusters, and I shared it,” he said. “After that, I was asked for input more often.”
Here, learning and contributing happen in parallel. Engineers build context while actively participating instead of waiting until they know everything.
At Citadel, systems are built in close collaboration with the people who use them. Feedback is constant, and learning is continuous.
Francis from Fixed Income and Macro Engineering described the iterative process involved with working with traders and partners to validate outputs.
“I ask a lot of questions, even basic ones, until everything makes sense,” he said. “You release something, check if the numbers match expectations and keep going until it’s right.”
This is how engineers build technical confidence and domain understanding at the same time.
Across the panel, one point became clear: You are not expected to arrive with deep financial knowledge. You are expected to build it quickly, with support, by:
As Hrvoje put it, “This knowledge compounds. It builds leverage over time.”
That’s what makes the environment different. Learning is not separate from the job. It is built into it.
Engineers at Citadel are close to the systems that matter. They see how those systems perform in real time. They are supported by colleagues who help them understand and improve them, creating a feedback loop where learning and impact reinforce each other.
Engineers are not building in isolation. They are shaping how the firm operates and competes.
For early-career engineers, that is the opportunity. You don’t need to know everything coming in. You just need to be curious, collaborative and willing to learn fast in an environment designed to help you do exactly that.
