Rwazi
AI Engineer – Marketing & GTM Systems
RemoteUTC-8…UTC-3
- Role
- AI / ML
- Employment
- Full-time
Salary not disclosed
Check eligibility
Open to UTC-8…UTC-3. Set where you work from to check your eligibility.
No BS summary
AI engineer for GTM/marketing automation who ships production workflows with LLM APIs, Python and/or TypeScript, scraping, enrichment, and API integrations. Must have built autonomous or semi-autonomous production workflows and be available with meaningful US-timezone overlap.
Core skills
LLM APIsPython/TypeScript
Required skills
ClaudeGPTPrompt engineeringAgent frameworksRAGScrapingAPI integrationsCRMHubSpotSalesforceClayApollon8nMakeZapier
Rwazi is a global consumer intelligence platform. Our go-to-market engine still runs on too many manual workflows — prospecting, enrichment, campaign ops, content production, reporting. Your job is to absorb those workflows into AI systems that run themselves.
You will not write strategy decks. You will ship working tools, weekly, that remove manual GTM work and make pipeline move faster.
What you'll build
- Outbound engine: lead sourcing → enrichment → scoring → personalized sequencing, wired into our CRM. Agentic where possible, human-in-the-loop where it matters.
- Inbound & lifecycle flows: lead routing, qualification, nurture triggers, activation and re-engagement automations.
- Content pipeline: AI-assisted production for outbound copy, landing pages, social, and campaign assets — with QA gates so nothing off-brand ships.
- GTM data layer: dashboards and reporting that show pipeline, conversion, and campaign performance without anyone assembling them by hand.
- Temporary fixes: when a GTM workflow breaks or a tool gap appears, you build the patch fast rather than waiting on a vendor.
First 90 days (how you'll be evaluated)
- Day 7: first shippable artifact live — a working flow, not a plan.
- Day 30: 2–3 GTM automations in production; outbound engine in alpha.
- Day 60: measurable scope absorption — which manual GTM workflows are you removing per week?
- Day 90: trial decision, based on shipped output and hours-saved/pipeline-moved numbers.
You
- Ship fast with LLM APIs (Claude, GPT) — prompt engineering, agent frameworks, RAG where useful
- Strong Python and/or TypeScript; comfortable with scraping, enrichment, and API integrations
- Hands-on with the modern GTM stack: CRM (HubSpot/Salesforce-type), enrichment (Clay/Apollo-type), orchestration (n8n/Make/Zapier), email infra
- Have built and can demo autonomous or semi-autonomous workflows that ran in production — links or Looms beat resumes
- Self-directed. You find the manual workflow, propose the fix, and ship it. Raising a problem without a proposed fix is not how we work.
- Available with meaningful US-timezone overlap
Engagement
- Contractor
- 25–40 hrs/week
- 3-month mutual trial; rate and scope re-evaluated at Day 90
- Reports into Marketing/GTM leadership (not Engineering)
To apply
- Link the best AI-powered GTM or marketing automation you've built. What did it replace, and what number did it move?
- Which part of a typical outbound flow would you automate first, and how?
- Your hourly rate and weekly availability (US-overlap hours).
Applications without a shipped-work link will not be reviewed.
What you'll do
- Absorb manual GTM workflows into AI systems that run themselves.
- Ship working tools weekly that remove manual GTM work and make pipeline move faster.
- Build an outbound engine for lead sourcing, enrichment, scoring, and personalized sequencing, wired into the CRM.
- Make outbound workflows agentic where possible and human-in-the-loop where it matters.
- Build inbound and lifecycle flows including lead routing, qualification, nurture triggers, activation, and re-engagement automations.
- Build an AI-assisted content pipeline for outbound copy, landing pages, social, and campaign assets.
- Implement QA gates so off-brand content does not ship.
- Build a GTM data layer with dashboards and reporting for pipeline, conversion, and campaign performance.
- Build fast temporary patches when a GTM workflow breaks or a tool gap appears.
- Deliver a first shippable artifact by Day 7.
- Put 2–3 GTM automations in production and an outbound engine in alpha by Day 30.
- Remove measurable manual GTM workflows per week by Day 60.
- Demonstrate shipped output and hours-saved or pipeline-moved numbers by Day 90.
- Find manual workflows, propose fixes, and ship them.
- Report into Marketing/GTM leadership.
- In the application, link the best AI-powered GTM or marketing automation built and explain what it replaced and what metric it moved.
- In the application, explain which part of a typical outbound flow would be automated first and how.
- In the application, provide hourly rate and weekly availability with US-overlap hours.
What they require
- Ship fast with LLM APIs including Claude and GPT, prompt engineering, agent frameworks, and RAG where useful.
- Strong Python and/or TypeScript.
- Comfortable with scraping, enrichment, and API integrations.
- Hands-on with the modern GTM stack: CRM such as HubSpot or Salesforce, enrichment such as Clay or Apollo, orchestration such as n8n, Make, or Zapier, and email infrastructure.
- Have built and can demo autonomous or semi-autonomous workflows that ran in production.
- Links or Looms to shipped work are preferred over resumes.
- Self-directed; finds manual workflows, proposes fixes, and ships them.
- Available with meaningful US-timezone overlap.
- Applications without a shipped-work link will not be reviewed.
Rwazi is a global consumer intelligence platform.
Consumer Intelligence
Details
Apply routeDom
Salary not disclosed