Senior Full Stack Developer

About the Company Fin365 delivers cutting‑edge software and technology services for the financial services industry. Our innovative cloud‑based software solutions leverage the latest Microsoft technologies to deliver exceptional value to our customers. We are passionate about building products that solve real business challenges and create a fun, collaborative environment for our team. About the Role The Senior Full Stack Developer is a hands‑on individual‑contributor role responsible for building the next generation of the Fin365 platform; from our re‑architected, source‑agnostic data‑feed engine to the client and adviser web portals. You will deliver features end‑to‑end across a modern Microsoft stack: Angular/TypeScript on the front end, .NET (C#) services on the back end, and Microsoft Dynamics 365 as the core data platform, all deployed to Azure. You will join a small, high‑performing product‑development team at a pivotal moment as we separate new‑architecture build from legacy maintenance and lift our engineering practices — introducing isolated (ephemeral) test environments, stronger CI/CD, and automated quality gates. You will write clean, well‑tested, well‑documented code, contribute to architecture and design reviews, and help mentor and uplift our distributed development team. Responsibilities Deliver full‑stack solutions end‑to‑end with a focus on performance, security, scalability and maintainability.Own assigned features from concept through to production, including tests, documentation and handover.Collaborate across development, QA/SDET, product and customer success functions.Stay current with emerging technologies and propose pragmatic improvements to existing systems. Technical Skills (essential) Strong commercial experience with .NET (C#) back‑end development and RESTful API design.Strong front‑end expertise with Angular and TypeScript (HTML5, CSS3/SASS); component‑based architecture.Solid experience with Microsoft Azure (App Services, Storage/Tables, Blob, Functions/Web Jobs) and SQL Server.Experience with OAuth2 and modern authentication protocols (tokens, refresh flows).Familiarity with CI/CD and DevOps tooling — Azure DevOps, GitHub, pipelines and branching strategies.Strong debugging, troubleshooting and performance‑tuning skills. Highly Regarded Microsoft Dynamics 365 / Dataverse / Power Platform development and its API limits and patterns.Cosmos DB and NoSQL data modelling; message queues and asynchronous processing.Experience integrating third‑party financial‑services data feeds (API and SFTP/file‑based).Test‑driven / behaviour‑driven development (TDD/BDD) and infrastructure‑as‑code (e.g. Terraform).Domain‑driven design and contemporary architectural patterns (e.g. CQRS). Additional Requirements Self‑directed, disciplined and comfortable working in a distributed team.Excellent communication skills.Demonstrable examples of collaboration and mentoring skills. Ready to shape the future of financial technology? As well as applying through LinkedIn, please email us at join.us@fin365.com.au directly with your resume. In your email, we'd love you to showcase your expertise by responding to the scenario below. Scenario Question: Building a New Data Feed on a Modern Architecture Fin365 is migrating from bespoke, per‑provider data‑feed modules to a single, source‑agnostic ingestion engine that must reliably import investment, insurance and account data from many providers into Microsoft Dynamics 365; some via API, some via scheduled file drops (including daily delta files). Keeping in mind Fin365's already has a functional data feed architecture, with 20+ functioning connections, describe how you would design and deliver a new provider feed on this architecture end‑to‑end. Cover: your approach to ingestion and transformation to a canonical model; handling deltas and avoiding data loss/duplication; front‑end surfacing of import status and errors; testing strategy (unit, integration, automated regression); observability and reconciliation; performance and API‑throttling considerations; and how you would validate correctness before release.