Growth Engineer (AI-Native)

iTmethods · Remote · Reports to the CMO. Partners with the CRO and VP Engineering.

An AI-native operator who owns high-velocity agentic GTM, then gets pulled into whatever the company actually needs next. Reign Ops, Reign Factory, Reign Gateway, and Reign Assurance are the product lines. iTmethods is the company. You design the strategy, orchestrate multi-agent workflows, run the agents, and ship the pipeline end to end. You also show up for product, sales, ops, and internal systems when that is the higher-leverage move.

This is not a marketing hire.

Why this role exists
iTmethods is a 21-year, profitable enterprise platform company that has rebooted AI-native. We sell into highly regulated enterprises in financial services, healthcare, pharma, defense, and semiconductors. We are shipping and relaunching multiple products. The person in this seat is the operator behind the motion, and a utility player for the rest of the company.

You operate at executive cadence. You report to the CMO, with regular alignment to the CRO and VP Engineering. Decisions in hours, not committees. No middle-management lift.

The work will not stay inside growth. Some weeks you are building demand systems. Some weeks you are standing up an internal agent, fixing a broken handoff, helping a product launch land, or taking a problem nobody has named yet and making it run. If you need a tidy marketing lane, this is the wrong role.

What you will own

• The number, across the portfolio. Marketing-sourced and marketing-influenced pipeline for every product you operate on.
• The agentic launch motion. Demand engineering for each product launch as it ships. New initiatives kick off on a quarterly cadence. You orchestrate the playbook and compound it launch after launch.
• The stack. HubSpot, Clay, Claude agents, ZoomInfo, and our internal Campaign Manager and Sales Manager surfaces. You configure, automate, and orchestrate the multi-agent system yourself.
• Data discipline. Encoded ICP per product, clean living segments, continuous scoring.
• Governed execution. Every agent and workflow runs through Reign Gateway, with a record. Reign Assurance is how we prepare evidence; people decide.
• Work outside the lane. Sales enablement, product launch support, internal tooling, ops automation, research, and whatever else the CMO, CRO, or VP Engineering put in front of you. You learn the domain fast and ship.

Your first 30 days (AI-native cadence)

• Week 1–2 · Wire. Encode ICP per product. Wire HubSpot lifecycle, Clay and ZoomInfo enrichment, Claude agent workflows, measurement. Learn the products, the buyers, and the internal systems well enough to be useful outside GTM.
• Week 3 · Ship. Launch playbook live on the first two product motions. Always-on nurture activated per ICP. Content engine connected to capture.
• Week 4 · Compound. Trigger-based ABM on regulatory events (EU AI Act, SR 26-2, DORA, FDA PCCP). Reliable MQL to SQL handoff. Reusable agentic playbook documented. First non-GTM problem taken off someone else's plate.

How you will work

• You are AI-native. You build with agents, skills, and MCP connectors. You do not wait for a specialist, and you do not brief work you could ship yourself.
• You learn in public and in production. New domain, new tool, new buyer, new internal mess: you get fluent fast.
• You are dynamic. Context switches weekly. Multiple products, multiple motions, plus unplanned work from the executive team. You do not need a static job description to know what to do next.
• You build in the stack (HubSpot, Clay, ZoomInfo, Claude agents). Not by briefing others to.
• You have an engineering team of builders behind you. The same people who ship Reign Ops, Factory, Gateway, and Assurance work alongside you.
• No high-volume AI slop. Precision and trust over noise, because we sell into banks, hospitals, and defense.

Who you are (must-haves)

• AI-native builder, not AI-curious manager. You have shipped multiple production agent or LLM workflows. You write your own prompts, compose your own skills, configure your own MCP connectors. This is the filter. If you "use ChatGPT" and manage a vendor, stop here.
• Learner. You pick up new products, tools, and domains without a curriculum. You get dangerous in a stack you did not know last month.
• Dynamic, and useful outside growth. You have done real work beyond campaigns and demand gen: ops, product, sales support, internal tools, implementation, or something adjacent. You do not protect a marketing lane.
• Hands-on fluency with HubSpot plus Clay-class tools and ZoomInfo or comparable. Configured by you, not briefed.
• Built and owned demand gen or growth at a B2B enterprise or regulated-industry SaaS.
• Light code comfort. TypeScript or Python at read-and-modify level. JSON-LD and YAML at author level.
• You write, build, and analyze. Not a vendor manager.
• Track record selling into long, regulated enterprise cycles where trust is the gate.

This is not

• A growth marketer who wants an AI overlay on last year's playbook.
• A specialist who only wants to own paid, content, or lifecycle.
• A manager who assigns agent work to someone else.
• A high-volume outbound operator optimizing for activity over trust.

Compensation

Competitive. Benchmarked against Toronto B2B SaaS and the North American AI-native growth-engineering market.

How to apply
The application asks for one artifact and four short answers. A short paragraph plus a link beats a long resume.

1. Walk us through a Claude or OpenAI skill you shipped in the last 90 days.
2. Show us a HubSpot or Clay agentic workflow you built yourself.
3. Give us an example of work you did that was not growth or marketing, and how you got up to speed.

The fine print

• This is an active, funded role. We are hiring now.
• We use AI-assisted tools for resume screening and interview scheduling. Final hiring decisions are made by humans.
• Candidates reaching the final interview receive a decision within 30 days.
• iTmethods is an equal-opportunity employer. We hire on merit and on what you have built. Canadian work experience is not required.