Lead Software Engineer

Lead Engineer

Turing Labs

Fully remote · EU working hours

About Turing Labs

Turing Labs is an AI-native professional services firm. We build the systems and agents that do the work — research, analysis, revenue operations, customer engagement — for organizations in private equity, B2B, pharmaceutical, logistics, and beyond.

We started Turing Labs because the gap between what AI can now do and what organizations are actually using it for is enormous. Entire functions — research, revenue operations, investment analysis, customer engagement — should be orchestrated by intelligent systems that do the work, not by dashboards that describe it. We build those systems and agents. We ran our own operations on them first, and only started offering them to clients once we were shipping real work on our own.

Our co-founders and practice leads have been operators — CEO, CIO, CDO, transformation director roles across financial services, private markets, technology, and consulting — before this. We built our own operations on the same connected intelligence model we deploy for clients, and we run on it every day. We are small, senior, and distributed across Zurich, Dublin, San Francisco, Spain, and Germany.

How we work

We are radically transparent and heavily AI-augmented. What that concretely means:

• Open engineering compensation. Every engineer sees what every other engineer is paid.
• Open Slack and open documents. Channels and docs are accessible across the team by default. Private is the exception, not the rule.
• Open financials. The team sees how the business is doing.
• Few meetings, fully captured. Every meeting is transcribed and pushed to Slack. The whole team has access to our client intelligence MCP, so context flows instead of getting lost.
• Agents do the mundane. Meeting intelligence, research, coordination, status updates — systems we built handle a lot of what would otherwise fill the day. The team spends its time on the interesting parts.

If you have worked in environments where ceremony outweighs output, this will feel different.

The role

We are hiring a Lead Engineer to own engineering delivery across our client portfolio and help shape the roadmap for our Accelerator library.

The Lead Engineer sits at the intersection of client work and platform development. You will ship production work for clients, and you will shape where the platform goes next — what gets built, what gets abstracted, and how our Accelerators evolve as we take on more engagements.

This is a hands-on role. You will write production code daily using modern AI-assisted workflows (Cursor, Claude Code, MCPs). You will lead technical discovery with clients. You will take ownership of the engineering function as the company grows.

What you will own

• End-to-end technical delivery across two to three concurrent client engagements — architecture, code, evals, deployment, and the technical side of the client relationship.
• The Accelerator roadmap. Helping shape what the platform looks like twelve and twenty-four months from now — the architecture, the abstractions, and the modules we prioritise next.
• Client-facing technical leadership. You will run technical discovery calls, write PRDs, and be the engineering counterpart to senior client stakeholders — VPs, partners, investment principals.
• Engineering hiring and team growth. Screening, interviewing, onboarding, and mentoring engineers as pods scale.
• Engineering practice. Code review, eval frameworks, deployment hygiene, observability. The shared playbook that makes multiple pods possible.

What you will work on

Our client base spans private equity, B2B organizations, pharmaceutical, and logistics, and is growing rapidly. The work ranges from connected intelligence platforms for investment research and portfolio analysis, to call intelligence and lead scoring systems integrating enterprise stacks, to voice agents and operational AI for industrial operators.

Each engagement needs its own pod as it scales. The Lead Engineer shapes how those pods are staffed, coordinated, and how the lessons from each engagement feed back into the platform.

What you bring

Senior hands-on engineering

• Seven to twelve years total experience, with at least three years leading engineers.
• Fluent in TypeScript and Python. Comfortable across backend, data, and frontend.
• Daily user of Cursor and Claude Code. Has built and used MCPs in real work.
• Has shipped production AI systems with real users, real evals, and failure modes you have had to debug.

Technical leadership with real reps

• Has led a team of three to six engineers for twelve months or more, with real direct reports, performance conversations, and hiring involvement.
• Has run technical discovery end-to-end — written PRDs, designed architectures, built eval plans — without a founder in the room.
• Has been the technical counterpart to senior client or stakeholder-side decision makers.

Stack fluency in our priority areas

• LLM orchestration, agent systems, and evals. Claude, Gemini, retrieval, prompt engineering treated as a real craft.
• Enterprise integration. Salesforce, Snowflake, and the realities of enterprise data pipelines.
• Full-stack product. Supabase or Postgres, React or Next.js, Render or equivalent.
• Useful but not required: voice and speech (Deepgram), N8N, Neo4j, AWS compliance work.

Judgment

• Knows when to optimise for reliability and when to optimise for velocity — and can explain the difference using past work.
• Sees compliance, data residency, and PII issues coming before they become blockers.
• Writes clearly. Works async. Communicates tradeoffs without dressing them up.
• Comfortable in a transparent, AI-augmented environment where agents are in the loop of daily operations, not just tools you use to code faster.

What would stand out

• You have been an early engineering hire at a Series A or B AI company, or led delivery at a senior AI consultancy.
• You have scaled a team across concurrent client engagements and can tell the story of what broke at each stage.
• You have worked with regulated clients — financial services, healthcare, private equity — and understand the compliance dance.
• You have shaped a technical platform or library from client work.

This is not the right role for you if

• You prefer research to shipping.
• You have stepped away from writing code and do not want to come back.
• You have only worked inside one product team — client-facing work will take some adjustment.
• You use AI-assisted tools occasionally. We need daily fluency with Cursor and Claude Code.
• You want pure product work. Half the role is client delivery.

How we think about the role growing

This is explicitly a Head of Engineering in waiting. Over twelve to eighteen months we expect the role to evolve:

• Months one to three. Embed in two client engagements. Own delivery and code alongside the founders. Build context on the Accelerator platform and roadmap.
• Months three to six. Take technical ownership of at least one flagship client. Begin hiring. Shape how the Accelerator roadmap evolves from live engagements.
• Months six to twelve. Staff new pods as the pipeline converts. Own engineering practice — reviews, evals, deployments. Become the engineering face to clients.
• Months twelve to eighteen. Head of Engineering in title. Owning the org, the architecture, and the technical direction of the platform.

Why this role

A few honest reasons, in the order we think they matter:

• Autonomy. You will own engineering end-to-end, reporting directly to the co-founders. There is no layer between you and the technical decisions.
• Impact on direction. You will shape the Accelerator roadmap at the point where those decisions compound for years. The architecture, the abstractions, the standards.
• Senior operator environment. Everyone around you has done the work before. You will not be explaining why requirements documents matter, or why client stakeholders deserve real answers.
• AI-native ways of working. Our own operations run on agents. You will build interesting things, not spend your days in ceremony.
• Clear path to Head of Engineering. The trajectory is real and sequenced, not aspirational.

Compensation is competitive in cash, with meaningful equity. The primary pitch for this role is autonomy and impact.

Logistics

• Location. Fully remote. EU working hours; our core team overlaps Ireland, UK, Switzerland.
• Process. First call with a co-founder. Technical deep-dive. Systems design. Paid three-day trial engagement on a real client problem. References. Offer.
• Contact. contact@turinglabs.ai