Tech lead — Salesforce + headless web

Tech lead — Salesforce + headless web*

Time Zone - CST preferred (Remote) , some team member work from PST also

Duration - Long Term

Skills - Salesforce Handson + UI Developer+ Excellent Communication as he will be discussing with requirement , coordination with offshore team , willing to learn new skills

Role

Hands-on technical lead across Salesforce and modern headless web. Partners with Product leadership to translate business needs into complete technical requirements. Writes code, reviews PRs, and fixes bugs on both stacks. Owns the boundary between the two systems - domain split, APIs, SSO, deployment pipelines.

Product partnership

•⁠ ⁠Thinking partner to Product, not an order-taker

•⁠ ⁠Surfaces non-functional requirements (performance, security, observability) Product would not raise on their own

•⁠ ⁠Identifies edge cases, integration constraints, and dependencies before they block development

•⁠ ⁠Partners with product in identifying solutions in case the current asks could be infeasible within a timeline.

•⁠ ⁠Co-authors technical specs and architecture decision records

Hands-on, daily

•⁠ ⁠Provide tech leadership in terms of architecture/set up and engineering

•⁠ ⁠Writes code as needed on both stacks - Salesforce (Apex, LWC) and modern web (React, Next.js, TypeScript)

•⁠ ⁠Reviews PRs from a code review standpoint with substantive feedback on both sides partners with Salesforce lead and web lead on Revance side along with Rsystems development team

•⁠ ⁠Coaches engineers in the moment, debugs across the boundary

Salesforce stack

Apex (triggers, batch, queueable, scheduled, Platform Events) · LWC / LWR · Experience Cloud · Health Cloud · Loyalty Cloud · B2B Commerce (Classic + LWR) · SCAPI · Connect REST · CDC · Gearset

Modern web headless stack

React · Next.js · TypeScript · Node.js · Convex · Tailwind · shadcn/ui · Vercel (edge functions, ISR)

Integration and architecture

•⁠ ⁠Contract-first API design (OpenAPI / GraphQL)

•⁠ ⁠BFF patterns, caching strategy, latency budgets

•⁠ ⁠SAML / OAuth / OIDC - Salesforce Community Cloud as IdP for external apps

•⁠ ⁠Hybrid architecture: Salesforce as system of record behind a non-Salesforce frontend

•⁠ ⁠Migration patterns: strangler fig, parallel run, feature-flagged cutover

Delivery

•⁠ ⁠Git workflows, CI/CD on both stacks (Gearset for SF, Vercel / GitHub Actions for web)

•⁠ ⁠AI-assisted development (Claude / Copilot / agentic coding) as part of daily flow

Operating mode

•⁠ ⁠Onsite or US time-zone overlap

•⁠ ⁠Hands-on, daily, in the code

•⁠ ⁠Active partner to Product in grooming, planning, and roadmap