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

Zack has genuine technical range and product judgment, but this is a pre-sales role built around customer demos, systems administration background, and DevOps monitoring tools that aren't where he's spent his time.

• Requires delivering technical presentations and demos to external customers and running POCs, Zack's work is directing AI to build and ship products, not customer-facing pre-sales, so this is a real gap
• Wants prior systems administration (Windows/Linux) and DevOps monitoring/architecture tool experience, not demonstrated in his project record
• Does bring credible technical fluency across full product builds (Sakura Storm, Vault Legacy) that could translate to articulating technical value
• Comfortable thinking creatively across a wide variety of technical challenges, which matches how he scopes and judges his projects

Zack ships products by directing AI rather than writing code, which clashes with this role's explicit requirement for 4+ years of hands-on Golang/Java development.

• The posting demands '4+ years of hands-on software development' and strong command of Golang/Java, Zack directs AI and does not write implementation code, so this is a genuine gap.
• 'Comfortable refining loose requirements into a clear technical spec' fits Zack well; he routinely turns vague ideas into shippable specs on projects like Sakura Storm and Vault Legacy.
• REST API design, PostgreSQL/NoSQL and Websocket experience are core here, and Zack judges and ships such systems through AI rather than personally engineering them at the depth a small IC team expects.
• The A/B testing and personalization/recommendation work maps to his product instincts, but Kalshi wants an individual contributor writing high-performance backend services daily.

Kalshi wants a hands-on React/TypeScript engineer with 5+ years writing and maintaining frontend code, which is squarely an implementation IC role rather than Zack's direct-the-AI, specify-and-ship approach.

• 'Writing and maintaining frontend code to drive the product features' and '5+ years of React experience' expect a hands-on coder, Zack directs AI to produce code rather than writing implementation himself, so this core requirement is a real gap.
• 'Conceive entire features before developing' and 'weighing customer feedback, business needs, and long-term goals to make product decisions' fit how Zack works, he specifies, judges, and ships whole products end to end.
• 'Attention to detail and good UI/UX intuition' aligns with the polished consumer products he has shipped like Sakura Storm and Vault Legacy.
• The role sits inside a small, ownership-heavy 'SWAT team' with green field to chart, which matches his self-directed way of building, but the title and evaluation are framed around coding output he doesn't personally produce.

Zack's instinct for turning fuzzy capability claims into defensible metrics matches the eval-design spirit here, but this is a hands-on Research Engineer role demanding strong personal Python and distributed-systems implementation, which is not how he works.

• 'Design and run new evaluations... produce visualizations that make results legible', Zack has genuinely done evaluation-style work by specifying and judging AI output across projects like Jarvis and his job agent, so the conceptual half fits
• 'Strong Python programming skills, including production or research infrastructure', this is a real gap; Zack directs and specifies rather than writing production code himself
• 'Build and harden the distributed eval execution platform... reliably at scale' plus on-call production support, this expects an individual contributor shipping infrastructure code, not an AI-directing role
• 'Clear written and verbal communication, especially explaining technical results to non-specialists', this Zack meets well, as making AI systems legible and defensible is central to how he ships

Zack's instinct for judging AI-generated output fits the actual task, but the posting demands 3+ years of hands-on Godot and GDScript work he doesn't have.

• Requires '3+ years of hands-on experience with Godot' plus working knowledge of GDScript and scene management, Zack directs AI rather than writing engine code, so this is a real gap
• The core work is 'review AI-generated responses for accuracy and relevance' and crafting tool questions, which matches how Zack specifies and evaluates AI output on projects like Sakura Storm
• 'Strong written communication skills and attention to detail' and independent, guideline-driven work suit how he operates
• Godot-specific game engine depth is not something in his shipped project history, which centers on AI agents like Jarvis and the job agent rather than 2D/3D engine workflows

Zack has genuine technical range across cloud and modern web tooling from his AI-directed projects, but this is a pre-sales role gated on prior technical sales experience he does not have.

• 'At least one year of experience in a technical sales and/or post-sales role', Zack has no sales or post-sales background; his work is building and shipping products by directing AI.
• 'Working knowledge of modern web development, DevOps monitoring, and cloud architecture', he genuinely meets this through projects like Vault Legacy and his job agent that he specced and shipped on cloud stacks.
• 'Comfortable delivering technical presentations/demos', plausible given how he articulates and judges technical work, but he has no documented client-facing demo track record.
• Requires in-person hybrid presence at the Boston office and up to 15% travel, a hard logistical constraint rather than a skills gap.

Zack is a technical builder-director rather than a pre-sales professional, and this role hinges on DevOps monitoring expertise and customer-facing sales demos he has no track record in.

• The posting wants someone knowledgeable with DevOps monitoring/architecture tools and prior Windows/Linux systems administration, Zack directs AI to build products and has no observability or sysadmin background to point to.
• It requires confident technical presentations and demos to external customers throughout a pre-sales cycle; Zack ships and judges products but has no documented sales-engineering or customer-facing pre-sales experience.
• One genuine overlap: 'think creatively about a wide variety of technical challenges' and rapidly learning new technology fits how he scoped and shipped Sakura Storm, Vault Legacy and his job agent, but that transferable curiosity doesn't cover the domain-specific and sales requirements.
• Travel up to 25% and Denver hybrid presence are hard logistical requirements that add further distance from his profile.

Zack's instinct for viral consumer product and rapid experimentation fits Kalshi's growth ambitions, but this is an explicitly hands-on React/TypeScript coding role that clashes with how he actually works, directing AI rather than writing implementation himself.

• Requires '3+ years of industry experience with strong programming skills' across the full stack with emphasis on React + Typescript, Zack specifies and judges rather than writing production front-end code, a real gap for a role described as 'hardcore and hands-on'
• 'Track-record of building viral applications and a knack for creating moments of delight', Zack has shipped consumer-facing polished products like Sakura Storm with a strong sense for delight and stickiness
• 'Build 0-1: Many of the things you will build do not exist yet' plus 'Rapidly ship experiments', Zack's whole method is fast 0-to-1 shipping by directing AI, from Jarvis to his job agent
• Data-driven with 'experience running A/B tests with experimentation platforms', not something Zack has demonstrated depth in

Zack ships games by directing AI rather than doing hands-on pixel art or sprite work in Defold or Cocos2d-x, so he misses this role's core artist requirement even though the review-and-feedback side suits him.

• Requires 1+ year hands-on experience with engines like Defold, Solar2D, MonoGame, libGDX, or Cocos2d-x, Zack does not do implementation or work in these tools, a real gap.
• Wants hands-on pixel art, sprite creation, and 2D asset design experience, Zack directs art generation for games rather than drawing sprites himself, so this is a partial miss.
• The task of reviewing AI-generated content for accuracy and stylistic consistency against briefs genuinely matches how Zack specifies and judges AI output.
• Strong written communication and following written style guides fit his direction-and-spec workflow.

Zack's strength in directing AI to build lightweight automations partly fits the AI-workflow angle, but this is fundamentally a junior sales operations role requiring GTM/RevOps experience he does not have.

• Requires 1-3 years in GTM, Revenue, or Sales Operations at a SaaS company, Zack has no sales operations or CRM/Salesforce background.
• 'Familiarity with AI/LLM tools, prompt engineering, workflow automation, or lightweight tool prototyping' is a bonus he genuinely covers, having directed AI to ship working agents.
• Core duties like account distribution, Salesforce hygiene, Rules of Engagement conflicts, and quarterly business reviews sit far outside his experience.
• The role centers on Excel/Google Sheets analysis and field-facing sales support, not the AI product direction Zack actually does.