Software Engineer - Entry Level 2027

Tell me about a coding project you're proud of. What did you build and what was your role in it?

What they are checking: whether the candidate can talk concretely about real work rather than buzzwords, and what they actually contributed

Tell me about a time you disagreed with a teammate about how to approach a problem. What happened?

What they are checking: how they handle conflict on a team-based development approach without becoming defensive or passive

Describe a time you had to learn something completely new under time pressure.

What they are checking: comfort with the steep learning curve of BTU and trading concepts they may not know yet

What draws you to financial markets or trading, even if you haven't studied it formally?

What they are checking: genuine curiosity versus a generic answer, since the role assumes no finance background but real interest

Tell me about a time you had to debug something you didn't write yourself. How did you approach it?

What they are checking: ability to read and reason about unfamiliar code, a daily reality on an established proprietary codebase

What's a technology or programming language you taught yourself outside of class, and why did you pick it up?

What they are checking: intellectual curiosity and self-driven learning, which the posting explicitly values

If you noticed a bug in production code that a teammate wrote, right before a deadline, what would you do?

What they are checking: judgment under pressure and whether they prioritize correctness and communication over ego or speed

If two engineers on your team wanted to solve the same performance problem in completely different ways, how would you help the team decide?

What they are checking: collaborative decision-making and technical judgment in a team-based, holistic development culture

Walk me through how you would find the second largest element in an unsorted array.

What they are checking: basic algorithmic reasoning and whether they can talk through complexity tradeoffs out loud

Suppose you have a system that needs to process incoming data as fast as possible, with every microsecond mattering. What kinds of things would you think about when writing that code?

What they are checking: awareness of low-latency thinking like memory allocation, cache behavior, and avoiding unnecessary overhead, even without prior trading experience

What's the difference between a process and a thread, and when would you choose one over the other?

What they are checking: core systems knowledge expected of a CS grad going into performance-sensitive software

Explain how a hash map works and what makes a good hash function.

What they are checking: solid grasp of fundamental data structures, since these underpin most performance-critical code

How would you go about testing a piece of software you just wrote before it goes live?

What they are checking: whether they think about correctness and edge cases as part of the development lifecycle, not just writing code that compiles