You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Early Window: Closes in
Company hidden

Senior Partner Deployed Engineer

  • Remote
  • 6+ years

Salary

$160,000 - 250,000/ year

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company is hiring a Senior Partner Deployed Engineer for its Customer Solutions team to grow its partner ecosystem across the AMER region.

The role is new at the company. It is modeled on forward deployed engineering roles that have spread across AI companies, but instead of working inside one customer, you work with strategic partners so they can understand, position, and deliver the company's platform to their whole customer base.

You combine field CTO, industry strategist, technical specialist, and partner relations work, and you are the technical authority for the AMER partner ecosystem. This is not a support role: one day you may discuss roadmap with a partner CTO and fix a Kubernetes deployment in a partner lab. You will build a new category through partners, with full autonomy at a fast-moving startup.

The company builds self-hosted, agent-ready workspaces for AI and human development workflows, aimed at enterprises that need security and governance.

Responsibilities

  • Act as the technical thought partner to AMER partner leaders, including practice leads, CTOs, and solutions architects at global integrators, regional cloud consultancies, and hyperscaler field teams. Own that relationship and set the direction for how the platform fits each partner's AI and modernization offerings.
  • Co-build sales plays for each partner based on its customers, verticals, and services. Write Working Backwards outcome proposals for strategic partner-customer pairings that turn AI development infrastructure into deal urgency.
  • Build and run workshops, Builder Labs, and partner-hosted enablement sessions to generate awareness and pipeline, including hands-on demo environments partners can use on their own.
  • Step into the highest-value partner-attached deals in AMER: co-sell calls, technical discovery, PoV scoping, architecture reviews, and technical win support. Stay with each engagement until the partner's team can run it alone.
  • Turn custom partner sessions into structured LMS modules and certification tiers that scale across the AMER partner base without live support for each new partner.
  • Write better-together reference architectures for strategic partner pairings across cloud providers and AI platforms, including deployment diagrams, network topology, IAM patterns, and runbooks that partner SAs can give directly to customers.
  • Turn each successful partner engagement into a repeatable play covering trigger conditions, discovery questions, positioning, demo script, PoV scope template, and expected outcomes. Maintain a playbook library that a new PDE or partner seller can run.
  • Build AI-powered self-service tools that remove repeated PDE work: an Opportunity Brief Generator, a PR/FAQ Generator, Workshop-in-a-Box deployment, and a demo site builder.
  • Publish a monthly AMER partner intelligence digest covering customer requests, competitor positioning, integration gaps, and emerging vertical use cases, and send it to Product, Engineering, and GTM leadership.
  • Own the AMER portions of the joint technical integration roadmap with strategic partners, setting priorities with Product and Engineering based on field signals.
  • Create partner relations content, the ecosystem version of developer relations: technical blog posts, cookbooks, partner conference talks, enablement videos, and workshop recaps that build the company's technical brand in the AMER partner community.
  • Help maintain cloud marketplace listings, competency documentation, and CSP co-build technical requirements for AMER partner and compliance needs.

Requirements

  • 7+ years of experience across forward deployed engineering, solutions architecture, field CTO, technical consulting, or developer relations at an infrastructure, developer tools, or AI company.
  • A record of helping partners or customers adopt products in new or undefined categories, not only running established playbooks.
  • Hands-on experience designing and deploying cloud infrastructure on AWS, Google Cloud, or Microsoft Azure, with production-level Kubernetes and Terraform depth. You can discuss the specifics of that work.
  • 2+ years deploying or running AI coding agents in production or near production. You understand agent loops, where credentials live, and the governance and audit expectations of AMER enterprises.
  • You can explain how workspace-local agent tooling differs from a centralized agentic harness, and why that difference matters to security, compliance, or data sovereignty stakeholders.
  • Experience with channel or technology partners in co-sell: hyperscaler partner programs, GSI or RSI partnerships, or VAR and distributor ecosystems in AMER.
  • Experience building technical go-to-market assets that outlasted your own delivery: sales plays, enablement curricula, reference architectures, or technical content programs.
  • Field CTO credibility: you can hold a technical vision conversation with a partner CTO and a deal-level architecture review with an SE on the same day.
  • Strong writing: you can produce a Working Backwards PR/FAQ, an architecture document, and a blog post, without needing separate people for each.
  • Self-directed and analytical, able to work with full autonomy. You define processes that do not exist yet, build tools no one has scoped, and build a function from scratch in a new region.
  • Bonus: prior forward deployed engineering experience at a platform company such as Palantir or Scale AI, a frontier AI lab, or a similar embedded deployment model.
  • Bonus: a public technical track record through blog posts, conference talks, open-source work, or developer and partner community engagement.
  • Bonus: operational experience with hyperscaler partner programs such as ISV Accelerate, strategic collaboration agreements, or co-sell programs.
  • Bonus: background in AI governance frameworks, session audit requirements, or SIEM integration for AI workloads.
  • Bonus: experience with LLM gateway or proxy infrastructure such as LiteLLM or OpenRouter in a multi-team or enterprise setting.
  • Bonus: experience designing human-in-the-loop breakpoints or escalation patterns for autonomous agent workflows.
  • Bonus: a Kubernetes certification (CKA, CKAD, or CKS).
  • Bonus: experience with Tailscale or similar overlay networking tools.
  • Bonus: open-source contributions, particularly in CNCF, MCP, or AI agent ecosystems.
  • Success looks like: you can take a partner CTO through how the platform runs parallel AI agents in a regulated AMER enterprise, covering credential isolation, audit lineage, GDPR-compliant data handling, and escalation design, then turn that discussion into a joint play partner sellers run next quarter.
  • Success looks like: you can enter an unstructured partner relationship, judge its technical and commercial potential, and map a route from first enablement session to first co-sourced deal without waiting for direction.

Conditions

Based in the United States, covering the AMER region.

The interview process aims to finish in 2 to 4 weeks, depending on schedules. You will meet individual contributors, managers, and senior leaders.

AI is not allowed during live conversational interviews. AI tools are allowed for take-home assessments if you note where and how much you used them. Honest use is not penalized.

Ashby and Brainerr help sort inbound applications by how well they match the role requirements, but they do not make hiring decisions. Granola takes notes during interview calls. Humans make all hiring decisions, and candidate data is not used to train AI models.

Under New York City Local Law 144, an independent bias audit was conducted on Ashby's automated employment decision tool, and the results are available from Ashby.

Questions about AI use in hiring or about the data collected can be sent to the careers team.

Equal opportunity employer.

Benefits

  • The company thanks people with tacos. Ask how that works.

Where you’d work

Fully remote

You can work from

  • United States

Your chances

Still hiring, not crowded yet, and you'd be among the first.

  • 17 checks run
  • 6 good signs
  • 0 red flags

Still hiring?

11 checks

Actively hiring

In its favour4

  • Still on the company's own careers site, checked 1 h agoModerate evidence
  • Found in the last 48 hours, before the big job boardsModerate evidence
  • Specific about the basics: pay, place, level, stack and contract all statedSlight evidence
1 moreFewer
  • States its salarySlight evidence

How crowded?

6 checks

Low

In its favour2

  • In its Early Window: not on the big job boards yetStrong evidence
  • Senior level: far fewer people qualifySlight evidence

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details11 facts · Role, Location, Compensation, Employment
Tech stack
  • AWS
  • Google Cloud
  • Kubernetes
  • Terraform
  • Azure
  • LLMs
Seniority
Senior
Type
Full-time
Specialty
Forward Deployed
Region
United States
Pay period
Annual
Show 5 more factsShow less

Role

Category
Solutions & Support
Specialty
Forward Deployed
Seniority
Senior
Experience
7+ years
Tech stack
  • AWS
  • Google Cloud
  • Kubernetes
  • Terraform
  • Azure
  • LLMs

Location

Work model
Remote
Region
United States
Remote from
  • United States

Compensation

Salary
$160,000 - 250,000 / year
Pay period
Annual

Employment

Type
Full-time

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason