You'll own the full stack of how Guardio communicates with its users across email, SMS, voice, and beyond.
Ownership here means three things: being the technical backbone that makes the stack work reliably at scale; enabling Growth & Product to use these systems independently; and spotting where we're leaving money on the table and acting on it.
You think like a technical product manager who builds things themselves, or a growth manager who genuinely cares about ARR. You collaborate with engineers as a peer, design systems others can operate, and connect the dots between a data signal and a revenue opportunity.
You will
Own the full communications stack end-to-end - architecture, configuration, governance, and documentation across Customer.io, Retell, and Twilio.
Be the internal expert everyone trusts - the person teams come to when they want to do something new with comms and need to know what's possible, what's smart, and what to avoid.
Build and maintain the technical layer - lifecycle flows, integrations, and automations. Enforce the guardrails that keep it clean: send frequency logic, suppression rules, fallback handling, and data hygiene.
Proactively identify revenue opportunities and lifecycle gaps (upsell moments, win-back sequences, churn risks) and own them from idea to shipped experiment.
Use AI to build, maintain, and optimize messaging skills - test, learn, and make every communication smarter over time.
Build the playbooks, templates, and documentation that let Growth, Marketing, and Product work on the comms stack independently.
Sounds great! Am I the right fit?
Well, our guess is you have a good chance of being that person if you check as many of these as possible:
3+ years in a technical role - lifecycle, CRM, growth, or marketing ops, ideally at a startup or growth-stage company.
Hands-on with at least one serious lifecycle, AI voice agent, or CRM tool - Customer.io, Braze, Iterable, Klaviyo, Retell AI, or equivalent. You've built complex flows yourself.
Genuinely excited about AI - you've built and maintained skills or agents and see them as a core part of how you work.
Technically confident: comfortable with APIs, webhooks, event-based data models, and data structures. You can read documentation, debug integrations, and have a real conversation with a backend engineer.
A systems thinker who builds for others - clean, structured, and ready for the AI era.
Revenue-oriented: you love spotting opportunities in the data and turning them into real business impact.
This is an IC role with the opportunity to build and lead a small team over time.
Requirements
