Senior Full-Stack Developer

We build and run a multi-tenant risk-management platform for commercial insurance. Underwriters and loss-control consultants use it to survey sites, raise recommendations, and track whether anyone actually did anything about them. It is a real product with real customers and about fifteen years of history. The work is roughly half building new things and half making old things behave.

This engineer will own features end to end. Angular in the browser, .NET on the server, SQL Server and MongoDB underneath, deployed through our own pipeline to customer sandboxes. This is not full stack used as a polite word for front-end work with occasional API calls. They will write the query, the endpoint, the component and the test.

As a Senior Analyst in Full Stack Engineering, you’ll own features end to end across the browser, server, data layers, and tests. You’ll design, develop, enhance, test, troubleshoot, and support software solutions; contribute to technical design decisions; and collaborate with engineering and business partners.

You’ll work with Angular 16, TypeScript, RxJS, Kendo UI for Angular, Angular Material, Bootstrap, and SignalR. The back end includes C# and .NET services, SQL Server, MongoDB, Kafka, xUnit, and Moq. The platform includes a classic ASP.NET Website alongside the modern Angular application. Our delivery environment includes Kubernetes through Rancher Desktop, Jenkins, Azure DevOps, and yuniql database migrations.

* Design, develop, configure, enhance, and maintain full stack software components across front-end, back-end, integration, and data layers in alignment with Duck Creek engineering standards. *  Analyze business, functional, and technical requirements to determine appropriate software design approaches, implementation options, and solution impacts. * Build and maintain scalable, secure, reliable, and maintainable application features using established software development methodologies, coding standards, and architecture patterns. * Contribute to technical design activities, including application flow, component interaction, API design, data structures, integration points, and system behavior. * Develop and support front-end application functionality, including user interface components, client-side logic, usability considerations, and integration with services or APIs. * Develop and support back-end application functionality, including business logic, service layers, APIs, data access, system integrations, and application performance considerations. * Investigate, troubleshoot, and resolve complex software defects, production issues, configuration problems, and technical anomalies using structured analytical and problem-solving techniques. * Perform code reviews, unit testing, integration testing support, debugging, and technical validation to ensure solution quality, maintainability, and adherence to standards. * Collaborate with architects, product owners, business analysts, quality engineers, DevOps engineers, and other technical stakeholders to clarify requirements, assess risks, and deliver effective solutions. * Adapt existing approaches, frameworks, and technical patterns to address non-routine problems where information may be limited, incomplete, or subject to interpretation. * Support continuous improvement of engineering practices, including automation, reusable components, development processes, documentation, code quality, and technical knowledge sharing. *  Advise peers and cross-functional partners on technical matters within the full stack engineering discipline, including solution behavior, implementation considerations, and issue resolution approaches. * Front end Angular 16 with Kendo UI for Angular, Angular Material and Bootstrap. State is a hand-rolled Behavior Subject store rather than NgRx, which was a deliberate choice and is occasionally annoying. Lazy-loaded feature modules behind a module registry. SignalR for live updates. Four locales. * There are two front ends. The modern Angular application, and a classic ASP.NET Website that predates it, which has no project file and is still load-bearing. They are bridged by Angular components compiled to custom elements and embedded into the older pages. It is a managed mess, and whoever joins will spend time there.