Senior Salesforce Developer (Apex + LWC)

Freelance Salesforce Developer (Apex + LWC) We're looking for an experienced freelance Salesforce developer to help us extend and harden a working, integration-heavy Salesforce application. This is real Apex and Lightning Web Component engineering — a developer role, not an admin role. You'd be the senior Salesforce voice on the project. The product A Salesforce-based platform for Medicare enrollment and broker scheduling: a multi-step enrollment flow, telephony with call-recording pipelines, e-signature, scheduling, and plan recommendations. It handles healthcare data in a HIPAA-sensitive domain — consent handling and auditability are first-class concerns.. Being candid about where it came from The application was built quickly, largely by one person using AI pair-programming tools, without a deep Salesforce-engineering background. It works, and it's better-tooled than that origin suggests — a source-driven SFDX repo with CI, linting, static analysis (Salesforce Code Analyzer/PMD), Jest and Apex test suites held to an 80% coverage bar, and documented conventions. What it hasn't had is an experienced Salesforce developer's judgment. Part of the value you'd bring early is telling us what we actually have: what's solid, what needs shoring up, and where the real risks are before we build further. The codebase ~40 Apex service classes with a matching test suite, ~90 Lightning Web Components, and 40+ custom objects. Heavy external integration — telephony (RingCentral), e-signature (DocuSign), transactional email (SendGrid), AWS-hosted APIs — via REST callouts with JWT/OAuth, token caching, retries, and idempotency concerns. Significant async Apex (Queueable, Batchable, Schedulable) written with governor limits in mind. Roughly half the codebase is integration code — if callout reliability is your kind of problem, there's plenty here. What you'll do - First engagement: a paid codebase health review. Give us an honest, written read on test quality, security posture (sharing model, FLS/CRUD, injection safety), and governor-limit safety — what to fix now vs. later. This is also how we both confirm the fit before ongoing work. - Then ongoing: build and extend LWCs and the Apex services behind them, write and maintain integration code, and write tests alongside your changes (Apex unit tests and LWC Jest). What we're looking for - Solid Apex with good governor-limit instincts (bulkification, no SOQL/DML in loops), including Queueable/Batchable async patterns. - Real Lightning Web Component experience (modern LWC, not Aura). - A genuine testing habit — you write tests as you go, mock HTTP callouts, and are comfortable in Jest. - Security awareness: sharing model, injection-safe SOQL, FLS/CRUD. This matters more than usual here — it's healthcare data and the existing patterns are unverified. - Comfort working independently and making sound judgment calls. You'd be the final word on Salesforce engineering quality — supported by the automated quality gates, but without a senior human reviewer above you. Nice to have: managed-package/ISV experience (the app is packaged for AppExchange, so permission sets — not profiles — carry FLS); deeper REST integration background (pagination, backoff, reconciliation jobs); exposure to DocuSign, RingCentral, SendGrid, or AWS API Gateway/Lambda; prior work in a regulated or compliance-sensitive domain. How we work You'd work directly with the project's owner, who knows the product and domain deeply but is not a career developer. You set the Salesforce engineering direction with their full support; expect fast decisions, real context, and no layers of process between you and the work. Logistics - Engagement: hourly / part-time, ongoing (after the initial review) - Estimated hours: 10-20 hrs/week - Time zone overlap: US Central Time How to apply Please include: 1. A short note on your Salesforce experience (Apex + LWC), ideally with one example of an integration-heavy or async-heavy project you built and what made t hard. 2. Links to verifiable work — GitHub, AppExchange listings, Trailhead, certifications. References welcome. 3. In 150 words or fewer: given what you've read — AI-built, unvalidated by a Salesforce expert, healthcare domain — where would you start your first review of this codebase, and what specifically would you look for first? Specific beats comprehensive; we read these carefully.