Live roles

Editor’s noteAudio annotation and linguistic QA role for Grok's voice capabilities — you judge speech quality and cultural nuance, not build AI systems or workflows.

Editor’s noteOwns AI transformation for a GTM function — builds production automations for sales, marketing, or CS teams using LLMs and agent frameworks, with direct executive visibility.

Editor’s noteStaff PM seat owning a major consumer surface end-to-end — you also model what AI-native PM craft looks like, ship prototypes with AI tools, and raise the bar for the function.

Editor’s noteAI adoption role in government — you teach public servants to use ChatGPT, build their communities, and create the content that makes AI stick; light on dev, heavy on enablement craft.

Editor’s noteCustomer-facing AI deployment role driving adoption across enterprise insurance brokerages — you enable teams, translate needs into configuration, and measure ROI, with no coding required.

Editor’s noteBSA role that translates sales and marketing workflows into AI agents and orchestration inside Salesforce—light on dev, heavy on translating business intent into agent-ready specs.

Editor’s noteSenior ABM & Campaigns seat — you blend AI tools into GTM motion, build no-code automations, and own account-based pipeline in an AI observability company.

Editor’s noteRevOps role heavy on Salesforce/HubSpot architecture and data infrastructure, with AI automation as a layer on top — you ship Clay workflows and vibe-coded automations, not the CRM itself.

Editor’s noteCreative producer role centered on using GenAI to scale mobile game ads — you ship creatives, not code.

Editor’s noteGTM engineer role where you build and own Clay-and-Claude-powered outbound workflows — you ship the enrichment stack, not the platform.

Editor’s noteEmbedded AI solutions architect role — you find inefficiencies in business teams and ship working agents/pipelines to fix them, not build platforms.

Editor’s noteRed team role that stress-tests frontier AI models for dangerous outputs — you bring offensive security craft, not engineering infrastructure, to a structured evaluation program.

Editor’s noteRed teaming seat evaluating AI model safety — you construct prompts and document where models fail, not write code or ship features.

Editor’s noteSystems-builder role inside the Office of the CEO — you ship AI agents and internal tools, not production software, using vibe-coding and lightweight infrastructure work.

Editor’s noteGrowth Lead role for someone who builds their own landing pages, microsites, and automation with vibe-coding tools — you ship the growth, not the roadmap.

Editor’s noteBuilds and ships recruiting automations using AI tools — you own the workflow, not the platform.

Editor’s noteQA lead role defining and executing quality standards for AI prompt outputs — you own the evaluation lifecycle, not the underlying models or infrastructure.

Editor’s notePM role owning agent fleet product and chat flow evals — prototype fast with AI tools, run 15-20 user sessions weekly, decide what ships.

Editor’s notePM role defining and shipping multi-agent AI systems at massive scale — you own AI product direction, not backend engineering, and prototype with vibe coding tools rather than writing production code.

Editor’s noteAI strategy role guiding developers from manual coding to natural language orchestration — vibe coding and reasoning models are the core work.

Editor’s noteCreative-technologist role at Princeton using AI tools (Claude, Runway, Suno, Elevenlabs) to architect and automate multi-platform marketing campaigns — you generate content at scale, not build software.

Editor’s noteCross-functional AI transformation seat — you identify broken workflows and rebuild them with AI tools, no deep engineering required.

Editor’s noteBuild and ship AI-powered workflows across sales, marketing, support, HR, and finance — you own the automation end-to-end, measured by what ships, not what's scoped.

Editor’s noteEmbedding AI into business operations — you ship working agentic workflows (n8n, vibecoding) and measure them against cycle-time and quality thresholds.

Editor’s notePM role shipping LLM-powered features (agents, RAG, intelligent assistants) on a sustainability platform — vibe-code your own prototypes, set eval criteria, and own what gets built.

Editor’s noteSenior enablement role driving AI adoption across Match Group brands — you build playbooks, prompt libraries, and training programs, not production code.

Editor’s noteAdoption role at an energy company scaling AI tools across teams — you drive capability, not code; light on dev, heavy on coaching and rollout.

Editor’s noteYou train teams and deploy AI tools across departments — heavy on teaching non-technical staff, light on engineering or building core AI.

Editor’s noteEnablement-heavy AI builder role — you build agents and workflows while driving enterprise-wide adoption through training, champions networks, and prompt libraries.

Editor’s noteEnablement lead role building AI capability across a biotech ecosystem — hands-on coaching, training programs, change champion networks, and tool adoption; light on dev work.

Editor’s noteInternal AI enablement role getting Microsoft Copilot and M365 AI tools actually used by operations staff — heavy on training, coaching, and workflow translation, light on dev.

Editor’s noteOwns AI support infrastructure from the ground up — you deploy agents, build the knowledge base that retrieves against, then automate ticket flows so the team stays lean.

Editor’s noteSenior AI enablement role building company-wide AI fluency through training programs, community of practice, and cross-functional capability building — you grow the org's AI muscle, not own production workflows.

Editor’s noteBuild clinical AI modules in a no-code platform for hospital workflows — prompt work, validation against clinical evidence, light on traditional engineering.

Editor’s noteInternal AI transformation lead role — you own how the whole company adopts AI, from hands-on prototyping with RAG and lightweight agents to driving adoption across GTM, Services, and Finance.

Editor’s noteEnablement-focused AI role building workflows and training GTM teams to use AI tools — you ship the adoption, not the platform.

Editor’s noteOps role building and deploying AI automations for client briefs using n8n, Zapier, and Claude Code — you ship the workflow, not the platform.

Editor’s noteOperations role building and tuning AI automations for sales and internal workflows — you ship the automation, not the platform. Light on coding, heavy on running things.

Editor’s noteCoaching and change-management role in construction that gets employees actually using AI tools — no AI system building required, heavy on 1:1 enablement and training delivery.

Editor’s noteOperations role managing AI agent deployments into enterprise financial environments — you keep the workflows running, handle escalations, and improve the playbooks, not the code.

Editor’s noteEnables field teams to understand, adopt, and sell OpenAI products — builds systems and workflows rather than training content, with automation and AI as tools.

Editor’s noteEnablement role driving AI adoption across business teams — heavy on use-case mapping, workflow design, and change management, not implementation.

Editor’s noteEnablement seat building AI capability across business teams — you run pilots and build playbooks, not own a product or operate live agent workflows.

Editor’s noteAI adoption and process change role — you build the framework, playbooks, and training that help teams across the company use AI tools responsibly.

Editor’s noteSenior architect role shipping AI solutions for government and enterprise clients using vibe coding and agentic IDEs — you build the proof-of-concept, not the platform.

Editor’s noteProduct-builder seat using AI coding tools to ship SaaS features end-to-end — you're generating the code and shipping the product, not owning the platform.

Editor’s noteGrowth marketer seat where you build and run AI agent workflows for content, paid, and distribution — one-person output at 10-person scale, minimal traditional marketing ops.

Editor’s noteProduct Builder role defining agent analytics as a category—you prototype with AI tools, ship working software, and own strategy end-to-end, not just specs and handoffs.

Editor’s noteSystems ownership role for Pigment (financial planning) with AI adoption work across Finance — moderate coding via SQL and integrations, but core work is running and scaling AI-enhanced finance workflows.