Senior SW Engineer - Infrastructure

The Role

Our products increasingly rely on data-intensive APIs. Beyond our reporting platform, MCP server, and public endpoints, these APIs now power per-customer environments where AI systems can execute tasks, access customer-specific state, and proactively run analysis. Today, that means Azure VMs running Dockerized workloads and a growing layer of application code which needs to cover everything from functionality to routine updates.

We’re looking for a senior software engineer who loves working at the boundary between product code and infrastructure. This is not a traditional DevOps or SRE role. You’ll spend most of your time writing application code that controls infrastructure primitives: messaging queue abstractions, VM management, data lifecycle, container updates, no-downtime migrations, bootstrapping, permissions, observability, and security.

The right person is comfortable going deep into Linux, containers, networking, and all that jazz, but thinks like a product engineer: shipping reliable systems, choosing pragmatic abstractions, and making complicated runtime behavior feel routine to our customers.

| Our tech stack: Node.js, TypeScript, React, MongoDB, ElasticSearch, Azure, and Pulumi.

What you'd be doing

• Build and evolve the systems that provision, update, secure, and observe Motion’s agent environments.
• Design abstractions around queues, locks, background tasks, and service bus mechanics so product engineers can build on reliable primitives.
• Evolve our infrastructure-as-code footprint in Pulumi - defining patterns other engineers can build on.
• Work with Linux systems, mounted persistent storage, OS disks, container boundaries, permissions, logs, and runtime debugging.
• Participate in a small, high-ownership, cross-functional team with weekly cycles.

Our ideal fit brings

• 6+ years of experience as a software engineer, with meaningful time spent going deep into infrastructure.
• Strong production backend experience. TypeScript / Node.js is ideal, but we care more about strong engineering judgment and the ability to learn our stack quickly
• Deep, hands-on cloud experience. Azure is where we live, but AWS or GCP experience transfers if you are strong on the fundamentals.
• Fluency with infrastructure-as-code. We use Pulumi but any relevant experience in Terraform or CDK is good.
• Hands-on experience with containers and runtime environments. Docker is important; experience with Kubernetes, Nomad, ECS, Docker Swarm, or similar orchestration systems is helpful but not required.
• Experience designing reliable systems around background jobs, queues, locks, service buses, migrations, retries, and failure recovery.
• Strong security instincts for application runtime environments.

...and you'll be a strong fit if you align with these qualities:

• You're genuinely excited about infrastructure. When something breaks, you want to understand how the system actually works, not just scale and restart it.
• A strong sense of ownership: you make decisions and move quickly to fix things quickly when they go wrong.
• A pragmatic mindset. You can ship the simple thing when speed matters, while flagging that which needs to evolve later.
• Comfortable in a fast-moving startup where requirements come with ambiguity and the “right” way isn't handed to you.
• You enjoy being a strong individual contributor and a supportive teammate. Engineering is a team sport here