Senior SaaS / Backend Developer – Insurance Platform, APIs & Customer Portal

# Senior SaaS / Backend Developer – Insurance Platform, APIs & Customer Portal We are developing **The Landlord App (TLA)**, a UK digital platform for landlords combining property management support, compliance monitoring and insurance products. The customer-facing website and sales journey are being developed separately. We are now looking for an experienced **SaaS / Backend Developer or Solutions Architect** to help design and build the infrastructure that sits behind it. This is **not a basic website or WordPress project**. We need a secure, scalable transactional platform capable of managing customers, properties, annual insurance policies, payments, documents, insurer reporting and API integrations. ## What we need The platform will need to support: ### Customer & Property Records * Customer accounts with multiple properties * A permanent **Master Property Reference (MPR)** for each property * Structured and standardised property/address data * Complete history against each MPR ### Policy Administration Each annual insurance contract will receive a unique policy reference. Renewal creates a **new policy**, rather than extending the existing policy reference. The system must therefore retain and link all historic policy terms against the MPR so we can identify continuous insurance history. It will need to manage: * New business * Renewals * Policy inception and expiry * Mid-Term Adjustments (MTAs) * Cancellations * Premium changes/refunds * Policy status * Product type * Policy documentation * Full historical audit trail Important information should not simply be overwritten. Changes and transactions need to be recorded with appropriate **date/time stamps and user/system attribution**. ### Payments Integration with an appropriate payment provider will be required. The system needs to record successful/failed payments, refunds and reconciliation information and trigger appropriate actions following successful payment, including policy creation and customer communications. ### Insurer Premium Bordereaux The platform must be capable of automatically producing monthly insurer premium bordereaux containing new business, renewals, MTAs, cancellations and financial transactions. Accuracy and reconciliation are particularly important. ### Property Compliance Landlords will be able to maintain important property and tenancy information including dates and supporting documents. Examples include: * Gas Safety * EICR * EPC * Property/HMO licensing * Tenancy documentation * Deposit documentation * Other relevant landlord compliance records The system will generate automated reminders as expiry/renewal dates approach. ### FNOL & Claims Integration TLA will provide landlords with an online **First Notification of Loss (FNOL)** journey. TLA does **not** make insurance coverage or claims decisions. The platform will capture the FNOL and supporting documents and transmit the information to the relevant insurer through an API. We ultimately require **two-way integration**. Insurers and appointed legal providers should be capable of returning claim acknowledgements, requests for information, status changes and appropriate claim/legal milestones to TLA. The landlord should then be able to log into their TLA account and see relevant claim progress without needing to understand or access the insurer's underlying claims system. ### Customer Portal Landlords should ultimately have a single account through which they can see: * Their properties/MPRs * Current and historic policies * Policy documents * Payments * Compliance information and upcoming dates * Outstanding actions * Claims and appropriate claim updates ### Reporting & Data We require a properly structured database capable of supporting management reporting and analytics, including **Power BI or equivalent BI tooling**. The platform should be designed so that policy, premium, property, compliance and claims information can be analysed as the portfolio grows. ## What we are looking for We are particularly interested in developers/architects with experience in: * SaaS architecture * Relational database design * PostgreSQL / SQL * REST APIs and webhooks * Third-party API integration * Payment gateway integration * Secure document storage * Customer/admin portals * Authentication and role-based permissions * Cloud infrastructure * Automated communications * Audit/event history * Reporting/data architecture * Production deployment and ongoing support Experience within **InsurTech, FinTech, financial services, policy administration or other regulated transactional platforms** would be advantageous, but is not essential. ## Initial engagement We do not intend to start by commissioning the entire platform in one large project. We would initially like to work with the successful candidate on a **technical discovery and architecture phase**. We will provide the detailed business requirements and customer journey. We would then expect you to help us determine: * Recommended technical architecture * Database structure and relationships * API architecture * Security approach * Cloud/infrastructure requirements * Payment architecture * Document architecture * Development priorities * MVP scope * Future scalability * Indicative development stages, timescales and costs We favour **practical architecture without unnecessary complexity**. The initial platform needs to be cost-effective and reliable while being designed properly enough to scale as policy volumes grow. ## Important TLA must retain ownership and control of the **source code, database schema, repositories, cloud infrastructure and technical/API documentation**. Clear documentation and maintainable code are essential. ## When applying Please briefly tell us: 1. About a SaaS or transactional platform you have architected or built that you believe is relevant. 2. Your experience integrating multiple third-party systems through APIs/webhooks. 3. Your experience with payments and financial transactions. 4. How you normally approach designing a new platform before development begins. 5. Whether you would be comfortable initially undertaking a discovery/architecture exercise before agreeing the wider development scope. We are looking for someone who can potentially become a **long-term technical partner to TLA**, rather than simply completing individual development tickets.