Head of Solutions Engineer

About Notch

Notch is the AI engine for enterprises running complex, high-stakes operations. We deploy purpose-built agents that resolve real workflows end to end — across insurance and financial services — with governance, auditability, and traceability built into every layer.

We were built inside regulated operations, not by a software company that decided to enter insurance. Our platform connects customer and employee interactions to back-office systems and automates complex workflows end to end, as the standard regulators actually require.

Backed by top-tier VCs, Notch has raised $45 million to date, including a $30 million Series A in March 2026 led by Headline, with participation from Lightspeed, Jibe Ventures, Illuminate Financial, Munich RE, and Phoenix.

About the role:

Our delivery org is scaling fast. Customers are getting larger and more global, and the number and complexity of delivery projects is growing with them.

We're hiring a Solutions Engineer Manager to lead the engineers who build the two-way integrations connecting Notch's agents to our customers' enterprise systems — and to turn that work from a series of custom projects into a repeatable engine.

Where you own and where you partner. Technical Project Managers own the project plan and the customer-facing schedule. You own the execution: the estimates your team commits to, the quality of what ships, and the health of what runs in production. When a date is at risk, the TPM manages the customer conversation; you own the engineering path back to green.

How the team grows. You'll lead and hire a team of 4–8 Solutions Engineers. Within your first year we expect the charter to broaden into DevOps and product-adjacent engineering, and we expect you to define that team and hire it. If you want to build an org rather than inherit one, this is the job.

This is a Tel Aviv–based role, with travel to our US office and to global customers.

What you'll own:

The team

• Hire, coach, and grow the Solutions Engineering team — then expand it into DevOps and dev hires as the charter widens

• Run the day-to-day: capacity allocation across concurrent projects, escalation triage, on-call rotation, 1:1s, and growth plans

• Raise the skill ceiling of every engineer who reports to you

Execution

• Stand behind your team's estimates — and hit them

• Own the quality of shipped integrations and the health of production environments; keep escalations that reach Notch personnel low

• Build reproducible playbooks so each implementation costs less than the last

• Feed engineering reality into TPM and Solutions Architect planning for POCs and production rollouts

Customers

You are not the account owner. You're in the room for four things: consultation, architecture planning, execution excellence, and timelines.

• Advise across the full stakeholder range — from the engineers your team integrates with, to their engineering managers, up to directors, VPs of Engineering, and CIOs

• Lead architecture planning with customer technical teams: what we'll build against, what their systems can actually support, and where the risk sits

• Speak to execution and timelines with authority — what's committed, what it depends on, and what changed. The depth adjusts to the audience; the answer doesn't.

• Be the technical voice customers trust when the question is can this actually work

Technical bar

Your engineers will go deeper than you in specific areas. You need enough depth to review their work, make architecture calls, and interview well across all of it.

• Large-scale resilient two-way integrations against custom enterprise APIs — queues, retries, idempotency, race conditions, rate limits and quotas

• Designing and consuming APIs for enterprise customers. Required knowledge: Protocols (REST, GraphQL), API security & authentication, architecture (polling, webhooks, pagination). Knowledge of best practices for market integrations

• Cloud deployments at scale — CI/CD, observability, and running on-call for an independent team. Enough infrastructure judgment to hire DevOps engineers, not just work alongside them.

A plus: on-prem environments; AI, LLM, and knowledge-pipeline engineering; building products and processes under data-protection regulation.

Requirements:

• Crazy personal drive. Be a bulldozer.

• Insatiable creativeness. Be a big dreamer.

• You've led an engineering team to predictable delivery — stable output, dates that hold

• You turn one-off solutions into repeatable process by instinct

• You have a hiring network and a real eye for engineering talent

• You can move between a code review and a CIO conversation in the same afternoon, and be taken seriously in both