MABASA / LINKEDIN
Senior Software Engineer (Platform)
Nexl
- Location
- Sydney, New South Wales, Australia
- Work type
- fulltime
- Source publication date
- Original publication date not confirmed
- Source closing date
- Not supplied — check original advert
Job description from the source
**About us** Nexl is a fast-growing LegalTech company on a mission to elevate the business of law. The company builds an AI-driven CRM and growth intelligence platform that brings a firm’s internal and external data together so lawyers, marketing teams, and business development teams can collaborate, spot opportunities, and grow revenue. Nexl has been recognised by the Financial Times, Deloitte, and the Australian Financial Review as one of the fastest-growing companies in the region, is trusted by 150+ law firms globally, and recently closed a $23M USD Series B led by Tidemark Capital. **The Opportunity** Nexl is looking for a Senior Software Engineer to join Keystone, our internal platform team. Keystone builds the common capabilities that make every other engineering team at Nexl faster. Near-term, that means consolidating several authentication mechanisms into one, building a design system with tokens and a shared component library, and replacing a feature flagging setup that no longer scales. This is foundational work that every other team will build on, so we need one of our strongest engineers in this seat. This isn’t a growth hire. We’re looking for someone who raises the bar from day one. AI tools such as Claude Code and Cursor are core to how we build, and you’re expected to use them to ship faster and at higher quality. Deep fundamentals still matter just as much, including architecture, distributed reliability, security and system thinking. They’re what let you direct AI effectively and catch where it gets things wrong. This is a high-ownership role for someone who designs before they build, can bring multiple teams along with a change, and wants to shape how a fast-growing LegalTech company builds. **What You’ll Own & Do:** * Lead the consolidation of our authentication mechanisms into a single approach, and get the teams that depend on it to move across. * Build and roll out a design system, covering tokens and a shared component library that product teams actually adopt. * Replace our feature flagging setup with something that scales with the business. * Design before you build. Write architecture decisions, test them with the engineers they affect, and get alignment upfront. * Own the reliability of the shared services you ship, including idempotency, retries, duplicate delivery and failure recovery. Make sure other teams can trust them in production. * Work with Tech Leads across engineering to understand what’s slowing their teams down, and turn that into platform capabilities. * Improve the shared agentic harness and AI workflows, not just use them, so the whole engineering team gets faster. **What We're Looking For:** Must haves: * You’ve led a consolidation across multiple teams, such as an auth or identity migration, a shared platform rollout, or a common service other teams adopted. You can explain how you got teams to move. * You have concrete depth in distributed reliability (idempotency, duplicate delivery, retries and failure recovery), with examples from systems you’ve run. * You design before you build, and can show evidence of writing architecture decisions and getting alignment upfront. * You’re agentic-first in practice. You use Claude Code, Cursor or equivalent tools as your primary workflow, and you’ve improved the shared harness rather than only using it. Nice to haves: * Ruby on Rails experience. Our core platform is a Rails monolith, so strong Rails depth is a real advantage, but platform leadership matters more. * Golang experience. * React experience. * Experience building or rolling out a design system or shared component library. * Experience with feature flagging platforms at scale. * Experience in multi-tenant, data-heavy SaaS applications. * Knowledge of DevOps practices, Infrastructure as Code, or cloud infrastructure (AWS or Azure). * Experience designing or orchestrating multi-agent systems. **What Success Looks Like:** * Teams across engineering are on a single, consolidated authentication approach, and the migration happened with buy-in rather than force. * Product teams build on the shared design system and component library by default. * Feature flagging scales with the business and stops being a source of friction. * Your architecture decisions are documented, aligned before build, and hold up over time. * The shared services Keystone owns are reliable, and other teams trust them. * Improvements you make to the shared agentic harness are adopted across engineering and multiply the team’s collective output. **Life at Nexl** * Hybrid working. You'll be in our Sydney hub 3 days a week for collaboration. * Work from anywhere. Spend up to four weeks a year working remotely from a location of your choice. * 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. * 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. * Tools & tech. Modern, AI-first ways of working to help you move faster and smarter, plus a work laptop. *Even if you don't tick every box, Nexl would still love to hear from people who are excited by the mission and believe they would thrive in a high-growth, high-accountability environment.*
Check the original advert before applying
Apply through the employer or original publisher. An external site may require registration. Opening an advert does not submit an application.
Content is supplied by an external publisher and may change. For source and availability limits, read our listing disclaimer. How to check an original listing ↗