About AICRO

AICRO is the first operator-built, AI-powered GTM system for modern revenue teams. We engineer complete revenue systems that turn market signals into qualified pipeline—built by CROs who’ve actually carried quota, powered by automation infrastructure that compounds our execution velocity.

The Role

As Head of Engineering for GTM Systems, you own the technical infrastructure that powers our entire revenue engine. This is where automation expertise meets software engineering—you’ll be building AI agent systems in Claude Code, designing data pipelines, and developing the automation architecture that scales across every client engagement. You’re simultaneously leading and growing a team of of GTM engineers who execute alongside you.

Your primary focus is building and technical leadership, not client management. That said, you should be comfortable stepping into client conversations when technical depth is needed—explaining how a custom agent works, walking through system architecture, or diagnosing why an enrichment pipeline isn’t firing correctly.

You report directly to the CEO/Founder. Expect rapid iteration, data-driven decisions, and the autonomy to architect systems the way you believe they should be built.

What You’ll Own

Agent Architecture & Engineering

• Design, build, and maintain AI agent systems in Claude Code - from signal detection and lead scoring to campaign orchestration and response handling
• Architect the software infrastructure that connects our stack—Airtable, Slack, email infrastructure, CRMs, enrichment APIs, and third-party data sources
• Build and extend custom application capabilities as our core automation platform—writing production-quality code that the entire team deploys against
• Create reusable agent templates, SDK components, and engineering patterns that let the team spin up new client deployments rapidly

Team Leadership & Engineering Culture

• Lead and grow a hybrid team of dedicated engineers—hiring, onboarding, setting engineering standards, and code review
• Establish development practices: version control workflows, testing standards, documentation, and deployment processes
• Build the training pipeline that levels up engineers from automation generalists into AI agent developers
• Scale the team as client demand grows—own capacity planning, resource allocation, and technical hiring

Technical Innovation & Platform Development

• Stay ahead of the AI/automation tooling landscape—evaluate new frameworks, LLM capabilities, and integration patterns
• Contribute to and extend our Claude skill library—encoding automation patterns into reusable, AI-assisted workflows
• Be the internal authority on what’s possible—when someone asks “can we automate X?” you have the answer and often already have a working prototype

Systems Reliability & Performance

• Own the reliability of our automation infrastructure—monitoring, error handling, logging, and incident response
• Optimize systems for cost and performance—API calls, token usage, processing time, and infrastructure spend all matter at scale
• Build the observability layer that surfaces issues before clients notice them

What You Bring

Non-Negotiable

• Deep automation and systems engineering experience—you’ve built GTM automation systems that actually run in production. Clay workflows with HTTP requests, AI enrichment, and multi-step logic. n8n or Make.com automations that connect APIs, transform data, and handle errors gracefully. Webhook architectures that tie CRMs, enrichment tools, and outreach platforms together. “I’ve used Clay” isn’t enough—we need “I’ve built systems in Clay that process thousands of records reliably and I can explain the data architecture behind them.”
• Working coding ability and appetite to go deeper—you can write Python, JavaScript, or both. Maybe you started with JSON prompting and API calls, then moved into scripting, and now you’re building more complex systems. You don’t need to be a senior software engineer on day one, but you need to be comfortable in a CLI, able to read and write code that does real work, and genuinely excited about leveling up into production engineering. The trajectory matters as much as where you are today.
• AI agent and LLM systems experience—you’ve built workflows that use Claude, GPT, or similar models as core components. You understand prompt engineering at a systems level—not just writing one-off prompts, but designing structured prompt logic, chaining agent actions, managing context, and building AI-powered automation that handles edge cases. If you’ve worked with Claude Code, Cursor, or similar AI-native dev environments, even better—Reel is built on Claude Code and you’ll be extending it.
• GTM context and revenue operations understanding—you know how outbound campaigns actually work. How signals turn into lists, how lists turn into sequences, how replies turn into meetings. You understand the data flow from enrichment through scoring through delivery—and you’ve built systems across that chain. This isn’t an engineering role where GTM is an afterthought; the GTM context IS the engineering problem.
• Experience leading or coordinating technical teams—you’ve managed, mentored, or coordinated engineers, freelancers, or offshore teams. You know how to set standards, review work, and grow people’s capabilities. You can context-switch between building and leading without dropping quality on either.

Strong Preference

• Production coding experience (Python/JavaScript/TypeScript)—you’ve built, deployed, and maintained software that handles real workloads. You understand APIs from both sides, can architect a data pipeline, and are comfortable with version control and deployment workflows. This is the growth ceiling for the role—the closer you are to this on day one, the faster you’ll take ownership of Reel development.
• Agency or consultancy background—you’ve built systems that serve multiple clients with different requirements, not just one internal tool. You know the difference between a prototype and production infrastructure that needs to work across 20 different client configurations.
• Community presence in GTM engineering or automation—you’re active in Clay communities, automation forums, or GTM engineering circles. You ship publicly, share what you learn, and stay connected to how the tooling landscape is evolving.
• DevOps/infrastructure awareness—CI/CD, deployment pipelines, monitoring, and cloud basics. Not required for day one, but invaluable as we scale the platform.

What You Get

• Competitive base + performance bonus tied to system performance, platform development milestones, and team output
• Remote-first with async-heavy culture—we care about what you ship, not hours logged
• Budget for tools, learning, and experiments—if you find something that makes us better, we’ll get it
• Direct access to founding team—shape the technical direction and platform architecture, not just execute someone else’s vision
• Equity participation for the right candidate—this is a leadership role building core infrastructure