We are building a greenfield Commercial Lines insurance platform with an initial focus on Commercial Property. The platform is designed as a modern microservices-based ecosystem supporting underwriting, rating, policy administration, carrier management, and third-party integrations.
The Solution Architect will report into Enterprise/Solution Architecture and work closely with Product, Underwriting, Actuarial, Engineering, and Data Engineering teams. This is a hands-on architecture and governance role responsible for defining the target-state architecture and producing architecture deliverables that engineering teams will build against.
Req.#1119126031
Responsibilities
Define service decomposition, bounded contexts, and data ownership per service
Design the event-driven backbone, including Kafka (or equivalent) domain event models, event schemas, versioning, and replay semantics
Author OpenAPI 3.1 specifications for all inter-service and externally consumed APIs before Engineering builds against them
Design the commercial insurance data model, including the Account → Applicant → Policy → Coverage → Location → Building → Unit/Exposure hierarchy and NAICS-specific exposure schema extensions
Design the immutable Premium Transaction Ledger enabling full rating-factor-level reconstruction of every bound dollar across policy, coverage, location, building, exposure, carrier, and factor levels
Enforce architectural separation between the stateless Rating Service (pricing only) and the Rules Service (eligibility, referral, and straight-through disposition logic)
Design the Carrier Service abstraction layer supporting multiple carriers and quota-share allocation models
Define integration architecture for SSO federation, AMS/clearinghouse connectivity, third-party data enrichment providers, and payment gateway integrations
Drive non-functional requirements, including sub-second rating response times, 99.9% uptime, RPO ≤15 minutes, RTO ≤4 hours, and architectural governance standards such as immutable transactions, effective dating, and prohibition of cross-service database access
Produce and maintain architecture artifacts, including C4 diagrams, ADRs, API contracts, and data models
Requirements
8+ years solution/enterprise architecture, with at least one greenfield microservices platform shipped end-to-end (design through production)
P&C insurance domain experience, ideally Commercial Lines (account/policy/coverage hierarchies, rating engines, underwriting rules engines). Personal Lines-only background is a gap, not a disqualifier, but must be paired with fast ramp capacity
Event-driven architecture in production – Kafka or equivalent, domain event design, CQRS, eventual consistency trade-offs
API design at the contract level – OpenAPI 3.1, versioning strategy, backward-compatibility discipline across independently deployable services
Data architecture for regulated, auditable financial transactions – immutable ledgers, effective-dating, reconciliation jobs, NUMERIC precision handling
Direct experience with reinsurance/quota share, bordereaux reporting, or multi-carrier allocation is a strong plus, not a hard requirement
Experience integrating IVANS, EZLynx, or similar AMS/clearinghouse platforms
Nice to have
Experience with Microsoft Azure, .NET, and SQL Server