> Markdown version of [/jobs/ext/4009826-senior-backend-engineer](https://www.wearedevelopers.com/jobs/ext/4009826-senior-backend-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Backend Engineer - **Company:** Monte Carlo - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Customer Data Management, Data Stores, Software Debugging, Distributed Systems, Design of User Interfaces, Human-Computer Interaction, Python (Programming Language), Microsoft Software, ReactJS, Large Language Models, Backend, Agentic-AI, Build Management, Pyspark, Front End Software Development, Data Pipelines, Crud - **Published:** October 29, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-backend-engineer--4a2f8022-7ffb-430c-8cb1-a1eb0fca72f5 ## About the Role Use Cases, Identify Issues, Artificial Intelligence (AI), Production Systems, Distributed Computing, User Interface/Experience (UI/UX), Test Design, Product Testing, Customer/Client Research, Microsoft FAST, * Backend depth. 5+ years shipping production backend services in Python or Java, with real experience designing, running, and debugging APIs and services under load. ## Description Monte Carlo is the agent trust platform that unifies data and agent observability to monitor, troubleshoot, and improve production AI systems. As enterprises prepare to deploy thousands of agents across business-critical use cases, Monte Carlo provides the reliability infrastructure to support them along this AI transformation, from human-guided agents to fully autonomous operations. Founded in 2019 and backed by leading investors, Monte Carlo empowers data and AI teams to ship trusted AI at scale. Learn more at montecarlo.ai, We're hiring a Senior Backend Engineer to design and build the core of our agent trust platform: the architecture, distributed systems, and backend services that let enterprises trust AI in production. You'll get a problem statement, not a spec, and own it from system design to a tested, deployed product. React experience is a plus for the times a feature needs a front end. What You'll Do * Own the architecture and system design for core platform services: make the calls, write down the tradeoffs, and evolve the design as scale grows. * Build and run production-grade backend services and APIs in Python or Java that power Monte Carlo's core platform and agentic systems. * Design and scale distributed systems that stay reliable, observable, and fast as customer data and agent volume grow. * Take vague problem statements to production: prototype, architect, build, test, deploy, and own it after launch. Start simple and evolve it without over-building up front. * Build and maintain data pipelines behind analytics, ML, and customer-facing features. * Work with product, ML, and infrastructure partners to ship customer value, and pick up React work when a feature needs it., * Architecture and system design. You've designed systems from a blank page, weighed the options, and can defend the tradeoffs: consistency, availability, latency, and cost. * Distributed systems. You've built and scaled distributed architectures yourself and run them in production: services, queues, event-driven flows, data stores, and what happens when they fail. * 0-to-1 ownership. You've taken ambiguous problems to a deployed product, owned testing and deploy, and kept owning it after launch. You move with urgency and treat outcomes as yours. * Nice to have. React for the times a feature needs a front end. Agentic or LLM-powered systems in production are a strong plus, as are data pipelines on AWS and PySpark. This Is Not For You If * You want a detailed spec before you start building. * Your backend experience is mostly CRUD apps on a single service, or you've only built inside architectures someone else designed. * You'd rather hand off testing, deployment, and on-call than own them. * You're mainly a frontend engineer looking to grow into backend.