Senior Forward Deployed AI Engineer

About the role

The posting lists New Jersey. Take the seat: do the operator's job for two to four weeks at the start of an engagement. Reach working fluency in a new domain (e.g., insurance underwriting, healthcare revenue cycle, asset flow) in weeks. Sit with the operator and the Forward Deployed Executive to redesign the function from first principles. Build and ship production GenAI systems into the customer's environment (LLM applications, agentic workflows, retrieval and structured-extraction pipelines, and surrounding services).

Key facts

What you'll do

• Take the seat: do the operator's job for two to four weeks at the start of an engagement.
• Reach working fluency in a new domain (e.g., insurance underwriting, healthcare revenue cycle, asset flow) in weeks.
• Sit with the operator and the Forward Deployed Executive to redesign the function from first principles.
• Build and ship production GenAI systems into the customer's environment (LLM applications, agentic workflows, retrieval and structured-extraction pipelines, and surrounding services).
• Build the evaluation harness before building the feature; define success metrics, instrument them, and let evals drive design.
• Write production code across the stack - backend services, data pipelines, and the AI layer.
• Take systems to production on AWS (GCP/Azure where required): containerized, observable, and maintainable after engagement.
• Start from the blueprint and feed the blueprint: convert field learnings into baseline for next engagements.
• Work in a pair with a Forward Deployed Executive who carries the Business Unit's KPIs; align outcomes to business metrics.
• Drive adoption; ensure systems are not routed around by changing management practices.
• Be credible with customer engineers, operators, and executives; willingness to disagree with all three.
• Shape scope and commitments before committing; own what will be built.

Requirements

• + years building software with substantial production code you were accountable for.
• Willing to spend weeks doing operator tasks (claims processing, underwriting, revenue-cycle) before writing code.
• Demonstrated ability to learn unfamiliar business domains fast enough to argue with practitioners.
• Shipped production GenAI/LLM systems (not demos or notebooks) and handled post-prototype hardness.
• Built or owned an eval suite for a non-deterministic system and can explain measurements.
• You need Strong engineering fundamentals; productive in unfamiliar codebases or languages.
• You need Python and/or TypeScript proficiency; depth matters more than stack.
• Cloud-native delivery on AWS (GCP/Azure a plus): containers, Kubernetes/ECS, IaC, CI/CD, operational reality of inherited systems.
• Credible with senior stakeholders; can hold redesign conversations with BU heads and scoping conversations with CTOs.
• You need Comfort with ambiguity and ownership; engagements start underspecified.
• Solid AI/ML foundations to reason about model failure modes, not just API calls.
• You need Strong hands-on production experience with Claude Code/Cowork.
• You need Fluent English written and spoken.

Nice to have

• Prior experience as founder, CTO, or engineering leader who returned to individual contribution.
• Real depth in financial services, insurance, healthcare, or asset management.
• It helps if Consulting, professional services, or embedded customer-facing delivery.
• Data platform depth: data lakes, warehouses, streaming/real-time analytics, data mesh, governance, data quality.
• It helps if MLOps and classical ML: PyTorch, SageMaker, MLflow.
• It helps if Fine-tuning, distillation, or inference/serving optimization.
• It helps if Graph databases (Neo4j, AWS Neptune).
• It helps if IaC depth: AWS CDK, CloudFormation, Terraform.
• It helps if Open-source contributions or public writing on applied AI.

Skills & tools

You will use GenAI. You will use LLM applications. You will use Agentic workflows. You will use Retrieval. You will use Evaluation. You will use Production engineering. You will use Python. You will use TypeScript. You will use AWS. You will use Cloud-native. You will use IaC. You will use CI/CD. You will use Claude Code. You will use Claude Cowork.

Relevant systems

The work touches Claude. The work touches AWS. The work touches GCP. The work touches Azure. The work touches Cowork Activation. The work touches Agentic SDLC. The work touches AI Blueprints. The work touches Submission Flow. The work touches Portfolio Lens. The work touches Asset Flow. The work touches Revenue Flow. The work touches Evidence Lens.