Skip to content
Search jobs inside your AI agent. Claude, ChatGPT, Claude Code, Codex, Gemini, Cursor and Grok
Connect

Nexl

NewBe an early applicant

Technical Lead

Posted Updated

Description

Description


Nexl is looking for a Tech Lead to lead our Internal Services (Keystone) squad. A Tech Lead at Nexl owns three things: the technical direction of their squad, the people in it, and how it delivers. You’ll be hands-on in the codebase and accountable for your engineers’ growth and performance. There is no delivery manager, scrum master or project manager alongside you. You own the cadence, the forecast and the escalation when something slips.
This squad builds the shared capabilities that make every other engineering team at Nexl faster. Near-term work includes consolidating authentication, building a design system and replacing our feature flagging setup, so a lot of what you lead will land across other squads.

Keystone takes on the hardest problems in our stack, the ones where a wrong call slows every other squad down for months. The bar for this seat is high, and we are looking for someone who raises it further.

Agentic-first ways of working are how we build, and Keystone owns the agentic harness that makes that possible for everyone at Nexl. Through our Agentic Factory project your squad builds the shared harness, the context and guardrails agents work within, and the evals we use to hold quality. Every other squad depends on what you ship here, so this is the part of the role with the widest reach.
You’ll work closely with the Product Manager in your squad, the Head of Engineering, our CPTO, Product and Tech Leads across the other squads.

This role is for someone equally comfortable making an architecture call, running a tough 1:1, and getting a slipping delivery back on track.


Requirements

Technical direction & architecture
  • Set the technical direction for your squad and make the architectural calls, working with the other Technical Leads and the Head of Engineering to uphold engineering-wide standards for infrastructure and system architecture.
  • Design before you build. Write architecture decisions, test them with the engineers and squads they affect, and get alignment upfront.
  • Stay in the codebase. Contribute code every week and set the quality bar through your own work, and through the automated checks and AI reviews your squad builds. We want quality enforced by the system, with your judgement spent on the calls that need a human.
  • Set the AI-first standard for your squad, decide which work goes to AI agents and with what guardrails, and improve the shared workflows and tooling the rest of engineering builds with, including how agent output is verified at scale.
  • Own the reliability, security and scalability of what your squad ships and make sure what you build for other squads is adopted and trusted.. Build security and privacy into designs from the start, lead incident response, and make sure fixes land.
  • Keep the architecture simple enough to change, and retire what no longer earns its place.
  • Explain complex technical decisions simply, in writing and in person, to engineers, Product Managers, Designers, and the leadership team.

People management
  • Manage the engineers in your squad through regular 1:1s, clear expectations, honest feedback and performance conversations.
  • Coach engineers on system design, problem-solving and AI-native development, so they grow into more autonomous, higher-output engineers.
  • Build a healthy team where knowledge is shared and nobody is a single point of failure, and play an active role in hiring and onboarding.
  • Give engineers whole problems to own, from design through to production, and back the decisions they make.

Delivery management
  • Own your squad’s delivery: planning, scoping and estimating work, and making sure it ships with quality.
  • Run your squad's rituals and set its cadence. The quality of those rituals is yours to maintain.
  • Present your squad's flow metrics at our fortnightly delivery review, and explain variance with data.
  • Ship in small, reversible increments and get work in front of users early.
  • Shape priorities with the Head of Engineering and Product, while balancing technical debt against new work.
  • Treat the engineering teams you serve as your customers. Understand their pain points, and measure success by how well they adopt what you build.
  • Anticipate risks, remove blockers and create clarity where things are ambiguous.
  • Coordinate with other squads where your work lands on theirs, so changes are adopted, not just shipped.


Apply

See also