Solution Architect (P&C insurance domain)

EPAM Systems•New York, NY

About The Position

We are building a greenfield Commercial Lines insurance platform, initially focused on Commercial Property. The platform is a modern microservices-based ecosystem supporting underwriting, rating, policy administration, carrier management, and third-party integrations. The Solution Architect reports into Enterprise/Solution Architecture and works closely with Product, Underwriting, Actuarial, Engineering, and Data Engineering teams. This hands-on architecture and governance role defines the target-state architecture and produces the architecture deliverables engineering teams will build against.

Requirements

  • 8+ years of solution or enterprise architecture experience.
  • At least one greenfield microservices platform shipped end-to-end, from design through production.
  • P&C insurance domain experience; Commercial Lines experience is ideal, including account/policy/coverage hierarchies, rating engines, and underwriting rules engines. Personal Lines-only experience is a gap but is not disqualifying when paired with the capacity to ramp up quickly.
  • Production experience with event-driven architecture using Kafka or an equivalent, including domain event design, CQRS, and eventual consistency trade-offs.
  • API design at the contract level, including OpenAPI 3.1, versioning strategy, and backward-compatibility discipline across independently deployable services.
  • Data architecture experience for regulated, auditable financial transactions, including immutable ledgers, effective dating, reconciliation jobs, and NUMERIC precision handling.
  • Experience integrating IVANS, EZLynx, or similar AMS/clearinghouse platforms.

Nice To Haves

  • Direct experience with reinsurance/quota share, bordereaux reporting, or multi-carrier allocation.
  • Experience with Microsoft Azure, .NET, and SQL Server.

Responsibilities

  • Define service decomposition, bounded contexts, and data ownership for each 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 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 to enable 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, responsible for pricing, and the Rules Service, responsible for eligibility, referral, and straight-through disposition logic.
  • Design the Carrier Service abstraction layer to support 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 of 15 minutes or less, and RTO of 4 hours or less.
  • Establish architectural governance standards, including 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.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service