“stum” – Ops Developer
A Typical Day as a Programmer for Ops
I go by my Unix name “stum” since I’m HRT’s third Tim.
Today, I arrive and check in with my teammates in London. I get a quick briefing on the progress people made on projects while I was asleep, as developers on my team are spread across our NYC, London, and Singapore offices. As always, there are code reviews waiting in my inbox; I prioritize these so that my colleagues aren’t blocked getting their code pushed live, something my team does daily.
The market opens and everyone in Ops is on alert, ready to jump in with some quick thinking and faster typing at the first sign of an issue. We’re lucky today: the markets open with no issues. I put on my headphones and turn my attention to long-term projects. Recently, I’ve been working on improving the responsiveness of one of our desktop GUIs that will benefit from some increased concurrency. I try a few different ideas — non-blocking I/O, threads, “doing less work at once.” Using PyQt5, I can easily test out multiple ideas without a lengthy recompile cycle. I’m optimistic it’ll work, but I’ll have to wait until tomorrow’s open to test it live.
Soon enough, it’s time for the handoff to Singapore, and just like with London, we discuss today’s progress, and I hand off a developing production issue that’s going to require a look, and I’m promised a review in my inbox “just as soon as I get my coffee.”
For more information, check out the “Trade Operations” opportunities on our careers page.
Join Our Team
We’re always on the lookout for the best and brightest.
Think you might be an awesome candidate?