Principal Engineer (Java Full Stack)

JD requirement Assessment 10+ years of progressive engineering Meets. 14+ years. Staff/Principal leadership across teams Moderate. Lead titles and "led modernization”, but no team size, pod scope or cross-team influence stated. Distributed systems and fault tolerance Good. Circuit breakers, retries, timeouts, failover, Kafka. Idempotency and consistency not explicit. Java and Spring Strong. Java 8/11/17, Spring Boot, Spring Cloud, Spring Security. REST API design, versioning, compatibility Good. OpenAPI, API versioning standards, contract-style integration. Event-driven architecture and Kafka Strong. Kafka, SNS/SQS, EventBridge across several roles. PostgreSQL / SQL and data integrity Good. PostgreSQL, Oracle, Aurora, query tuning, PL/SQL. Schema evolution and migrations not shown. Observability (logs, metrics, traces, SLOs) Moderate. Splunk and general logging/tracing mention. No OpenTelemetry, Prometheus, Grafana or SLOs. Automated testing and quality Moderate. JUnit and Mockito, regression tests in Jenkins. No contract or end-to-end tooling named. AWS, Docker, Kubernetes, Helm, Argo CD Strong, minus Helm. AWS (EC2, Aurora, Lambda, CloudFormation), Kubernetes, OpenShift, ArgoCD GitOps. CI/CD and release engineering Good. Jenkins with testing and security checks, GitOps. Rollback and progressive release strategy not described. Legacy modernization Good. Java 8 to 17, monolith to microservices, claims platform modernization. AI-assisted development Strong. Devin, Cursor and Claude, with a review and validation approach. Strengths: the right core stack (Java, Spring, Kafka, PostgreSQL, AWS); resilience patterns and legacy modernization experience; GitOps and CI/CD with quality gates; mature, responsible AI tool use; insurance domain with complex rules.