Senior Software Engineer – Backend

pRIVR, part of Amazon is a robotics company pioneering Physical AI through real-world doorstep delivery. Founded in 2024 as an ETH Zurich spin-off, RIVR developed wheeled-legged robots designed to operate in complex, unstructured environments such as stairs, gates, doors, and uneven urban terrain. We believe that achieving general physical intelligence requires solving real customer problems in the real world, where robots can learn from rich operational data at scale. /ppFollowing our acquisition by Amazon in March 2026, we are continuing this mission with greater reach and speed. By combining custom robot hardware, onboard autonomy, and cloud-based coordination, RIVR, part of Amazon is building the next generation of safe, reliable autonomous robots for last-mile delivery /ph3Job Description /h3pAs our next Senior Backend Engineer you will focus on the design, development, and operation of the server-side systems that power our cutting-edge robotics delivery platform. This role involves building robust, scalable microservices and integrations crucial for fleet operations, process integrations, and data processing in a cloud-native environment. You will play a key part in translating complex business requirements into reliable and efficient backend solutions. /ph3What you’ll be doing /h3ullibDesign and implement backend services /b for integrating RIVR's platform with our customers’ systems, to provide delightful delivery experiences. /lilibDevelop and enhance the backend infrastructure /b for our robot operations platform. /lilibDevelop backend components /b to aggregate Key Performance Indicators (KPIs), providing insights into platform performance and business value. /lilibContribute to the overall architecture /b, reliability, and scalability of our backend systems within a containerized microservices context. /lilibCollaborate closely /b with frontend, robotics, and infrastructure engineers to deliver end-to-end features /li /ulh3What you must have /h3ullipApproximately b5 years of professional experience /b designing, building, deploying, and operating backend systems in a Service-Oriented Architecture (SOA) context. You have production experience with: /p /lilipStrong experience with Typescript, Java, C++ and/or Python /p /lilipService decomposition. /p /lilipAPI design. /p /lilipDifferent interaction patterns (e.g. RPC, publish/subscribe, event-driven). /p /lilipAt least two database technologies /p /lilipTrading off consistency for availability/performance. /p /lilipProven experience (5+ major services) with at least bone major cloud provider /b (AWS strongly preferred). /p /lilipDemonstrable experience in bat least one /b of the following areas: /p /lilipIntegrating with complex bthird-party APIs /b and building reliable, bdistributed workflows /b (e.g., using task queues, state machines). /p /lilipBuilding bevent-driven applications /b and/or scalable bdata processing pipelines /b (e.g., using Kafka, message queues, serverless functions). /p /lilipA bbusiness-oriented mindset /b, with a focus on leveraging technology to solve concrete problems and deliver value. /p /lilipA strong sense of bownership /b, comfortable venturing beyond immediate expertise to understand and solve problems effectively. /p /lilipThe ability to bearn trust /b by providing and receiving candid, constructive feedback. /p /lilipWillingness to participate in bon-call rotations /b to ensure the reliability of our production systems. /p /lilipbExcellent communication skills /b, with the ability to articulate complex technical ideas clearly and drive mutual understanding across teams with diverse technical backgrounds. /p /li /ulh3Get some bonus points /h3ullipFamiliarity configuring and operating bCI/CD pipelines /b. /p /lilipBackground in robotics, IoT, fleet management, or real-time data streaming systems. /p /lilipStrong familiarity with observability such as bOTLP, Grafana, prometheus /b, etc preferably in the context of devices with intermittent connectivity /p /li /ulpWe believe the best work is done when collaborating and therefore require in-person presence in our office locations. /p