Software Engineer - Denmark Talent Pool

Software Engineer - Denmark Talent Pool Department: Engineering Team: Backend Location: Aarhus, Denmark Type: Full-Time **Building the Backbone of Global Motion: Backend Engineers (Denmark Talent Pool)** **Location: Aarhus, Denmark** **Disclaimer**: Please apply if you are based in Denmark only. At Uber, we don’t just move people; we move the world. But before a car arrives or a meal is delivered, millions of lines of code have to execute in milliseconds. Our **Aarhus Engineering Hub** is the engine room for some of Uber’s most critical global systems. We are looking to connect with **Backend Software Engineers** who want to build the future of **Infrastructure/Platform** and **Catalog** at a scale few companies on earth ever reach. **Why Join Our Talent Pool?** This isn't a typical "apply and wait" role. By joining our Aarhus Talent Pool, you’re putting yourself on the radar for our two most impactful engineering pillars in Denmark: **1\. Platform & Infrastructure** You’ll build the "foundations of the house." This team ensures that Uber’s global fleet of microservices is reliable, scalable, and lightning-fast. If you enjoy deep-diving into distributed systems, high-availability architecture, and cloud-native tech, this is your playground. **2\. Catalog Platform** Uber’s Catalog is the world’s most complex digital inventory. We manage millions of items across thousands of cities for Uber Eats and beyond. You’ll solve "impossible" problems related to data consistency, searchability, and real-time updates at a massive scale. **What We’re Looking For** We value engineering craft over specific buzzwords, but you’ll feel right at home if you have: - **Distributed Systems Expertise:** You understand how to build systems that don’t break when millions of people use them simultaneously. - **Language Agnosticism:** Our primary languages are **Go** and **Java**, but we care more about your ability to pick the right tool for the job. - **A "Scale" Mindset:** You don't just write code; you think about observability, latency, and how your service behaves at 100x its current load. -