Live roles

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 noteHands-on operator turning AI search into a growth channel — heavy on LLM prompting and content shaping, light on traditional coding.

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 noteSEO specialist role using AI tools for keyword research, content optimization, and automation — SEO expertise is the primary craft, AI augments the workflow.

Editor’s noteFoundational marketing ops role where you architect and automate go-to-market workflows using AI tooling — your output is a running growth engine, not software features.

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 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 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 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 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 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 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 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 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.

Editor’s noteGTM automation role — you build and run enrichment pipelines and outbound workflows across Clay, Zapier, and AI tools, with measurable impact on sales team productivity.

Editor’s notePart-time contractor seat contributing senior ops expertise to AI training data — you design real-world tasks and evaluate how AI handles operations scenarios.

Editor’s noteOps role running AI workflows in a post-sales org — you build automations in Workato and configure them in Salesforce/Gainsight/Zendesk, not write production code.

Editor’s noteStrategic AI enablement seat — you own the roadmap, governance, and champion networks that make the rest of Headspace AI-capable, not the AI products themselves.

Editor’s noteSenior AI product seat shaping Generative AI features across financial product suites — you ship AI capabilities, lead a team, and talk to senior leadership, not write production code.

Editor’s noteEnablement-first role coaching Sales and Ops teams on AI tools — you configure agents and workflows, but your real job is making people actually adopt them.

Editor’s noteBuilder-first PM role prototyping and shipping AI adoption products — vibe coding with Claude Code/Cursor is non-negotiable, but you're shipping features, not production engineering.

Editor’s notePrototyper role where you prompt AI tools to build functional front-ends — your craft is product vision and iteration speed, not writing code yourself.

Editor’s noteCreative technologist role building AI-powered marketing assets and shipping prompt libraries that let non-designers generate on-brand visuals — vibe coding required, platform engineering minimal.

Editor’s noteCross-functional AI adoption role — you're teaching teams to find AI opportunities themselves, not just building tools for them.

Editor’s noteInternship building internal AI agents for product ops using vibe coding tools — you're the architect of the workflow and the team's AI translator.

Editor’s noteEnablement role building AI fluency across an ad-tech org — you launch training programs, launch an AI Guild, and own adoption metrics, not the platform.

Editor’s noteOperations role configuring and improving Mercury’s customer-facing chatbot and email agents — you monitor performance, expand bot scope, and optimize workflows rather than build the underlying platform.

Editor’s noteEntry-level AI ops seat watching dashboards and logs to catch AI failures before they escalate — you flag and coordinate, engineers do the fixing.

Editor’s noteAI adoption and capability-building seat — you identify AI opportunities across business functions, deploy tools with teams, and build the internal frameworks and playbooks for scaling adoption.

Editor’s noteEnablement-first AI role in legal tech consulting — you embed in client teams, build integrations and workflows, and drive adoption until AI actually sticks.

Editor’s noteHands-on AI builder seat in GTM ops — you ship AI-powered workflows and tools in days, not weeks, using agentic coding tools.

Editor’s noteRevenue systems lead role that builds and runs AI-powered automations with Clay, Zapier, and n8n — you're owning the GTM tech stack and its workflows, not just advising on it.

Editor’s noteApplied AI builder role shipping LLM features, evals, routing, and automation from business need to working prototype.

Editor’s noteCustomer-facing agent PM role owning prompt logic, agent design, rollout, and roadmap advice for enterprise deployments.

Editor’s noteInternal AI ops role building tools, prompt libraries, SOPs, and adoption loops across company functions.

Editor’s noteHealthcare QA role reviewing AI agent calls, catching errors, labeling issues, and improving real workflows.

Editor’s noteBuilds and runs AI automations with Claude, n8n, and similar tools, shipping practical workflow fixes fast.

Editor’s noteBuilds internal AI capability through champions, workflow-mapping workshops, and training for no-code agent platforms.

Editor’s noteAI product role taking agent features from concept to launch, with workflow tuning and interface design in the mix.

Editor’s noteOwns healthcare agent behavior from concept to rollout, shaping how agents reason across voice, chat, and text.

Editor’s noteEarly AI enablement role helping coworkers learn tools, prompts, and use cases across business functions.

Editor’s noteLeads the team turning legal AI onboarding into repeatable playbooks, adoption metrics, and customer change management.

Editor’s noteWizard is an AI-native shopping startup. This role is dedicated to 'Agentic AI Experiences', fitting the agentic UX requirement perfectly.

Editor’s noteWorkato is moving heavily into agentic automation. This Staff PM role specifically leads the developer tools for these AI-native apps.

Editor’s noteHigh-level leadership role focused on 'Agentic AI' within the graph database ecosystem, a key piece of modern RAG and agent orchestration.

Editor’s noteA 10-week intern role focused on low-technical AI application and testing, fitting the 'first-semester CS' depth requirement.