> Markdown version of [/jobs/ext/4613530-senior-software-engineer-infrastructure](https://www.wearedevelopers.com/jobs/ext/4613530-senior-software-engineer-infrastructure). 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 Software Engineer - Infrastructure - **Company:** PROBOOK LLC - **Location:** Manhattan, KS, United States - **Experience:** Expert - **Salary:** $200,000 - $300,000 - **Contract:** Permanent contract - **Skills:** Cloud Computing, Continuous Integration, Software Debugging, Distributed Systems, Software Engineering, Software Coding - **Published:** November 7, 2026 - **Apply:** https://www.juju.com/job/28_25196_9ea2842b2b71bc7ed38481b706b326ef ## About the Role * 3-6 years of engineering experience with meaningful ownership of infrastructure you built rather than inherited. * Zero-to-one experience. You've built infrastructure from scratch at a startup, or stood up new systems on a team inside a larger company. * Strong infrastructure fundamentals across distributed systems, cloud infrastructure, networking, CI/CD, and observability. * Real software engineering. Infrastructure at Probook means writing code and owning complex systems end to end, from design through production. * Breadth over depth. You'd rather build new systems than operate mature ones, and you move up the stack when that's where the problem is. * Judgment. You know when a system deserves careful architecture and when it deserves to be finished this week. ## Description * Product infrastructure. Build and operate the infrastructure behind our real-time decision systems - durable execution, workflow orchestration, reliability, and performance for products customers run their business on. * Agent infrastructure. Build the sandboxes, evaluation infrastructure, and harnesses our engineers use to develop and ship agent workflows, including the compute environments agents execute in. * The developer platform. CI/CD, deployment, local development, and internal tooling - the abstractions that let the team ship in days rather than quarters. * Reliability and observability. Instrumentation, monitoring, incident response, and debugging tooling for systems whose failure modes are often probabilistic rather than deterministic. * Cost and scale. Cloud and inference costs as the product footprint grows, and capacity and architecture decisions made before they become bottlenecks. * Partner across engineering. Work directly with the product engineers building on your infrastructure, and with the customers affected by it.