Principal Software Engineer

Description

About the Team – Claims Loss Data Capture: 

 

Our mission is to develop a platform that can collect, update, and retrieve loss data for both new and existing claims through easy‑to‑consume APIs that are fast, secure, flexible, configurable, and resilient to core system constraints. We enable downstream components to react proactively and asynchronously, powering experiences across FNOL, claim registration, coverage, telematics crash detection, and customer communications. 

We work in an agile framework with a strong culture of collaboration, continuous improvement, and engineering excellence, partnering closely with claims, policy, and digital teams across the organization. 

 

 

**This is a hybrid role (two days in the office a week) in one of our five tech locations: Plano, TX, Columbus, OH, Indianapolis, IN, Boston, MA and Portsmouth, NH**

 

Role Overview:

 

We’re looking for a Principal Software Engineer to serve as a technical leader for the Loss Data Capture platform. In this role, you will help influence the architecture and implementation of high‑scale services that power FNOL intake, loss data management, claim search, claims contact, coverage determination, telematics‑driven crash handling, and telematics crash communications. 

You’ll combine deep hands‑on engineering with system‑level thinking: shaping technical vision, guiding design and implementation, and mentoring engineers, while ensuring our services are secure, observable, resilient, and easy to integrate with. 

 

Responsibilities 

 

• Design, build, and support highly available, scalable microservices and REST APIs that power FNOL intake, loss data capture and updates, claim and contact search, coverage determination, telematics‑driven crash handling, and customer communications. 
• Participate in end‑to‑end solution architecture and system design for JVM/Spring services deployed on cloud platforms, integrating with Apigee X, Entra ID, Kafka, and NoSQL/relational datastores. 
• Own and optimize high‑volume, low‑latency APIs handling millions of requests per day, ensuring strong performance, reliability, and disaster‑recovery readiness. 
• Model and manage data across relational databases and NoSQL/document stores (e.g., MongoDB Atlas, DynamoDB, DocumentDB), balancing consistency, performance, observability, and cost. 
• Design and evolve event‑driven integrations (Kafka) that connect FNOL, claim registration, coverage, crash events, and outbound communications in a resilient, decoupled way. 
• Embed security and privacy by design by driving threat modeling, enforcing modern authentication and authorization patterns (e.g., OAuth2/Entra ID via Apigee X), and protecting PII throughout the loss data ecosystem. 
• Define and champion standards for logging, metrics, and tracing (e.g., Splunk, DataDog) to ensure services are observable, easy to debug, and easy to operate. 
• Collaborate with product, architecture, and claims business partners to translate the team’s loss data platform vision into clear technical roadmaps and well‑designed APIs. 
• Provide strong operational support for team owned services, including participating in the on‑call rotation, responding to production incidents and client requests (e.g., via Slack and Splunk/DataDog dashboards), driving root‑cause analysis, and creating follow‑up work to improve reliability. 
• Mentor and coach engineers on system design, cloud‑native practices, testing, and operational excellence; foster a culture of continuous improvement and learning. 

 

 

Qualifications 

 

Required 

• 8+ years of professional software engineering experience, including significant hands‑on work in Java/JVM with Spring/Spring Boot building production APIs and services. 
• Proven experience architecting and operating cloud‑hosted microservices at scale, ideally on platforms such as Cloud Foundry or Kubernetes with AWS‑backed services. 
• Strong background designing RESTful APIs and integration contracts for high‑throughput, low‑latency systems, including experience with OpenAPI/Swagger and API gateways (e.g., Apigee X or equivalent). 
• Solid experience with both relational databases (e.g., Oracle) and NoSQL/document datastores (e.g., MongoDB Atlas, DynamoDB, DocumentDB), including schema design, performance tuning, and data access patterns. 
• Hands‑on experience with event‑driven architectures and messaging platforms such as Kafka, including designing resilient publish/subscribe and streaming patterns. 
• Demonstrated ability to lead