Reliance Back Office provides a wide range of administrative services for companies around the globe. We recruit, train and staff talented remote professionals.

What we are looking for:

We’re looking for an Full-Stack Engineer to join our team partnered with one of our clients, Hey Capto.

In this role, you’ll be the primary engineer on the product, working across the whole stack largely on your own, so the ability to work independently is essential.

About the product:

HeyCapto is a property-risk intelligence platform for insurance professionals. It aggregates property data from 7 specialized providers, caches it in a two-tier architecture, and layers AI-powered analysis on top.

It's a multi-tenant SaaS with a three-level user hierarchy and token-based billing.

The product surfaces are:

• A .NET 10 API backend (the core system)
• A React website (heycapto.com — dashboard, admin, billing)
• A Chrome browser extension (the sidebar analysts actually work in)
• A separate public marketing site (its own repository)

The role in one sentence:

Own and maintain the HeyCapto application repository and the public marketing-site repository — keeping the backlog healthy, the code shippable, the integrations alive, and the deployments green — as the primary (often sole) engineer on the product.

This is a breadth role. You won't go deep on one subsystem for months; you'll move across the API, two frontends, an extension, a static site, seven third-party integrations, the database, and the CI/CD pipelines — often in the same week. We're hiring for someone who is genuinely comfortable being the one person who understands how all of it fits together.

What you’ll do:

Backlog & product hygiene:

• Groom and maintain the GitHub Projects backlog (stories, bugs, milestones) for both repositories.
• Triage incoming bugs, reproduce them against real runtime data, and write clear, implementation-ready tickets.
• Keep milestone scope, follow-up tracking, and manual-verification checklists honest and current.
• Uphold the project's engineering standards (documented, story-driven, test-tiered).

Application code (this repo):

• Implement and maintain features across the .NET API, the React website, and the Chrome extension.
• Maintain the 7 external data-provider integrations — API contracts drift, rate limits change, responses break; you keep them resilient and correct.
• Maintain the multi-tenant data model, token-billing logic, and caching tiers.
• Write and maintain tests across the four-tier model (unit, contract, integration, UI).

Public marketing site (../heycaptopublic):

• Maintain the standalone marketing/marketing-content site (vanilla HTML/CSS/JS, no build step).
• Keep brand, plans, contact, and legal pages accurate and deploying cleanly to Azure Static Web Apps.

Ops & delivery:

• Keep CI/CD green across both repos (GitHub Actions, self-hosted runner, Azure deploys).
• Own database migrations (DbUp — ordered, forward-only SQL scripts) and their safe rollout.
• Monitor deployed environments (Azure Container Apps, Static Web Apps) and diagnose production issues from logs before theorizing.

Required tech stack experience:

Backend (.NET) — primary:

• C# / .NET 10, ASP.NET Core Minimal APIs
• Dapper (raw SQL, not EF) over SQL Server
• DbUp migrations (versioned, forward-only SQL scripts)
• Serilog, Polly (retry / circuit-breaker resilience per provider)
• Clean layering discipline: a zero-dependency Domain, an Infrastructure layer for integrations/logic, a thin API layer, plus background Workers.

Frontend & extension:

• React 18 + TypeScript, built with Vite
• Bootstrap (website) and Tailwind CSS (extension) — different frameworks per surface, on purpose
• Chrome Extension (Manifest V3) development — side panel, content scripts, extension messaging
• Plain HTML / CSS / JavaScript for the public marketing site (no framework)
• Google Maps Platform JS, Leaflet, MSAL (auth) on the client

Cloud, auth, integrations & payments (Azure-centric)

• Azure: Container Apps, Static Web Apps, Container Registry, Communication Services
• Microsoft Entra External ID (CIAM) — JWT bearer auth, MSAL, social login, native auth flows
• Azure OpenAI (GPT-4o) — prompt design and compliance guardrails for the AI features
• Stripe (subscriptions + token top-ups)
• Integrating and maintaining REST APIs from third-party data vendors (contract mapping, defensive parsing)

Testing & CI/CD

• xUnit, Testcontainers (Docker-based integration tests), Playwright (E2E), Vitest (frontend)
• GitHub Actions pipelines, including deployment workflows to Azure
• Git / GitHub Projects fluency (branching, PRs, issues, milestones, subissues)

Nice to have

• PDF generation (PdfSharp / MigraDoc)
• Insurance, property-data, or risk/underwriting domain background
• Experience owning a multi-tenant SaaS billing model end-to-end
• Comfort operating a self-hosted CI runner

How we build (worth knowing before you apply):

HeyCapto is built with a standards-driven, agentic development workflow: work is decomposed into well-specified stories, and much of the implementation is driven through an AI-assisted pipeline that enforces the team's engineering standards (test tiers, reviews, CI gates). You do not need to build or operate that agentic tooling — but you should be comfortable working within a highly structured, story-first process where clear tickets and disciplined tests are the norm, and you should be an effective collaborator with AI-assisted tooling rather than resistant to it.

The heart of this role is human judgment: keeping the backlog coherent, catching what the automation misses, diagnosing production reality, and being the person who actually understands the whole system.

What success looks like in the first 90 days:

• The backlog for both repos is groomed, triaged, and trustworthy.
• You can independently ship a bug fix from ticket → PR → green CI → deploy across any surface.
• You've maintained at least one provider integration or migration without hand-holding.
• Production incidents get diagnosed from logs and evidence, not guesswork.