Technical Chief of Staff (CEO) — Ops, GTM & Systems Lead (AI‑Augmented)

Technical Chief of Staff (CEO) — Ops, GTM & Systems Lead (AI‑Augmented)

Company: Truey × Inneractive

Location: Remote‑first

Type: Full‑time

C2C with your own LLC considered; NO staffing vendors — direct to Truey.

If you’re looking for a role that’s mostly coding, this won’t be a fit. This role is about operating, integrating, QA’ing, and systematizing across GTM + ops—with some technical work when useful.

Why this role exists

We’re building fast across two small, founder-led orgs. The CEO is currently the bottleneck across operations, GTM systems, tool integrations, QA/UAT, content workflows, and “random but important” tasks.

We’re hiring a high‑ownership operator who can take ambiguous tasks, run them end‑to‑end, and build the systems (process + automations + documentation) that keep things moving—using AI to research, draft, test, and execute with speed and accuracy.

This is not a pure software engineering role.You should be comfortable doing a blend of systems work, admin, QA, content ops, and GTM execution—with some lightweight scripting/integrations where helpful.The Role

You are the CEO’s right hand across both companies, responsible for turning priorities into shipped outcomes. You’ll own the “operating system” that keeps projects and day‑to‑day execution moving:

- GTM execution + automation QA - Content/catalog workflow ownership - Tool integration + business systems - Release QA/UAT + coordination - Internal ops + lightweight IT/process - Ad hoc CEO-delegated tasks (with excellent follow-through)

You’ll partner 1:1 with the CEO and collaborate with engineers, contractors, and vendors.

What You’ll Do1) GTM Ops: lead response, pipeline, and automation quality

- Monitor inbound leads and respond quickly using templates + AI drafts (while keeping tone and claims accurate). - Qualify and route leads; schedule meetings; keep CRM updated and clean. - Review and QA outbound automation before it goes live (personalization fields, links, compliance, deliverability basics). - Maintain and improve follow‑up sequences, routing rules, and tracking.

2) Content Ops: catalog/site content workflow ownership

- Run the content pipeline for our catalog site: generation → review → QA → publish → update. - Use and improve our custom AI content tools (prompts, templates, guardrails, QA checklists). - Coordinate content changes with engineering when needed (clear tickets + acceptance criteria). - Maintain consistent formatting, metadata, internal linking, and quality standards.

3) Systems & Integrations: connect tools and reduce manual work

- Implement and maintain automations (Zapier/Make/n8n-style workflows, webhooks, API connections). - Evaluate and integrate third‑party tools to streamline GTM + operations. - Create lightweight scripts or internal utilities when no-code isn’t enough (basic Python/JS is a plus, not required). - Document systems so they’re maintainable and not “tribal knowledge.”

4) QA/UAT + coordination across engineering and ops

- Translate CEO asks into clear specs/tickets (scope, assumptions, acceptance criteria, edge cases). - Run UAT and regression checks on releases; file high-quality bug reports with steps to reproduce. - Coordinate with engineers/QA contractor(s) to confirm fixes and close loops. - Maintain release checklists and QA standards.

5) Internal Ops + lightweight IT/process ownership (remote-friendly)

- Own onboarding/offboarding checklists: accounts, permissions, tool access, documented steps. - Manage SaaS admin tasks (permissions, licenses, access reviews) and vendor coordination. - Help standardize device/software setup via documented SOPs (and coordinate hands-on work when needed).

6) “Whatever the CEO delegates”

- Take on high‑priority tasks that don’t fit neatly into a bucket—research, comparisons, drafting SOPs, setting up workflows, vendor coordination—then deliver with clarity and completeness.

How We Work

- Remote-first, async-friendly. - Weekly priorities + a simple execution cadence (you’ll help run it). - Clear writing matters: specs, SOPs, and status updates are part of the job. - You’ll have broad access to systems; trustworthiness and discretion are essential.

Core Tools / Skills You’ll Use (not all required)

Business Systems & Automation: Zapier / Make / n8n-style automation, webhooks, APIs, spreadsheets

GTM Systems: CRM (HubSpot/Zoho/etc.), email sequencing/automation, lead routing

Content Ops: CMS workflows, structured content QA, metadata, publishing

Execution: Notion/Linear/Jira/Trello-style task management, SOP writing, checklists

QA: test plans, reproduction steps, acceptance criteria, release checklists

Nice-to-have technical fluency: basic HTML/CSS, light scripting (Python/JS), SQL basics

What You Bring (Must‑Haves)

- Proven experience as a high-ownership operator (ops, chief of staff, business systems, growth ops, revops, technical PM, implementation/systems) in a fast-moving environment. - Strong judgment and ability to handle ambiguity: you can turn “rough idea” → “shipped outcome.” - Excellent written communication (clear, concise, high signal). - Detail-oriented: you catch broken links, bad merge fields, wrong claims, edge cases, and inconsistent formatting. - Comfortable working across disciplines: GTM, ops, light technical work, and QA. - Strong learning speed: you can research unfamiliar topics quickly (including with AI) and implement correctly.

Nice‑to‑Haves (Great, not required)

- You’ve owned or rebuilt a GTM automation stack (routing + sequences + QA + reporting). - You’ve run a content operation or catalog workflow (especially with AI-assisted generation). - You’ve worked closely with engineers and can write great tickets/specs. - Familiarity with SaaS admin, onboarding/offboarding, permissions, and basic security hygiene. - You’ve supported a CEO/founder directly and enjoy being the “force multiplier.”

What Success Looks Like

In 30 days

- Lead response + outbound review is reliable and on-brand. - You’ve documented core workflows and tightened obvious bottlenecks. - You can run UAT and push tasks through without heavy CEO involvement.

In 60 days

- Key automations are stable, monitored, and documented. - Catalog/content workflow is predictable with clear QA gates. - Engineers receive clear specs and fewer back-and-forth cycles.

In 90 days

- CEO is no longer the default “router” for ops/GTM/system tasks. - Manual work is reduced measurably, and execution is calmer and faster.

How to Apply

Send:

- Resume / - A short note describing 1–2 examples where you built or fixed an ops/system workflow end-to-end - (Optional but helpful) a sample SOP/spec you wrote, or a short Loom walking through an automation you built