Technical Team Lead
Mid-sized Australian Fintech – Sydney – Hybrid
A mid-sized Australian fintech. Established, growing, and product-led. The platform is central to the business, so reliability and clear system behaviour matter. Engineering is now focused on maturing architecture, clarifying domain boundaries, and ensuring the platform evolves cleanly over time. This role suits someone who cares about how systems behave, not just whether code runs, and who leads through technical clarity while staying hands-on.

Context
Platform built in C# / .NET with event-driven microservices. Real financial workloads – correctness and sequencing matter. The system is live and healthy, with space to improve domain models, service boundaries, testing discipline and architectural consistency. The team is capable and productive. They now benefit from someone who provides structure, reasoning and shared technical direction. This is a player-coach role. You write code, shape architecture, review design, and mentor in real time. Not delivery admin. Not people management. Leadership is demonstrated in the quality of the engineering work.

What You’ll Do

• Clarify and maintain service and domain boundaries

• Improve how business concepts are represented in code

• Make decisions designed to last

• Stay hands-on in code and reviews

• Mentor through structured, calm technical reasoning

• Encourage testing as part of design

• Treat refactoring as ongoing practice

• Help engineers think in systems rather than isolated components

• Work with Product to translate intent into clear, sequenced work

• Communicate trade-offs plainly

Not This Role

• Not performance management

• Not delivery tracking

• Not roadmap ownership

• Not slide-deck architecture

Required Technical Experience

• Strong C# / .NET Core or .NET 6+

• Event-driven and message-based systems

• Microservices in production

• Domain-Driven Design(bounded contexts, aggregates, ubiquitous language)

• BDD/TDD used for behavioural clarity

• Understanding of distributed system trade-offs

• Practical data modelling experience

How You Work

• Communicates clearly and directly

• Leads through competence and reasoning

• Values clarity and maintainability over cleverness

• Thinks in systems, not just components

• Enjoys improving engineering environment and capability

Why This Will Appeal

• You remain hands-on

• Your decisions influence platform behaviour long-term

• You shape engineering culture, not just delivery output

• You build systems designed to last, not just ship

Work Model
Sydney-based hybrid. Collaboration when useful, focus time protected. Team values craft, clarity and thoughtful engineering.

Next Step
If this aligns with how you like to build and lead software, share your CV or reach out for a straightforward, confidential conversation.