Coding For Speed and Scale: A Software Developer's First Year at DRW

Can you describe your career path and what led you to pursue a Software Developer role at DRW?  

I pursued a degree in Computer Engineering with a minor in Finance. During my first year at university, I stumbled upon machine learning and free-to-use libraries like TensorFlow. This sparked my interest in the role of technology and machine learning in finance. My first internship at ARM as a GPU build systems engineer marked my entry into the tech field, but it was my internship at Visa that deepened my fascination with how high transaction volumes are managed in payment systems networks. DRW, which merges my interests in tech and quantitative finance offers the ideal environment to launch my career, with endless opportunities to learn, grow, and make a real impact.

Describe your role at DRW. What does a typical day look like for you?  

As a front office software developer at DRW, I work in a fast-paced environment that differs from traditional software roles. Each morning, before the markets open, I verify that all systems are healthy and operational. We have early stand-ups to sync as a team and share updates. The rest of my day is spent collaborating with quants and traders to identify and implement new features for my framework. Throughout the day, I also need to be ready for any system outages, quickly debugging and applying hotfixes to minimize downtime.

What kind of projects are you currently working on, and what technologies are you using? 

Currently, I'm building tools and automation for our traders to streamline their workflow. My main project involves designing and building a framework for PnL attribution and risk decomposition. Python is the primary language used, as it’s well understood by both quants and traders. Handling large volumes of data requires proficiency and expertise in numerical analysis libraries.

What advice would you give someone who is just beginning their journey as a software developer? 

Don't be afraid to take on new challenges and have confidence in yourself. Be vocal about your ideas and actively engage in exchanging them with your team. As a fresh graduate, you may bring valuable new perspectives to the team. Remember that learning is a continuous process; always be open to exploring new technologies, even if they are not immediately applicable to your current work.

List 3 things you wish you had known before becoming a software developer?   

• There is no perfect solution or code for most real-world problems. Sometimes, coming up with the quickest solution brings more value to the team than spending loads of time trying to figure out the perfect solution. Other times though, it’s critical that the code is clean so that it can be maintained for a longer-term period.  

• The majority of learning stems from your own curiosity. There are plenty of articles and blog posts out there that explore various aspects of technology, some of which you may not use in your current work. Read them. They may not be immediately useful, but they could be valuable down the line. 

• Becoming a good software developer is not just about writing the best code. Communication and the ability to gather business requirements from users (like traders) are crucial, especially for a front office software developer. 

How would you describe the culture and working environment in the London office? 

Considering my role as a software developer, I initially expected a stressful work environment. It’s the opposite; my colleagues have been incredibly helpful and fun to work with. The flat hierarchy really shines here, and the opportunity to work closely and directly with senior engineers has significantly accelerated my growth as a software developer. Plus, the various social events and activities organized by the company ensure that employees always having something fun to look forward to.