Software Architect (Fullstack, Salesforce)

Hands-On Software Architect

A senior engineer who designs the system and writes the hardest code in it.

\n
• Designs the three-layer architecture (Salesforce Azure portal/mobile) and personally builds the core of it.
\n
• Owns the trickiest integrations and the parts no one else can do yet leads from the codebase, not from a deck.
\n
• Makes and defends build-vs-buy calls (portal product vs. Salesforce Experience Cloud vs. custom) with real cost/time/control reasoning.
\n
• Sets standards by doing: repos, CI/CD, code review, tests, secure coding, and documentation that survives the author leaving.
\n
• Mentors the Senior Engineer through code, not just meetings.
\n
• Expect roughly 60 70% of their time writing/reviewing code, the rest on design and direction. A candidate who wants to stop coding is wrong for this role.
\n

Requirements:

\n
• Currently hands-on and want to stay hands-on. Recent shipped code is required.
\n
• At least two production languages. "React" is a JavaScript/TypeScript framework, not a separate language the real bar is JavaScript/TypeScript plus Python (Apex a strong bonus). One language pass.
\n
• Built front end, back end, and database genuinely full-stack.
\n
• Salesforce Experience.
\n
• Hands on Work on Cloud (AWS, Azure, etc.)
\n
• Shipped at least one product to real external customers.
\n
• Git, CI/CD, and a documentation habit.
\n

Tech environment

Layer

Stack

Frontend

React / TypeScript; responsive web; mobile (React Native or Flutter)

Backend

Python and/or Node; REST APIs; integration/orchestration services

Data

Salesforce as system of record; Azure data/SQL layer; reporting (Power BI)

Cloud

Azure App Service, Functions, Storage/SQL, API Management, Key Vault, Entra (broker/borrower auth)

Salesforce

Apex, Lightning Web Components, Experience Cloud, REST/Bulk APIs, Platform Events

AI

Azure OpenAI / LLM integration, document automation, Copilot/Agentforce-style features

Security

SOC 2 / GLBA context; secure coding; OWASP awareness (financial + HNW client data)

Ways of working

Git, CI/CD, infrastructure-as-code, code review, written design docs

Must-have / Strong-plus / Nice-to-have

Must-have

\n
• Hands-on now; recent production code; wants to keep coding
\n
• 2+ production languages incl. JS/TS + Python (or equivalent)
\n
• Full-stack: front end + back end + database, demonstrably
\n
• Azure (or transferable cloud) with named services , not "I've used cloud"
\n
• Shipped to real external users
\n
• Distributed/scale awareness (services talking to each other, queues, async, reliability)
\n

Strong-plus

\n
• Salesforce depth (Apex / LWC / Experience Cloud / integrations) the differentiator for the Architect
\n
• Mobile shipped to an app store
\n
• AI/LLM feature work
\n
• Fintech / lending / regulated-data experience
\n

Nice-to-have

\n
• Power BI / data-viz
\n
• IaC (Bicep/Terraform), containers
\n
• Insurance or premium-finance domain exposure
\n