SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 200,000 - 300,000 / annual
Probook is an AI operating system for home services, serving customers with $10M–$100M in annual revenue. The company has built dispatch and front-office solutions that power operations for a $750B industry.
You will own critical infrastructure systems that power real-time decision-making and AI agent workflows. Your responsibilities include:
• Product Infrastructure: Build and operate infrastructure for durable execution, workflow orchestration, reliability, and performance of systems customers depend on daily.
• Agent Infrastructure: Develop sandboxes, evaluation infrastructure, and execution harnesses that enable engineers to develop and ship agent workflows at scale.
• Developer Platform: Own CI/CD, deployment, local development, and internal tooling that allows the team to ship in days rather than quarters.
• Reliability & Observability: Design instrumentation, monitoring, incident response, and debugging tools for systems with probabilistic failure modes.
• Cost & Scale: Manage cloud and inference costs as the product grows; make capacity and architecture decisions proactively.
• Cross-functional Partnership: Work directly with product engineers building on your infrastructure and with customers affected by reliability and performance.
The team includes 2x IMO medalists, 3x ICPC World Finalists, a Columbia professor, former founders, and engineers from Stripe, Palantir, Two Sigma, Citadel Securities, and Meta.
REQUIREMENTS:
- 3–6 years of engineering experience with meaningful ownership of infrastructure you built (not inherited)
- Zero-to-one experience: built infrastructure from scratch at a startup or stood up new systems at a larger company
- Strong fundamentals in distributed systems, cloud infrastructure, networking, CI/CD, and observability
- Real software engineering: writing code and owning complex systems end-to-end from design through production
- Breadth over depth: prefer building new systems to operating mature ones; move up the stack where the problem is
- Sound judgment about when a system deserves careful architecture versus when it should ship this week
