capsa - Engineering Manager

• You'll work alongside a small, senior and high performing engineering team • Meaningful equity in a company that grew ARR 15x last year • What you'll achieve in the first six months • Formed an evidence-based view of the codebase, delivery process and engineering capability across all three squads, and agreed the most important improvements with the CTO and Product. • Made your first hiring and team-shape decisions, grounded in the capabilities and capacity each squad needs. • Established regular coaching and clear expectations for your engineers, with a grounded view of who’s thriving, who needs support and where the gaps are. • Established clear technical ownership within each squad, with engineers taking responsibility for decisions and technical leads working effectively with Product. • Helped the squads deliver meaningful improvements end to end, and assessed their impact on customers or the teams that depend on them. • Put an agreed, lightweight planning and delivery rhythm into practice across the squads, making commitments, dependencies and risks visible without centralising every decision. • Recent projects from the team • Agent Harness: our own agent harness built on a custom, streaming-first graph execution framework • Code Execution Framework: interruptible and resumable mid-execution, for programmatic tool calling • Document Ingestion, Indexing, and Search: a VLM-based OCR pipeline, a self-hosted search cluster, domain-aware search strategies • Citations: an end-to-end approach to reviewing supporting documentation behind AI-generated statements • Document Authoring: agent tooling and a document editor supporting collaborative authoring across Word, Excel, PowerPoint, and email • Managed engineers directly for a few years; before that, a strong individual contributor at a venture-backed startup or a serious tech company • You’ve coordinated work across teams or substantial parallel workstreams, resolving dependencies and competing demands while keeping ownership with the engineers doing the work. • Hired people, developed them, and made calls about team shape as things scaled or didn't go to plan • Shipped distributed systems, data pipelines, or platform services to production through a team you led • Comfortable operating at pace, with incomplete information • How you operate • Takes responsibility for what your team ships and its effect on customers, not just internal velocity metrics • Thinks carefully about the problems being solved and the decisions the team makes; uses AI to sharpen that thinking, not replace it • Accepts that time is short and information is incomplete, makes progress anyway, and adjusts as more is known • If this opportunity excites you • We'd like to meet you. Initial conversations are direct and substantive, going deep on the work, the team, and what you'd own in the first six months.