Engineering Manager

Company Overview

BotCity brings governance to the code AI writes. AI turned asking into code, and every business user is now a developer. The Python they generate runs on corporate workstations outside any pipeline, inventory, or approval flow, and nothing in the enterprise stack was built to see it. BotCity Sentinel governs that code where it runs: a script-level inventory of what executes, where, and by whom, contextual policies that allow, alert, or block, and a remediation loop where the author makes the first fix. Security asks whether code is malicious. Governance asks whether it should run, here, by this person. We built Sentinel to own the second question. Today it's Python. Tomorrow it's every line of code AI writes.

BotCity serves 1,000+ teams in 70+ countries, including customers as Bayer and LG. We raised a $12M Series A led by Four Rivers, with participation from Y Combinator, SoftBank, and founders and investors including Lew Cirne (New Relic), Rod Johnson (SpringSource), and Walter Kortschak (Summit Partners and Firestreak Ventures). G2 named BotCity one of the world's top 25 emerging platforms.

We are a remote company with teams across the US, Canada and LATAM. Small team, large customers, a category forming around us. If you want real ownership over a problem that matters, we should talk.

Role Overview

The Engineering Manager will be responsible for leading and growing a high-performing, engaged engineering team that gives BotCity the people foundation to scale reliably. This person will manage the Platform Engineering team, overseeing people processes and making technical decisions. This role is built for someone with a strong technical background and a methodical, curious mindset, who combines strong technical judgement with pragmatic execution and the ability to lead a talented engineering team. This role will report to the CTO.

Responsibilities

• Lead, hire, and develop a high-performing, globally distributed engineering team, including career paths and performance reviews.
• Run a consistent cadence of 1:1s, feedback sessions that develop engineers and surface issues early.
• Design and evolve team structure as the organization scales.
• Partner with Product and peer Engineering leads to translate business priorities into team plans, without owning day-to-day technical architecture.
• Define and drive the "Brilliant Basics" roadmap: reliability, observability, security, CI/CD, and engineering practices that scale across squads.
• Own incident management, on-call rotation, and SLOs to ensure platform reliability for ICP (ideal customer profile) enterprise customers.
• Balance hands-on technical involvement with delegation, stepping into architecture or code-level discussions when needed.