🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
The Research Engineering team develops and deploys the pipelines connecting a research idea all the way to its rollout in production. We exist to ensure that the entire pipeline describing our research is efficient, effective, and scalable. People in our team are avid collaborators and work in tight feedback loops with our researchers. We talk through problems on desk, prepare solutions same day, and work out how to deploy safely for tomorrow. The scope of the team covers anything that accelerates the path from research to production at massive scale. This could be designing our external data ingestion pipelines, writing our feature discovery and storage systems, building our model validators and experiment trackers, authoring and deploying a bespoke algorithm, or figuring out how to roll out something novel. We use a broad toolkit including Python, C++ and internal domain-specific languages, and are happy to pick up new tools and languages as required. About you You write production code in both Python and C++. You reach for the second one when it matters, and you know when it does. You're naturally curious about how other teams' systems work, not just your own, and you often end up being the person who spots where things won't fit together before it becomes a problem. You enjoy working on many projects at once, seeing connections and opportunities between them which others miss. You’re motivated to solve issues with whatever tool is best, rather than a preference towards deep specialisation in one area. You like working with research stakeholders across the business and you're good at figuring out what someone actually needs, not just what they asked for. You've done this commercially. You've owned something in production that other people relied on. Not necessarily big, but something you had to maintain, debug and live with long after you shipped it What you don’t need A finance background. Every language we touch. We hire engineers who like to solve the problems our traders face - we'll teach you the context on the ground. About Us IMC is a global trading firm powered by a cutting-edge research environment and a world-class technology backbone. Since 1989, we’ve been a stabilizing force in financial markets, providing essential liquidity upon which market participants depend. Across our offices in the US, Europe, Asia Pacific, and India, our talented quant researchers, engineers, traders, and business operations professionals are united by our uniquely collaborative, high-performance culture, and our commitment to giving back. From entering dynamic new markets to embracing disruptive technologies, and from developing an innovative research environment to diversifying our trading strategies, we dare to continuously innovate and collaborate to succeed.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.