Posting record
Open 12+ days
- Rwazi's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Rwazi, so its true age is longer.
Last checked Nov 4, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
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.
Something wrong with this posting?