Salesforce Architect

Axiom Strategic Consulting•Sarasota, FL

5d•Onsite

About The Position

Roofing by Curry is seeking a Salesforce Architect to bring their Salesforce platform fully in-house. This role will own the platform from the ground up, completing what exists, designing what comes next, and building a scalable platform for years to come without technical debt. The vision is to build a single, unified Salesforce platform where one customer record sits at the center of everything, supporting multiple service lines like roofing, windows, HVAC, and electrical. The Salesforce Architect will be a senior, hands-on leadership role, reporting directly to ownership. This is a role that involves designing and building, not just strategy, with accountability for delivery and leaving behind a maintainable platform for the internal team.

Requirements

5+ years of Salesforce architecture or senior development experience
Demonstrated experience designing multi-object, multi-business-line Salesforce data models
Hands-on experience inheriting and extending an existing Salesforce org (not only greenfield builds)
Proficiency in Apex, Lightning Web Components, and declarative automation (Flow, Approval Processes)
Field Service Lightning experience - essential for multi-trade crew scheduling and dispatch
Experience designing Salesforce integrations with third-party platforms via REST/SOAP APIs
Strong documentation discipline - you build platforms others can understand and maintain
Salesforce Certified Administrator and Platform Developer I - minimum

Nice To Haves

Salesforce Field Service Lightning Consultant certification
Salesforce Sales Cloud Consultant certification
Experience in residential home services, construction, or a trade services company
Experience building a unified customer record across multiple service or product lines
Salesforce Application Architect or System Architect certification
Experience transitioning a platform from an external implementation partner to internal ownership

Responsibilities

Design and own the unified data model that supports a single customer record across all current and future service lines.
Establish the record type, object, and pipeline framework that allows each new service to be added as a configured extension, not requiring a separate build.
Define the org's long-term technical governance standards: naming conventions, field usage, automation layering, and development practices.
Document the full architecture in a living technical reference that the internal team can use and maintain.
Evaluate the existing build, identify technical debt, and develop a remediation plan that does not disrupt live operations.
Finalize the commercial record type pipeline: record types, minor adjustments to fields, page layouts, and flows from Bidding through Closed Won.
Complete phase and milestone tracking, change order workflows, and progress billing tied to project phases.
Implement Field Service Lightning to accommodate adjustments from existing FSL work types.
Design and document the service line expansion framework for additional lines of home services so that windows & doors, HVAC, and electrical can each be added without architectural rework.
Build shared customer record structures that unify cross-service history, communication, and reporting.
Ensure separate service line pipelines, crew types, pricing models, and job types coexist in a single org without conflict.
Ensure ownership reporting rolls up across all service lines into a single business-wide view.
Write and maintain Apex triggers, classes, and batch jobs for business logic that cannot be handled declaratively.
Build Lightning Web Components for custom UI where native Salesforce falls short.
Design and implement complex Flow automations, approval processes, and escalation rules.
Maintain clean separation between declarative and programmatic layers to preserve long-term maintainability.
Own the integration architecture across all connected systems: QuickBooks, ERP and related integration tools, measurement tools (EagleView, HOVER), photo documentation (CompanyCam), and supplier portals.
Design and implement API-based integrations as new service lines introduce new tooling requirements.
Establish integration standards and documentation so new connections follow a consistent pattern.
Develop admin guides, runbooks, and training documentation for day-to-day platform operation.
Build a platform the internal team can maintain and extend without external dependency.