Live roles

Editor’s noteConsulting role driving AI adoption across client organizations — you coach executives and guide teams, not build AI systems.

Editor’s noteEnterprise AI adoption role in fashion/retail — you translate customer AI usage into playbooks and guide large teams through transformation, not a coding seat.

Editor’s noteAI adoption lead role at a consulting firm — you teach enterprise teams to work with AI through curriculum, labs, and executive coaching; code is explicitly not part of the job.

Editor’s noteGrowth seat owns AI-powered GTM automation — you ship outbound workflows and tooling integrations, not software engineering.

Editor’s noteContent creator role at an AI company building with Voice AI — you ship demos and prototypes on camera, not production code.

Editor’s noteKnowledge ops role owning the help center, AI-assisted content workflows, and AI assistance optimization using Claude and ChatGPT — light on engineering, heavy on scaling knowledge with AI.

Editor’s noteEnterprise AI adoption lead role — you own making AI stick across the whole org, from training rollout to governance guardrails. Light on dev, heavy on change management and fluency-building.

Editor’s noteRed teaming seat — you create prompts to break AI models and document where they fail against safety taxonomies; light on dev, heavy on judgment work.

Editor’s noteOwn and ship marketing agents that run campaigns autonomously — you build the AI workflows, not the underlying platform.

Editor’s noteOperator role running AI agents for marketing workflows — configure, prompt, iterate, not code from scratch.

Editor’s note10-week intern seat building AI-powered tools and agentic automations with vibe coding emphasis — ship working demos, not polished products.

Editor’s noteBuild-and-ship role for someone who lives in vibe coding, workflow automation, and prompt libraries — hand off to engineering follows, but you own the working prototype.

Editor’s noteHands-on ops role building and tuning AI workflows for small business clients — you own the automation, not the platform.

Editor’s noteBuild and ship client-facing AI agents and automations end-to-end using no-code/low-code tools — minimal coding, heavy on delivery and iteration.

Editor’s notePrompt and eval work shaping e-commerce AI training data — you build realistic shopping simulations and score model outputs, not ship production code.

Editor’s noteForward-deployed PM role — you own the biopharma client relationship and vibe code lightweight AI automations to reduce manual reporting, not build production systems.

Editor’s noteSupply chain lead role where you design and deploy AI agents for supply chain workflows, then upskill teams to own and run them.

Editor’s noteHands-on operator turning AI search into a growth channel — heavy on LLM prompting and content shaping, light on traditional coding.

Editor’s noteGrowth PM seat on a high-converting AI B2C SaaS — you own acquisition, activation, and retention end-to-end, with daily AI prototyping via Claude Code for production concepts.

Editor’s noteSenior IC driving enterprise-wide AI fluency and workflow redesign across people teams — builds enablement programs, not production software.

Editor’s noteGTM engineer seat building and shipping AI-driven automation for revenue ops — deep on workflow tools, light on dev, and direct leverage over how the GTM team actually scales.

Editor’s noteSenior automation role — you build AI-powered GTM workflows at scale, but Marketo architecture, Salesforce routing, and SQL are the real core work, with AI tooling layered on top.

Editor’s noteCreative technologists design and maintain generative AI video workflows in a film production setting — heavy on workflow building, moderate Python, and heavy AI fluency.

Editor’s noteOwn the full PLG loop for an AI-focused product using Clay, n8n, and LLMs — you ship growth agents, not a marketing roadmap.

Editor’s noteCreative AI specialist role building automated pipelines for video ads and social content at scale — heavy on AI generation tools and workflow engineering, light on traditional dev.

Editor’s noteContent creator role using AI tools daily to produce marketing assets for restaurant tech partnerships — you ship copy, visuals, and video, not code.

Editor’s noteAI enablement manager driving adoption across three marketing agencies — you identify use cases, run enablement, and embed AI into workflows, not build or ship software.

Editor’s noteContent creator role using generative AI to produce Instagram videos — you make the content, not the models.

Editor’s noteRev ops lead at an SEO AI startup — building automations with n8n and Clay for the sales team, light on engineering work.

Editor’s noteQuality-specialist seat evaluating AI agent behavior at scale — you're watching for hallucinations, looping, and escalation failures, then feeding that back to improve how agents perform.

Editor’s noteAI-native operator building and shipping internal AI agents and lightweight apps across recruiting, finance, and sales — you own the whole loop from spec to observability.

Editor’s noteProduct builder role that blends PM instinct, design thinking, and TypeScript coding — AI fluency is table stakes, but this leans engineering-heavy and asks you to own full product arcs end-to-end.

Editor’s noteFinance and accounting pro who builds and owns AI-driven automation workflows — this role owns the automation, not the underlying platform engineering.

Editor’s noteEnterprise AI adoption role — you turn Writer's platform into working AI workflows for customers, build champion networks, and run the workshops that make adoption stick. Light on dev, heavy on enablement and activation strategy.

Editor’s noteAI adoption consulting role — you guide enterprise clients from discovery through capability-building, heavy on enablement and change management, light on delivery engineering.

Editor’s noteCSM role where you build and tune the operational programs that help customers get value from HeyGen's AI video platform — light on engineering, heavy on automation, onboarding design, and cross-functional execution.

Editor’s noteCustomer-facing AI adoption role — you translate AI capabilities into working systems for Fortune 500 clients, with hands-on work in prompt design and workflow configuration, not backend engineering.

Editor’s noteAI consulting lead driving client AI adoption and workflow automation through low-code platforms—85% of the work is solution delivery and enablement, not platform engineering.

Editor’s noteAI customer success role guiding enterprise clients through BrazeAI adoption — you translate product capabilities into customer value, not build the underlying AI.

Editor’s noteAdversarial AI testing role — you probe AI systems for safety and security weaknesses through prompt injection, attack chains, and adversarial inputs.

Editor’s noteGround-floor operator role — you vibe-code the marketplace into existence alongside the founder, working with external devs and shipping AI-built automations, not writing production code yourself.

Editor’s noteClient-facing implementation role building AI automations inside Alexia — you map processes, configure workflows and integrations, then coach clients to use them.

Editor’s noteSEO specialist role using AI tools for keyword research, content optimization, and automation — SEO expertise is the primary craft, AI augments the workflow.