Insurance Policy Management Platform

A full-stack web platform is being developed to handle every stage of insurance policy management, from issuance through renewal, with tight PDF generation and editing built in. The system sits at the heart of a California-based carrier, so all collaboration, stand-ups, and code reviews happen on Pacific Time. Scope The project focuses exclusively on the policy side of the business; claims workflows and CRM modules are out of scope for now. Core business logic must mirror real-world carrier rules, endorsements, and regulatory reporting, so fluency in typical U.S. insurance terminology is essential. Technology Expectations I am coding in a modern JavaScript/TypeScript environment—React on the front end, Node (or a comparable framework) on the back end—paired with PostgreSQL and deployed on AWS. Strong experience manipulating PDFs through libraries such as PDFLib, pdf-kit, iText, or similar is non-negotiable, as policy packets, declarations, and endorsements must be assembled, annotated, and re-issued on demand. Key Features to Deliver • Automated policy renewal with configurable underwriting rules • Real-time policy updates that instantly reflect on the dashboard and downstream reports • Secure policy documentation storage, including on-the-fly PDF rendering and editing Acceptance Criteria 1. A user in the “Underwriter” role can trigger an automated renewal and view the resulting PDF packet without manual intervention. 2. Editing any coverage field must update every associated premium and endorsement figure in real time (≤1000 ms latency). 3. All policy documents are versioned, stored, and retrievable through an encrypted S3 bucket, with access logged per SOC 2 guidelines. Daily overlap with 9 AM–3 PM California time is required for walkthroughs and quick iterations with the actuarial and compliance teams. Production-quality code, unit tests, and concise documentation are expected with every milestone push.