> Markdown version of [/jobs/ext/2571452-software-engineer-backend-focused](https://www.wearedevelopers.com/jobs/ext/2571452-software-engineer-backend-focused). 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). --- # Software Engineer (Backend-Focused) - **Company:** AZX INCORPORATED - **Location:** Seattle, WA, United States (Remote available) - **Experience:** Expert - **Salary:** $140,000.0 - $225,000.0 - **Contract:** Permanent contract - **Skills:** C++ (Programming Language), Databases, Continuous Integration, DevOps, Distributed Systems, Python (Programming Language), Key Management, Machine Learning, Routing, Svelte, Tensorflow, Web Application Frameworks, WebSocket, Pulumi, Pytorch, Autoscaling, Large Language Models, Prompt Engineering, Generative AI, Backend, Rate Limiting, Fastapi, Vue.js, AngularJS, Kubernetes, ONNX (Open Neural Network Exchange) Format, Xgboost, Bicep, Graphql, Machine Learning Operations, Api Design, Terraform, Docker - **Published:** August 24, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=8c8fa738da4c8f7f ## About the Role * 4+ years of experience in backend engineering fundamentals: distributed systems, API design, and production experience in Go, Rust, or async Python. * Familiarity with LLM-specific backend concerns (rate limiting, caching, token accounting) is a plus, though not required on day one. * Exposure to Kubernetes and containerization; interest in sandboxing or security is a plus. * Comfort working across a range of platform concerns rather than one narrow specialty - this role is intentionally broader than our specialist infra profiles. * Eagerness to grow into deeper specialization in gateway, sandbox, or inference infrastructure over time. Bonus Qualifications: * Experience in both startup and enterprise environments * Past work in energy, real estate, utilities, climate or related fields * Bonus if you have experience and passion in one or more of * Additional web frameworks (e.g. Svelte, Vue, Angular) * Lower-level languages e.g. C++, Rust * Networking paradigms e.g. GraphQL, Websockets * ML capabilities e.g. Sk-learn, xgboost, Pytorch/Tensorflow/JAX, Onnx… * Additional database types such as graph or vector databases * DevOps e.g. CI/CD pipelines, Docker, Kubernetes, Terraform, Pulumi and/or Bicep * Generative AI e.g. prompt engineering, RAG, fine-tuning, tooling ecosystem ## Description We're looking for a Staff or Senior ML Engineer to own the technical backbone of how AZX serves and evaluates models at scale. This is a high-leverage IC role spanning our inference platform - GPU scheduling, autoscaling, and serving infrastructure for vLLM/SGLang across cloud and customer-managed clusters - and the evaluation systems that tell us whether model, prompt, and agent changes that make things better. You'll create technical direction for how AZX serves models reliably. This role suits someone who wants architectural ownership over hard ML infrastructure problems, paired with the judgment to build the guardrails that let the rest of the team move fast safely. Responsibilities: * Build and maintain backend services for our LLM gateway - routing, rate limiting, key management, and observability in front of the inference fleet. * Contribute to sandboxing and isolation infrastructure that keeps agent-generated code safe to execute, working alongside our security-focused engineers. * Support Kubernetes-based platform services, including operators and autoscaling logic adjacent to our inference platform. * Write high-performance backend code in Go, Rust, or async Python (FastAPI/Starlette), working with infrastructure like Envoy and gRPC. * Instrument services with OpenTelemetry so behavior, latency, and cost stay observable as the platform scales. * Collaborate across the gateway, sandbox, and inference platform teams, flexing across areas as priorities shift. ## Related Videos - [Back(end) to the Future: Embracing the continuous Evolution of Infrastructure and Code](https://www.wearedevelopers.com/videos/440-back-end-to-the-future-embracing-the-continuous-evolution-of-infrastructure-and-code) - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Why segmenting your infrastructure into tiers makes your infrastructure design better](https://www.wearedevelopers.com/videos/1960-why-segmenting-your-infrastructure-into-tiers-makes-your-infrastructure-design-better) - [Lessons learned from building a thriving Vue.js SaaS application](https://www.wearedevelopers.com/videos/1666-lessons-learned-from-building-a-thriving-vue-js-saas-application) - [Inside Bitpanda's Tech Stack: Scaling a European Fintech Leader - Markus Dorner](https://www.wearedevelopers.com/videos/1979-inside-bitpanda-s-tech-stack-scaling-a-european-fintech-leader-markus-dorner) - [Unleashing Potential Across Teams: The Power of Infrastructure as Code](https://www.wearedevelopers.com/videos/930-unleashing-potential-across-teams-the-power-of-infrastructure-as-code) ## Related Articles - [What’s the Difference Between Frontend and Backend Development?](https://www.wearedevelopers.com/magazine/240-what-s-the-difference-between-frontend-and-backend-development) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)