16 Nov
|
NEXL
|
Australia
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.
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, transparent 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.
Must haves
- Technical leadership: Proven experience as a Tech Lead, or a Senior Engineer leading technical direction, in a high-growth SaaS or technology company.
- People management: Experience managing engineers, including 1:1s, feedback, performance and growth.
- Delivery ownership: you have run a team's delivery without a dedicated delivery manager or project manager, owned the forecast, and escalated early when it was at risk.
- Architecture: A track record of sound architectural decisions and trade-offs under real delivery pressure, with evidence of designing before building and you write explicit design docs and architecture decisions that others can challenge.
- Collaboration: You’ve worked with other technical leads to set and uphold shared engineering standards, and you can influence decisions beyond your own team.
- Internal customer focus: You treat other engineering teams as customers,
build what they’ll want to adopt, and balance their needs against your own team’s roadmap.
- Agentic-first: you use Claude Code, Cursor, or equivalent tools as your primary workflow. You can explain how you verify agent output at scale, including your use of evals, how much code you still write by hand and why, and how you have lifted a whole team's practice.
- Communication: you can make a complex design clear to a technical or non-technical audience quickly.
- Reliability: Strong fundamentals in distributed systems and reliability, including idempotency, retries, failure recovery, observability, and incident response.
Nice to haves:
- Ruby on Rails experience. Our core product is a Rails monolith, so strong Rails depth is a real advantage, but technical leadership matters more.
- Golang experience.
- React experience.
- Experience leading an internal services or platform team, or a change multiple teams had to adopt, such as an auth migration or shared service.
- Experience with design systems or feature flagging at scale.
- Experience in multi-tenant, data-heavy SaaS applications.
- Experience building in security-conscious environments, such as ISO 27001, SOC 2, or GDPR.
- Knowledge of DevOps practices, Infrastructure as Code, or cloud infrastructure (AWS or Azure).
- Experience designing or orchestrating multi-agent systems.
- Experience hiring engineers and growing a team.
What Success Looks Like
- Your squad’s technical decisions are sound, documented and aligned with the broader engineering strategy.
- Engineers in your squad are growing in skill, ownership and AI-first capability, and others want to join it.
- Your squad delivers what it commits to, at high quality, without shortcuts that cost technical health.
- The shared services your squad builds are adopted by other squads and trusted in production.
- You help define what engineering excellence and AI-first engineering look like at Nexl.
- Hybrid working. You'll be at our Sydney WeWork 2 days a week for collaboration.
- Work from anywhere. Spend up to four weeks a year working from outside Australia.
- Purposeful connection. A jam-packed social scene with weekly catered lunch, quarterly socials, team off-sites, and events throughout the year to bring everyone together.
- Birthday leave. Take a paid "Nexl Day" during the week of your birthday.
- High growth. A scaling environment with autonomy, ownership, and visible impact.
- ESOP. Employee stock options so you share in the upside.
- Parental leave. Paid leave to support you and your family as it grows.
- Transparent by default. Fortnightly all-hands with strategy, metrics, wins, and learnings.
- Tools & tech. Modern, AI-first ways of working to help you move faster and smarter, plus a work laptop.
📌 Technical Lead (Australia)
🏢 NEXL
📍 Australia