🎁 Zanim zaaplikujesz, przećwicz tę rozmowę. Załóż darmowe konto WorkMundi i odbierz Trening rozmowy kwalifikacyjnej w HelpsYouSpeak — bez opłat, bez karty. Chcę swój trening →
Project Description: Your Role Are you a software engineer who is up for a challenge? Because we’ve got a great one. We’re building a new analytics and risk platform. It’s called ACQA. It’s a cloud native platform with a host of business specific applications and services built on top of it. At its heart its Python, but we also use other languages, including Java and Scala. We’re not looking for somebody who fits in a box. Our team is diverse, and our hiring reflects that. You might be a Python expert with an unparalleled depth of knowledge about financial derivatives risk and pricing. Or you might be a big data guru who writes beautiful Scala (or PySpark) on massive and complex datasets. Or you may be somewhere in-between. Either way you are the kind of person we want to speak to. So, if you are an awesome Python developer, if you know about derivative risk; if you’re a Java or Scala developer who’d like an opportunity to learn some Python then we would love to hear from you. Your team You’ll be working in the ACQA Engines Crew, as part of the IB Risk Technology Stream under CDIO. ACQA is “Advanced Cloud Quantitative Analytics” – it’s our strategic cloud based Analytics and Risk platform. The team is composed of approximately 60 top level engineers in multiple global locations, organised into agile local autonomous pods of 5-10 members. We work directly with traders, risk managers and finance users to provide platforms and tools that for management of the investment bank's Risk and PnL. Responsibilities: Your expertise You have: A deep software engineering background and mindset. You’ve seen several different programming paradigms and languages. You understand design patterns – and know when not to use them. You know what it means to develop bullet proof software in a fast-paced environment where bugs cost money. Strong communication skills, written and spoken, you can communicate complex subjects concisely. You’ll have a few of: Deep experience developing in Python. You’ve used it at scale, you have a deep knowledge of the language and many of its commonly used packages. You believe in testing your code to destruction, using several different testing frameworks. You’re a Pythonista who loves the language and embraces its culture. Experience in one of the JVM languages. You’ve used it at scale and have excellent knowledge of the language and its associated ecosystem. Strong knowledge of Spark or other data focused work on massive, complex datasets. You’ve built, tested and tuned spark jobs that operate on giant data sets. A great working knowledge of financial interest rates derivative products, their risks, and how the front to back process works. Some exposure to AI-assisted software development using tools such as GitHub Copilot to improve delivery speed while maintaining quality, review discipline and ownership. Spec-driven development, data-driven development. Some exposure to cloud-based systems (ideally Microsoft Azure) and a desire to learn more. Some exposure to web-based UI frameworks would be useful, though not essential A desire to learn Python You are: A passionate engineer. Dedicated to building software that end users love. You enjoy working in a fast-paced agile environment. A dev-ops evangelist. Committed to helping to improve the developer experience for everybody working on the ACQA platform and interacting with your code. A teacher. You enjoy helping those around you develop their skills, while you develop your own. Collaborative by nature. You enjoy working in a highly skilled team where the best ideas win. Even if they are not yours. You are equally happy developing something new or building on the work of others. Mandatory Skills Description: Python, Java, Scala, PySpark, Spark, Microsoft Azure, cloud-native platforms, big data, financial derivatives, derivative risk, pricing, Risk and PnL, investment banking technology, quantitative analytics, testing frameworks, design patterns, DevOps, agile software development, CI/CD, developer experience, GitHub Copilot, AI-assisted software development, production-grade software, scalable systems. 🏠 Hybrid work (3 days/week from the office) What do we offer our employees? 💰Copyrights which means higher net salary for Developers 🌐 Fully remote recruitment process 🖋 Stable employment based on an employment contract LuxMed health & dental care 🏦 Life insurance, 🧳 Travel insurance 🏋🏽 MyBenefit program (sports card, well-being program etc.) 📞Employee assistance program for you and your family! (consultations with a psychologist, coaching sessions, assistance in private life) 🚗 Car rental 🎓 LuxTalent platform (webinars, training, courses with certificates) 🌎 Internal Mobility program - possibility of rotation between projects, locations, accounts ...and even more!
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.