The job agent

Zack's fluency in directing LLM agents and automation pipelines maps well to Harvey's content-automation mandate, but the posting explicitly wants a hands-on engineer with 5+ years writing production integrations, which isn't how he works.

• 'Build and maintain AI agents using LLM APIs (Anthropic Claude, OpenAI)', Zack directs exactly this kind of agentic tooling, as with his job agent and Jarvis, though he specifies and judges rather than writing the implementation himself.
• '5+ years of automation engineering... designing and building API integrations' and 'Proficiency with HTML, CSS, JavaScript, React', this is a genuine gap; the role expects a coding engineer, and Zack does not write implementation code.
• 'Own and optimize the learning technology stack, including Skilljar and Sanity CMS', Zack has no stated experience with LMS/CMS platforms, another gap.
• 'translating business needs into well-architected technical solutions with minimal oversight', Zack operates autonomously across his projects, shipping AI-driven builds like Hoard and Vault Legacy from concept to release.

Zack's daily practice of judging and correcting AI output maps well onto evaluating model responses against policy, though this is individual-contributor annotation work rather than the directing-and-shipping role he actually operates in.

• The role centers on evaluating AI model responses within full conversation context and writing defensible rationales, Zack does exactly this kind of judging when he directs and reviews AI output across projects like Jarvis and his job agent.
• It rewards making precise distinctions and separating personal views from an imposed standard; Zack's habit of specifying tight acceptance criteria and rejecting near-misses fits directly.
• Genuine gap: the posting favors backgrounds in trust and safety, law, content moderation, or compliance, none of which Zack has, his experience is in directing AI to build and ship products, not policy classification.
• This is repetitive, feedback-heavy evaluation work with no building or leadership component, which is a poor match for how Zack prefers to operate as someone who ships products end to end.

Zack's work directing AI to build agentic systems, evals, and a job-search agent maps closely to this GTM Claudification role, but the posting's insistence on strong hands-on Python/TypeScript programming and 8+ years as a software engineer cuts against how he actually works.

• Meets 'production experience with LLMs, including agent development, MCP development, tool use, and evaluation frameworks', his job agent and Hoard involve directing agents, tool use, and judging outputs against evals
• Meets 'ability to navigate ambiguity and ship without a spec', he specifies, judges, and ships projects like Sakura Storm and Vault Legacy end to end
• Genuine gap: the role centers on 'strong programming skills in Python or TypeScript' and '8+ years as a software engineer' writing and operating production code, and Zack directs AI rather than writing implementation code himself
• Partial gap: no direct experience with go-to-market systems like CRM or sales engagement tooling, a preferred qualification here

Zack's strength in directing AI agents, prompt engineering, and shipping working solutions fits the orchestration side of this role, but GitLab explicitly wants someone who can write clean, maintainable production code independently, which is a real gap.

• The posting prizes 'prompt engineering as a core discipline: designing effective system prompts, managing context windows, evaluating output quality, iterating systematically', Zack does exactly this across his AI projects.
• It also demands 'competent, confident coding skills... deliver production-quality work independently' and REST/GraphQL integration by hand, Zack directs AI to produce code rather than writing implementation himself, a genuine mismatch.
• 'Diagnose business problems before building... map workflows, identify the true constraint, say this doesn't need AI' matches how Zack scopes and judges projects like his job agent.
• 'Deliver working prototypes in days, not months' aligns with his rapid shipping cadence on Sakura Storm and Hoard.

Zack's whole method is directing AI to build and ship games and judging its output, which maps neatly onto reviewing AI-generated game content, but the posting's core ask is hands-on GDScript and specific engines like Godot, which isn't how he works.

• Requires 'reviewing game builds for accuracy, performance, or design consistency' and evaluating AI-generated content, this is exactly what Zack does when he judges and ships AI-built projects like Sakura Storm.
• Wants 'at least 1 year of hands-on experience' with Godot/GDScript and 'scene management', Zack directs AI rather than writing GDScript himself, so this hands-on coding bar is a real gap.
• 'Create tool-related questions and review AI-generated responses' plays to his strength in specifying and critiquing AI output.
• Flexible, async, project-based contract work suits an independent operator who ships on his own terms.

Zack's AI-agent building and product-shipping instincts fit ElevenLabs' AI-first culture, but this is a customer-facing sales-engineering role that leans on hands-on Python and prior enterprise customer work he doesn't clearly have.

• 'Craft compelling technical demonstrations' and 'productize common integration patterns', Zack has shipped a string of AI products (Jarvis, the job agent, Hoard) and is strong at spotting patterns worth standardizing.
• 'AI first: we use AI to move faster', this is literally how Zack operates, directing AI to specify and ship rather than write code by hand.
• Gap: 'Proficiency in Python, inclusive of a deep understanding of software development', Zack directs and judges implementation rather than coding it himself, so hands-on Python fluency is a stretch.
• Gap: 'Experience working with customers', his projects are self-directed builds, not enterprise customer engagements or sales-cycle support.

Zack's instinct for AI-native, agentic pipelines fits Cursor's Voice-of-the-Customer vision, but this is a hands-on full-stack IC engineering role and he directs AI rather than owning code database-to-UI.

• 'Develop AI-powered systems that synthesize customer signal at scale' and 'agentic pipelines' map directly to how Zack ships, specifying and judging AI-built systems that separate noise from signal.
• 'Build intelligent bug intake and triage systems' echoes the autonomous triage-and-route logic behind his job agent, which sorts and prioritizes at scale.
• Gap: the posting asks for 'strong full-stack engineering skills, comfortable owning projects from database to UI,' and Zack does not write implementation code himself.
• Gap: 'deep product knowledge of Cursor and AI-assisted development workflows' is assumed here, and that specific tool fluency isn't something he's demonstrated in his projects.

Zack has deep hands-on experience directing AI agents, prompt engineering, RAG and evaluation, but this DevRel role explicitly demands personal coding credibility, a public content track record and speaking history he doesn't clearly have.

• 'Practical experience building and testing AI agents: LLMs, prompt engineering, agent frameworks, function calling, RAG', Zack meets this squarely; his job agent and other projects live in exactly this territory.
• 'Improve onboarding and first-build experience, sample apps, reference integrations', Zack routinely specs, judges and ships agent systems, which maps to demonstrating what good agent-building looks like.
• 'Strong technical credibility and hands-on coding ability... able to read and write real integration code', genuine gap: Zack directs AI to produce code rather than writing implementation himself, and this role centers on personal coding demos.
• 'A track record of developer content and public speaking at conferences/meetups', no evidence Zack has a portfolio of published tutorials, videos, or conference talks.

Zack's strength in directing AI agents, prompt engineering, and shipping end-to-end AI solutions maps well to the AI-first mandate, but this posting explicitly demands hands-on production coding, which is not how he works.

• The posting repeatedly stresses 'Competent, Confident Coding Skills' and delivering 'production-quality work independently', Zack directs and specifies AI rather than writing implementation code, a real gap for a Senior AI Engineer title.
• 'Prompt engineering as a core discipline: designing effective system prompts, managing context windows, evaluating output quality, iterating systematically', this is exactly how Zack operates across his projects.
• 'Own AI initiatives end-to-end, from discovery through deployment, delivering working prototypes in days' and 'diagnose business problems before building', matches his pattern of scoping, judging and shipping AI tools fast.
• Model selection and cost-performance trade-offs plus orchestration via APIs align with his agent-building work, though the role is framed as an individual hands-on engineer, not a director of AI.

Zack's strength directing AI agents from idea to shipped product maps well onto this Applied AI team's agentic and eval mandate, but the role wants a proven people-manager of engineers and scientists, which is not his track record.

• 'Experience taking AI products from 0 to 1' and 'agentic systems', met: Zack has shipped autonomous agents like his job agent and Jarvis, scoping hypotheses and deciding what to pursue or stop
• 'Drive evaluation and iteration practices... define the quality bar and build offline and online evaluation pipelines', met: he specifies and judges AI output quality as his core working mode
• 'A people-focused manager with experience leading and mentoring engineers', gap: Zack directs AI systems rather than managing a team of human engineers and applied scientists
• Hybrid NYC office culture and a formal EM I title with hiring/career-pathing duties, gap: his experience is shipping products by directing AI, not running a headcount-based engineering org

Zack has strong hands-on AI agent direction and LLM tooling fluency that map well to deploying ElevenAgents, but he lacks the enterprise customer-facing and commercial deal-structuring track record this role centers on.

• 'Technical aptitude and familiarity with common LLM, tooling and AI agent frameworks' plus 'creatively map enterprise use cases to AI systems', Zack meets this, having directed multiple shipped AI agent systems including a job agent and Jarvis.
• 'Own flagship deals end-to-end... structuring commercial terms including outcome-based pricing', this is a genuine gap; Zack has not run enterprise sales cycles or structured commercial deals.
• '3+ years working with customers in a technical capacity, direct enterprise customer experience preferred', Zack's work is project- and product-focused rather than embedded enterprise customer delivery, so this is only partially met.
• 'Build and deliver compelling demos of ElevenAgents', strongly aligned, as Zack routinely specifies, judges and ships voice- and agent-driven prototypes.

Zack's model of directing AI rather than writing code lines up neatly with a role that explicitly says you don't need to write production code, but he lacks the 6+ years of solutions architecture or engagement-management experience and the C-suite consulting track record this seat is built around.

• The posting wants someone who understands agentic coding and LLMs 'well enough to hold your own with senior eng' without writing production code, this matches how Zack works, specifying and judging AI output across projects like Jarvis and his job agent.
• It requires being 'comfortable hands-on with Cursor workflows, integrations, and platform config' and able to read Python/JS-TS to partner with an FDE, Zack reads and directs code across his projects, so he can hold the configuration layer.
• Gap: the role asks for 6+ years in Solutions Architecture, deployment strategy, or an Engagement Manager seat owning enterprise scoping and delivery, plus executive presence in the boardroom, Zack's shipped projects are self-directed, not enterprise consulting engagements with C-suite sponsors.
• Gap: domain depth in FSI, insurance, telecom, healthcare, or semiconductor is called out as a strong plus, and Zack has no stated background in those verticals.

Zack lives AI-native development daily and has real conviction about how AI reshapes software, but this is a post-sale enterprise customer-facing role built on prior Solution Architect/FDE experience and hands-on CI/CD debugging that he hasn't done in a commercial setting.

• 'Passion for developer tooling and strong conviction around how AI will reshape software engineering', Zack genuinely embodies this, having shipped multiple products entirely by directing AI rather than writing code
• 'Strong understanding of developer workflows, SDLC tooling, integrations, CI/CD', he understands AI-assisted build workflows from directing them, but has translated that into personal projects, not enterprise platform environments
• Gap: the role wants experience in customer-facing roles (Solution Architect, SE, FDE, TAM) inside strategic enterprise accounts, and Zack has no record of embedded enterprise deployment or executive stakeholder management
• Gap: it is explicitly 'highly hands-on', configuring environments and debugging CI directly with developers, which cuts against how Zack operates, since he specifies and judges AI output rather than doing implementation himself

Zack has deep hands-on fluency with AI tooling and adoption, but this is an early-mid-level, execution-focused ops coordination role that undersells his experience directing AI to ship real products.

• 'Interest in AI Tooling' and acting as an AI adoption advocate: Zack genuinely fits, he directs AI daily across multiple projects and can speak credibly to how tools are configured and used.
• 'Utilization & Tracking' plus 'AI Data Management': Zack has built data-driven agentic systems (the job agent, Hoard) so tracking adoption and maintaining dataset hygiene is well within reach.
• Gap: the role explicitly wants 'some experience in enablement, sales/business operations, or IT operations' and process-following rather than strategy-building, Zack's background is product direction, not sales/IT ops coordination.
• Gap: this is a detail-oriented intake/access-request administration role, which is narrower and more junior than the AI product work Zack typically drives.

Zack's strength in turning vague intent into crisp specs and directing AI to ship fits the requirements-writing core of this role, but he has no formal business-analysis track record or finance/operations domain background.

• 'Translate business needs into delivery-ready artifacts: user stories, acceptance criteria', Zack does exactly this kind of specification and judging work when directing AI across his projects, so this maps well.
• 'Use AI tools responsibly to accelerate analysis and documentation', this is squarely how Zack operates, using AI for drafting, comparison and gap analysis while judging accuracy.
• 'A track record of leading business analysis or requirements work on real software delivery projects', Zack's experience is self-directed AI builds, not stakeholder-facing BA engagements at an enterprise, a genuine gap.
• 'Experience in operations, finance, accounting, or control-oriented domains' plus on-site NYC consulting for an investment manager, Zack has neither the finance domain nor a client-facing consulting history.

Zack has genuine depth in agentic system design, orchestration, and evaluation, but this Staff Forward Deployed Engineer role is explicitly hands-on production coding at a level he directs rather than personally writes.

• 'Contribute production-quality changes' and 'Strong programming skills in Python, TypeScript, Go...', Zack directs AI to produce code and judges output rather than writing implementation himself, so this is a real gap against a role built on personally shipping code.
• 'Design and build agentic systems using models, tools, action loops, orchestration, context, retrieval, state, memory, evaluation, tracing, and human oversight', Zack meets the systems-design and evaluation dimension through his agent work.
• 'Understanding of why AI systems become unreliable, fail to achieve adoption, or consume significant resources without producing useful outcomes', Zack has practical experience specifying, judging and iterating on agent behavior to reach reliable outcomes.
• 'Staff-level software-engineering experience building, shipping, and improving complex production systems', GitLab frames this as a traditional SWE career track, which does not match how Zack operates.

Zack's strength in directing and critiquing AI output maps to the role's bonus criteria, but Datadog wants a hands-on support/solutions engineer with observability depth that his AI-orchestration background doesn't cover.

• The posting requires 3+ years in a technical support, solutions architecture, or software development role acting as primary technical contact, Zack directs AI and ships products but hasn't held a partner-facing support engineering position.
• It expects deep observability fundamentals (Metrics, Logs, Traces, OpenTelemetry) and OAuth/log-pipeline consulting, a clear domain gap for him.
• The bonus asks for someone who validates, critiques, and refines AI-generated output and pushes AI into software workflows, this is squarely how Zack operates.
• Deep-dive code reviews against a Quality Rubric require judging code quality, which he does when shipping via AI, though he does not write the implementation himself.

Zack's habit of judging and shipping AI output maps onto the evaluation and mitigation side of this role, but he lacks the trust-and-safety, content operations, and policy-enforcement background the posting treats as the core qualification.

• Posting wants 'experience in trust and safety, content operations, policy enforcement, or a related operational role', Zack has no formal T&S or content-moderation operations history, a genuine gap.
• 'Think strategically about eval quality to build processes and eval paradigms that keep evaluations unsaturated, high-signal', Zack does exactly this kind of judging and quality-gating when he directs and ships AI systems like Jarvis and the job agent.
• 'Adopting internal tools and AI-assisted workflows (e.g., Claude Code) to accelerate your work', Zack routinely directs AI-assisted workflows rather than writing code, which fits the expectation for a non-implementer here.
• 'Building processes, workflows, or programs from scratch (zero-to-one work)', Zack has taken projects like Vault Legacy and Hoard from concept to shipped, showing the zero-to-one instinct, though not in an enforcement setting.

Zack's strength in RAG, evaluation workflows, and agentic systems maps to Snorkel's Applied AI work, but this role demands hands-on Python software engineering and 3+ years of customer-facing enterprise delivery that he doesn't have.

• 'Develop and implement state of the art AI systems such as RAG, fine-tuning pipelines, prompt engineering and agentic workflows', Zack has directed exactly this through Jarvis and his job agent, with a genuine data- and evaluation-first mindset.
• 'Proficiency in Python, strong grounding in software engineering fundamentals (pydantic, mypy, pytest, poetry, FastAPI, Ray, Airflow)', this is a hands-on implementation bar Zack does not meet, since he specifies and directs AI rather than writing production code.
• '3+ years of customer-facing experience in the design and implementation of AI/ML solutions' plus executive presentation and enablement workshops, Zack has not held a customer-facing enterprise delivery role of this scope.
• 'Create augmented real-world datasets and comprehensive evaluation workflows to ensure model reliability', Zack's evaluation-driven approach to shipping Vault Legacy and Sakura Storm aligns well here.

Zack ships GenAI applications end-to-end by directing AI, but this role is explicitly a hands-on coding position demanding 5-8 years of software engineering and personal Python/LangGraph/SQL implementation, which is not how he works.

• 'Designing and deploying GenAI applications into production', met: Zack has specified, judged and shipped LLM-driven products like Sakura Storm and a working job-application agent.
• 'Act as a trusted technical advisor to customers, translate technical complexity to customer-facing narratives', met: he is strong at scoping, specifying and communicating AI system design.
• 'Hands-on engineering role... write clean, maintainable code' and 'proven expertise in Python, Langchain, LangGraph, SQL', genuine gap: Zack directs AI to produce implementation rather than writing production code himself.
• '5 to 8+ years in software engineering, deep experience with APIs, microservices, event-driven systems', partial gap: his depth is in directing and shipping AI systems, not a traditional coding engineering resume.

Zack has the technical depth and demo instincts to speak credibly about observability and cloud architectures, but he has no pre-sales or customer-facing sales-engineering track record, which is the core of this role.

• Requires ~1.5+ years as a Sales Engineer or comparable customer-facing technical role, Zack has no formal pre-sales experience, a real gap.
• Requires strong understanding of cloud infrastructure, observability, and DevOps, Zack works fluently across these domains directing AI builds like Vault Legacy and his job agent.
• Requires independently leading technical presentations, demos, and POCs, Zack is strong at articulating value and judging technical tradeoffs, though he hasn't done it in a quota-carrying sales cycle.
• Requires translating technical capabilities into business outcomes, a natural fit for how Zack specifies and ships, but untested in front of paying customers.

Zack ships AI-built production systems and excels at end-to-end technical delivery, but this FDE role explicitly demands a hands-on contributor writing production code directly in customer codebases, which is not how he works.

• 'Write and ship production code (Python, TypeScript, Node) directly in customer codebases... as a hands-on contributor', Zack directs AI to build and ships systems, but he does not personally write implementation code, a core and repeated requirement here.
• 'Demonstrated experience running end-to-end technical engagements from POC workshops through to production deployment', Zack meets this: he has scoped, specified, judged and shipped multiple production systems end-to-end.
• 'Strong communication skills and executive presence' and building reusable reference implementations and demos, aligns well with how Zack specifies architectures and ships demonstrable products.
• Gap: the '5+ years hands-on software engineering, shipping production code not just prototypes' bar assumes a traditional developer, and Zack's value is in directing AI rather than being the coding hands on keyboard.

Zack's product-first, experimentation-driven approach to shipping AI-assisted experiences overlaps with the onboarding mandate, but he lacks the 2+ years of formal people-management over full-stack engineering teams this role centers on.

• Requires 'Create AI-assisted setup options to make sure initial setup just works' - Zack genuinely fits, having directed AI to ship products like Jarvis and his job agent end to end.
• 'Passionate about experimentation and using data to drive decisions' and shipping features quickly - matches how Zack specs, judges and iterates rapidly.
• 'At least 2 years of people management experience' and 'managing full stack development teams' - a real gap; Zack directs AI agents to build, not human engineering teams, and holds no formal EM track record.
• Hybrid NYC office culture requirement may not fit Zack's AI-directed, solo-ship working style.

Zack genuinely uses AI coding tools as core infrastructure and has strong opinions about AI-assisted development, but he has no post-sales, customer-facing, or hackathon-facilitation track record, which is the core of this role.

• 'You use Cursor or comparable AI coding tools in your own workflow and have genuine opinions about what good AI-assisted development looks like', Zack meets this squarely, directing AI across Sakura Storm, Vault Legacy, and his job agent.
• 'Be a credible technical presence in the room with developers: you can follow a codebase, troubleshoot in real time', he can follow and direct at a working level, though he doesn't write implementation code himself.
• 'Experience running developer events, hackathons, or technical workshops with adoption outcomes', genuine gap; Zack has shipped products, not run customer events.
• 'Worked in a post-sales or customer success context', no evidence of this in his background, and it's central here.

Zack has shipped React and TypeScript products by directing AI, but this is a hands-on IC coding role at a specific experience band that doesn't match how he actually works.

• 'Own the implementation of small-to-medium features from design through deployment', the role centers on writing production code personally, which is not how Zack operates; he specifies and directs AI rather than implementing.
• 'Solid TypeScript and React Native experience', Zack has shipped TypeScript/React web products like his job agent and Vault Legacy, but mobile-specific React Native is a genuine gap.
• '2 to 3 years of professional software engineering experience delivering features within a software team', Zack ships products end to end but the on-call rotation and team-IC framing here fits a traditional coder more than a director-of-AI approach.
• 'Participate in design discussions on component architecture, state management, and UI patterns', this is a real strength; Zack makes exactly these architectural judgment calls when shipping.

Zack directs AI to ship products and games and fits ElevenLabs' AI-first culture, but he lacks the creative-agency production portfolio and enterprise consulting track record this Creative Director role centers on.

• The posting demands 'significant experience in a creative production, creative technology, or creative direction role at an agency, studio, or production house', Zack has shipped products by directing AI but not from a formal creative-agency or studio background.
• It requires 'hands-on fluency with AI creative tools... you actively use generative AI for image, video, audio, or text production', Zack genuinely lives in AI tools daily, directing and judging output across projects like Sakura Storm and Jarvis, which maps well.
• It wants 'experience working directly with enterprise clients or large brand teams in a consulting, solutions, or embedded capacity', this is a real gap, as Zack's work has been on his own products rather than embedded with enterprise creative teams.
• The role is explicitly 'hands-on, in the tools alongside customers' building reference content, Zack works by specifying and directing AI rather than producing polished creative assets himself, which is a mismatch with the portfolio expectation.

Zack has genuine depth in agent engineering, evals, and multi-agent orchestration, but this role is half heavy infrastructure (Kubernetes, Terraform, HA/DR) and demands 7+ years hands-on customer-facing solutions architecture, which he lacks.

• 'Strong experience with LLM frameworks (LangChain, LangGraph) for building agent-based applications' and 'evaluation frameworks / prompt optimization', Zack meets this well, having directed multi-agent systems like Jarvis and a job agent with eval and prompt-tuning cycles.
• 'Strong Kubernetes experience (GKE/EKS/AKS), Terraform, Helm, multi-region HA/DR', genuine gap; Zack has not architected production cloud infrastructure at this depth.
• '7+ years in technical, hands-on customer-facing roles such as Solutions Architect or Forward Deployed Engineer', Zack directs and ships AI-built systems rather than serving as an enterprise-facing SA, so this is a real mismatch.
• 'Vector stores, RAG patterns, tool integration, error handling', Zack meets this through work like Hoard and the job agent, specifying retrieval and tool-calling behavior.

Zack has deep hands-on experience directing AI agents and building conversational systems, but he lacks the 4-6 years of customer-facing pre-sales engineering background this role centers on.

• Requires 4-6 years in a sales engineering (pre-sales) role partnering with AEs, Zack has no formal pre-sales or customer-facing sales engineering track record, a genuine gap.
• 'Create and architect generative AI experiences' and 'develop custom demonstrations', Zack directs and ships AI agents (his job agent, Jarvis), which maps well to building tailored demos.
• 'Communicate complex technical concepts clearly to C-level and engineering stakeholders', Zack can specify and judge AI systems credibly, but has not done this in an enterprise sales context.
• Note: role is described as in-office elsewhere despite the remote title, and 'functional understanding of GTM systems' is not a proven strength for him.

Zack directs AI builds and ships working products, but this role centers on enterprise customer deployments and project management that his background doesn't clearly show.

• The posting wants experience 'leading technical or AI-driven SaaS implementations' with enterprise customers like United and Marriott, Zack ships AI projects but has no evidenced record of customer-facing enterprise deployments
• 'Comfort working with technical concepts, data, and analytics' and translating complex AI into clear plans, Zack genuinely does this, specifying and judging AI systems like Jarvis and his job agent
• 'Strong project management skills paired with a consultative, customer-first mindset', this is a real gap, as Zack's work is self-directed building rather than managing external stakeholder deployments
• The role is explicitly 'hands-on' and customer-facing at scale, which is a different mode than Zack's direct-and-ship approach to his own projects

Zack ships games and is fluent at judging AI output, but this role wants 1+ year of genuine hands-on pixel art and sprite work in LibreSprite, Defold, or Solar2D, which isn't his toolset.

• Requires 'at least 1 year of hands-on experience with LibreSprite, Defold, and/or Solar2D' plus sprite creation and pixel art, a real gap, since Zack directs AI to produce game assets rather than crafting pixel art in those specific tools
• 'Review AI-generated responses for accuracy and relevance' and 'reviewing game art for quality, accuracy, or stylistic consistency' fits his core strength of specifying, judging and shipping
• 'Creating game assets following style guides or project briefs' aligns with how he ran Sakura Storm, but that was AI-directed rather than manual asset design in the named tools
• Flexible, async, contractor structure suits how he already works across multiple projects

Zack has genuine depth in designing and directing AI agent systems, but this is a customer-facing enterprise pre-sales role where his lack of quota-carrying, workshop-facilitation, and C-suite selling experience is a fundamental mismatch.

• '5+ years in a customer-facing technical role, with 1-3 years in pre-sales selling to large enterprises', Zack has no enterprise pre-sales or quota-carrying sales background, a hard gap.
• 'Hands-on experience designing, building, or selling AI Agents or agentic AI systems, agent frameworks, orchestration patterns, LLM-based architectures', Zack meets this through directing agentic projects like Jarvis and his autonomous job agent.
• 'Natural workshop facilitator... equally comfortable whiteboarding with a prospect's engineering team and presenting to a C-suite audience', no evidence Zack has done customer-facing facilitation or executive selling.
• 'Practical understanding of APIs, integration patterns, and how enterprise systems connect to AI Agent workflows', Zack meets this from specifying and shipping integrated agent systems like Hoard and Vault Legacy.

Zack has genuine analytical and pattern-recognition instincts from directing AI systems, but this role centers on daily fantasy sports domain expertise and hands-on analyst work he doesn't have.

• 'Extensive knowledge and experience in sports gaming, player prop and DFS industries' is a hard requirement Zack does not meet, his background is AI-directed product building, not DFS trading.
• 'Strong pattern recognition and ability to react to observed trends' and identifying coordinated member patterns (multi-accounting, sharp discords) aligns well with the fraud/anomaly logic he specified for his job agent and Hoard.
• 'Partner with Analytics to develop models, algorithms, benchmarking' fits how he directs and judges AI-built analytical tools, though the role wants an operator running the analyses, not a director.
• SQL/R/Python is 'preferred, not required', Zack directs AI to produce and evaluate such analysis rather than writing it himself, which is a partial fit.

Zack has deep AI-product fluency with LLMs, agents and APIs, but this is a front-line enterprise support contract role built around 2-3 years of ticket-owning SaaS support experience he doesn't have.

• Requires 2-3 years in technical customer support at a SaaS company with B2B/enterprise experience, Zack's background is directing AI to build and ship products, not staffing a support queue
• Wants familiarity with LLMs, AI agents and API integration, genuinely met, as he specs and orchestrates AI systems across multiple projects
• States comfort 'reading and troubleshooting code, especially Python or JavaScript' and 'building things yourself', partial gap, since Zack directs and judges AI-written code rather than writing or debugging implementation himself
• The core deliverable is diagnosing and resolving enterprise tickets end-to-end, which is outside the shape of his hands-off, ship-oriented work

Zack's AI-orchestrated builds and interest in recruiting tooling align thematically, but this is a hands-on full-stack coding role demanding personal proficiency in React and Python that his direct-and-ship approach doesn't match.

• 'Own the full product development lifecycle for new people products end-to-end', Zack has shipped 0-1 products by directing AI, so the end-to-end ownership and fast iteration fit genuinely.
• 'AI-powered automations and scalable recruiting tools', his job agent that automates candidate/role matching is a direct domain match.
• 'Proficiency with JavaScript, React, and a backend language (Python)' plus '4+ years professional engineering experience', real gap: Zack directs AI to produce code rather than writing it himself, and lacks the professional hands-on engineering track this role screens for.
• 'Interest in building company culture and/or recruiting', a plausible fit but not a demonstrated focus in his projects.

Zack's fluency in directing AI-native systems and shipping demos fits Decagon's platform, but he lacks the 4-6 years of customer-facing pre-sales and GTM sales-engineering track record this role centers on.

• Requires 4-6 years in a customer-facing sales engineering (pre-sales) role partnering with Account Executives, Zack has no pre-sales or quota-carrying background, a genuine gap.
• 'Create and architect generative AI experiences for customers' and 'develop custom demonstrations', Zack has directed multiple AI agents to build shippable products like the job agent and Jarvis, which maps well to rapid tailored demos.
• Communicating complex technical concepts to C-level and engineering stakeholders, Zack can articulate AI system design clearly, but has not done so in an enterprise sales context.
• 'Functional understanding of GTM systems and workflows', this is not an area Zack has demonstrable depth in.

Zack has genuine AI-agent depth and can make complex AI accessible, but this is a principal enterprise pre-sales role demanding 1-3 years of customer-facing selling to large enterprises that he simply doesn't have.

• Requires 'Hands-on experience designing, building, or selling AI Agents or agentic AI systems, including agent frameworks and orchestration patterns', Zack meets the design/direction side, having specified and shipped an agentic job agent and LLM-driven systems, though he directs rather than codes them.
• Requires '5+ years customer-facing technical role, with 1-3 years in pre-sales selling to large enterprises', this is a real gap; Zack builds and ships products, not runs enterprise sales cycles or high-stakes prospect demos.
• Values 'natural workshop facilitator, equally comfortable whiteboarding with engineering and presenting to C-suite' and 'ROI models for economic buyers', Zack can translate technical depth to business value but lacks the enterprise pre-sales track record this principal role centers on.
• 'Ability to write Python for prototyping is a plus', Zack does not write implementation code himself, so demo customization would rely on his AI-direction approach rather than hands-on scripting.

Zack has genuine conversational-AI fluency from directing his own agent projects, but he lacks the enterprise pre-sales and CCaaS sales-cycle background this role is built around.

• Requires 4+ years customer-facing with 1-3 in technical pre-sales supporting large enterprise sales cycles, Zack has no formal pre-sales or quota-carrying sales experience, a real gap.
• Wants deep hands-on expertise with Conversational AI platforms and demoing value, Zack does understand conversational AI deeply, having directed the Jarvis assistant and a job-application agent end to end.
• Values simplifying complexity and captivating demos for customers, Zack's habit of shipping working AI-directed prototypes gives him credible material to demo, though not in a contact-center context.
• Requires Salesforce, contact center infrastructure, and enterprise SaaS familiarity, Zack has not worked in CCaaS or enterprise SaaS environments.

Zack's AI-directed workflow matches Twilio's emphasis on prompting and evaluating AI-generated code, but this is a hands-on L2 Java engineering role built on JVM distributed-systems fundamentals he doesn't personally code.

• Required: 'Minimum 2-3+ years of hands-on experience in a large scale, distributed applications environment on JVM based technologies' and 'Strong Java fundamentals', Zack directs AI rather than writing production Java, so this core requirement is a genuine gap.
• Required: 'Demonstrated proficiency working with AI coding assistants (Claude, GitHub Copilot, Cursor)... describe your workflows and show examples', this squarely fits how Zack has shipped projects like Sakura Storm and his job agent.
• Required: 'Proven ability to critically evaluate AI-generated code for correctness, security, performance' and 'Excellent written communication skills essential for effective AI prompting', these judgment-and-spec strengths are exactly where he operates.
• Required: on-call rotations, Kafka/SQS event-driven architecture, and AWS/GCP infrastructure depth, Zack lacks demonstrated experience operating this kind of real-time low-latency production platform.

Zack understands how to deploy generative AI solutions but lacks the enterprise contact-center, telephony, and formal pre-sales solutions-architecture background this role centers on.

• The role wants deep Customer Experience and contact-center infrastructure expertise (AWS Connect, Genesys, Five9), Zack has no telephony or CX platform experience, a genuine gap.
• It requires 'deep understanding of how enterprises leverage Generative AI solutions', Zack genuinely fits here, having directed AI to ship real products end-to-end.
• It expects extensive large-scale enterprise software implementation and stakeholder management from pre-sales to post-sales, Zack has shipped his own AI projects but not managed enterprise account delivery.
• Strong expertise in AI/ML, cloud, and data systems is valued, and Zack's practice of specifying and judging AI output across projects like the job agent partially maps, though not at enterprise integration scale.

Zack's AI-first delivery instincts fit Cresta's conversational-AI mission, but this Customer Engineer role is fundamentally a hands-on implementation seat demanding personal Go/Python/JavaScript coding and contact-center domain depth he doesn't have.

• Requires 'hands on experience in Go, Python and Javascript' to design, build and deploy applications with Cresta SDKs, Zack directs AI and specifies systems rather than writing implementation code himself, a real gap.
• Wants contact-center experience with AWS Connect, Genesys, Five9 and CX platforms, Zack has no demonstrated background in call-center infrastructure.
• Values consultative, customer-facing problem solving and shipping working AI solutions, Zack does ship AI-directed products end to end (a job-application agent, Jarvis) which partially aligns with the delivery and API-integration side.
• The 'think big, deliver simple' and APIs/SDKs value-add framing matches how Zack scopes and judges AI-built tools.