Technical Operations Manager
Technical Operations Manager at Customer.io, responsible for managing technical operations and ensuring the smooth functioning of the platform, utilizing skills in Python, AWS, Cloud Computing, DevOps, Automation, and Machine Learning.
About Customer.io
Over 8,000 companies — from scrappy startups to global brands — use our platform to send billions of emails, push notifications, in-app messages, and SMS every day. Customer.io powers automated communication that people actually want to receive. We help teams send smarter, more relevant messages using real-time behavioral data.
About the role
Hi, my name is Bill Miksich, VP of Operations at Customer.io , and I'm looking for a Technical Operations Manager to join our Strat Ops team.
You'll work alongside our existing Tech Ops Manager, to build, maintain, and scale the internal systems that keep the company running. The work is primarily about building AI-assisted internal tooling — partnering with our Automation/AI leads on agent infrastructure and evals, and building integrations across our stack (Linear, Ramp, Notion, Slack, Google Workspace, 1Password, Kandji, GCP). You'll work across teams — especially BizOps and People — identifying where toil can be automated, building solutions quickly, and leaving behind documentation that lets others self-serve.
This isn't a role where someone hands you a ticket queue. We operate like a startup — broad scope, fast iteration, high ownership. The right person doesn't need much direction to get moving; they talk to a stakeholder, understand the real problem, and start shipping.
What we value
Builder mentality: You find genuine satisfaction in shipping internal tools that people actually use. You're biased toward building a small working version quickly over planning the perfect system for months.
Ownership and autonomy: You identify what needs to be done, build it, and maintain it — without waiting to be told. When a team is blocked, you step in.
Range without ego: You can hold a credible technical conversation with our CTO and turn around and explain the same system clearly to a finance manager. You adapt your communication to the room.
Cross-functional curiosity: You actively look for where operational friction exists across the business. You don't wait for teams to come to you with a fully formed problem statement — you surface friction before it escalates.
Pragmatic documentation: You write runbooks, wikis, and guides that people actually follow — not as an afterthought, but as part of how you build.
What you'll do
Posted June 6, 2026