Engineer; AI-Native

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

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.

• 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. Hub Spot, Clay, Claude agents, Zoom Info, 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.

• Week 1–2
• Wire. Encode ICP per product. Wire Hub Spot lifecycle, Clay and Zoom Info 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.

• 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 (Hub Spot, Clay, Zoom Info, 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.

• 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 Hub Spot plus Clay‑class tools and Zoom Info or comparable. Configured by you, not briefed.
• Built and owned demand gen or growth at a B2B enterprise or regulated‑industry SaaS.
• Light code…