MyOperator
Website:
myoperator.com
Job details:
This is not a core engineering role but founder's office operation role which require use of AI to build systems, processes & analytics.
JOB DESCRIPTION
You will operate out of the Founder's Office with a company-wide mandate across every non-product function. Your first month is spent establishing a hard baseline: how many hours a month MyOperator actually burns on manual, repeatable work, function by function, process by process. Everything after that is judged against that number. You will design and personally build agentic workflows using Claude Code, Codex, or equivalent — wiring together the systems we already run (Zoho, Google Workspace, our internal platform, our data stores) through MCP, APIs, and orchestration you write yourself. You own the build, the deployment, the monitoring, and the failure modes. This is a role for someone who has enough business experience to know which manual work is actually expensive, and enough engineering discipline to ship something that does not break silently at 3am.
About MyOperator
MyOperator is a Business AI Operator platform that allows businesses, teams, and AI Agents to work in tandem for customer operations, i.e., handle Sales, Support, Escalation, Feedback, and Refund processes. With over 12,000+ businesses using our platform, we are the largest in the space.
MyOperator is built for people who want to work on ambitious problems at a meaningful scale. We value ownership, speed, critical thinking, and a bias for building things that create real customer and business outcomes. This is a high-expectation, high-learning environment where people are trusted to think independently, challenge ideas openly, move with urgency, and keep raising the bar as we build for long-term impact.
KEY RESPONSIBILITY AREAS
- Establish and maintain the manual-effort baseline. Within the first 30 days, produce a measured inventory of manual-touch hours per month across Support, Finance Operations, and Recruitment — process by process, with volume, time-per-touch, and owner — signed off by each function head. Refresh it quarterly.
- Prioritise automation targets by hours and risk, not by request volume. You choose what gets built based on measured cost and error exposure. Function heads raise candidates; you own the sequencing and can say no.
- Design and personally build agentic workflows end to end. Write the orchestration, prompts, evals, and integration code yourself using Claude Code, Codex, or equivalent — connecting Zoho (Recruit, Desk, CRM, Books), Google Workspace, internal APIs, and data stores via MCP and direct API work.
- Operate what you ship. Every workflow you deploy carries alerting, an idempotency and retry strategy, a documented rollback path, and a named human fallback. You are on the hook when something fails in production, not just when it launches.
- Instrument outcomes and report them. Maintain a live dashboard of hours eliminated, workflows in active use versus abandoned, error rates, and internal AI spend per hour saved. Report to the CEO on a biweekly cadence.
- Build internal AI capability in others. Run enablement for function teams so that low-complexity automation moves to them over time and your queue moves up the complexity curve rather than growing indefinitely.
- Maintain the internal AI systems register. Own documentation of what exists, what it depends on, who the business owner is, and what happens if it is switched off.
REQUIREMENTS — MUST HAVE
- 5+ years of professional experience in a role with direct exposure to how business functions actually operate — operations, business systems, internal tooling, solutions engineering, revenue operations, or a technical founding-team role. You must be able to discuss a support queue, a collections cycle, or a hiring funnel from first-hand experience.
- A production system you personally built and operated, which real users depended on. You must be able to walk through its architecture, describe what broke after launch, and explain what you changed in response.
- Demonstrated hands-on fluency with Claude Code, Codex, Cursor, or an equivalent agentic development environment. You will be asked to show a repo, workflow, or system you built with it and still use. Claimed familiarity without a demonstrable artifact does not qualify.
- Working ability to write and debug code independently — Python, JavaScript/TypeScript, or equivalent — sufficient to build integrations, handle authentication, process data, and manage state without engineering support.
- Practical experience integrating third-party SaaS systems via API (CRM, ticketing, HRMS, accounting, or communication platforms), including handling rate limits, pagination, webhooks, and partial-failure states.
- Evidence of sustained personal investment in frontier AI tooling — for example, a paid frontier-tier AI subscription held over multiple months for your own work, with specific examples of what you built with it.
REQUIREMENTS — GOOD TO HAVE
- Experience building with MCP (Model Context Protocol) servers, function calling, or multi-agent orchestration frameworks.
- Background in a startup where you worked directly with a founder or CXO on internal systems, with scope you defined yourself rather than received.
- Familiarity with the Zoho ecosystem (Recruit, Desk, CRM, Books) or comparable mid-market SaaS stacks.
- Experience designing evals or quality gates for LLM-based systems, rather than relying on manual spot checks.
- Exposure to a CPaaS, telephony, contact-centre, or customer-operations business.
- Comfort with data work — SQL, warehouse queries, or building the measurement layer needed to prove an outcome.
THIS PROFILE IS NOT FOR
- People whose contribution is analysis rather than shipping. If your strongest work samples are opportunity assessments, automation roadmaps, or transformation decks, this is the wrong role. The deliverable here is a running system.
- Traditional RPA or iPaaS specialists whose experience is confined to no-code/low-code builders and who do not write and debug code independently.
- People who need a defined brief to start. You will often be the only person who knows a problem exists. Nobody will hand you a spec, a backlog, or a sprint plan.
Click on Apply to know more.
