Salesforce Architect

Job Title: Senior Salesforce Solution Architect
Engagement Duration: 8 to 9 Weeks at 40 hours per week
Location: Remote but must be in the United States
Start Date: May 4, 2026
End Date: The solution must be turned over to Customer no later than July 1, 2026

Engagement Context

A FOCI-mitigated subsidiary is being stood up from a parent organization to comply with U.S. defense-industrial regulations. A defense-relevant subset of the parent's Salesforce footprint must be migrated into a new Salesforce Government Cloud Plus (GC+) environment, with legacy Salesforce CPQ refactored into Revenue Cloud, by July 1, 2026 (firm) . The contractor will own end-to-end delivery for an initial user base of approximately 20 internal users on a simplified, flat security model. This is not a portal build and not a customer-facing Experience Cloud engagement.

What You'll Own

You will perform all five delivery phases — Discovery, Design & Build, Migration & Validation, UAT & Cutover, and Closeout — as the single accountable architect.

• Lead a Customer-approved discovery covering the parent org's objects, fields, metadata, automations, products, pricing, and CPQ logic; produce a defensible scope baseline and migration plan.
• Stand up the target Salesforce GC+ environment (sandbox + production), including a flat security model using standard Profiles to the maximum extent practical, with two to three custom Permission Sets for Revenue Cloud, PSA, and other Customer-approved restricted access.
• Refactor Customer-approved legacy CPQ data structures, logic, and supporting processes into Revenue Cloud, including Quote and Order document templates.
• Migrate Customer-approved objects, fields, accounts, related records, product catalog, and Price Book Entries into the target org. Implementation is single-currency (USD), single-region (United States), Standard Price Book.
• Identify, assess, migrate, and validate Customer-approved Apex, Flows, workflow rules, and validation rules. Automation migration is expected to be minimal.
• Design and implement a custom data structure to store, manage, and associate license keys and license files with customer entitlements (the customer-facing portal that consumes these is a separate, third-party effort and is out of scope for this role ).
• Execute migration testing, reconciliation, and validation. Support Customer-led UAT (the Customer drives UAT; you remediate defects).
• Plan and execute production cutover; provide week-one hypercare; deliver architecture documentation, configuration documentation, and admin handoff.

Mandatory Qualifications

• Continental United States (CONUS) residency. All work performed within CONUS on compliant hardware.
• Salesforce Government Cloud Plus hands-on experience. Direct experience with GC+ feature lag, AppExchange package gaps, and FedRAMP Moderate / GCC High data-plane constraints on tooling.
• Revenue Cloud delivery experience — Product Selling Models, Pricing Procedures, Product Related Components, quote-to-order flow. Not legacy CPQ-only experience.
• Legacy Salesforce CPQ working knowledge sufficient to refactor existing CPQ logic into Revenue Cloud. You must understand both sides of the line.
• Salesforce data migration at production scale using compliance-acceptable tooling (sfdx / Salesforce CLI, direct REST/Bulk API approaches, Copado GovCloud or equivalent FedRAMP-Moderate-compliant deployment tools). Familiarity with what tools you cannot use in a GC+ data plane is as important as what you can.
• Apex, Flow, and metadata management to a senior level.
• End-to-end SOW delivery accountability as the lead architect on at least one prior engagement of comparable shape (multi-phase, fixed-deadline, single-architect-led).
• Salesforce Certifications: Application Architect or System Architect required. Platform Developer II strongly preferred. Revenue Cloud Accredited Professional or equivalent demonstrable Revenue Cloud delivery experience required.

Strongly Preferred

• M&A or divestiture-driven Salesforce migration experience (carve-outs, source-to-target object/data filtering against a parent org).
• FOCI-mitigated subsidiary or NISPOM-adjacent program experience.
• Familiarity with Salesforce PSA / FinancialForce / Certinia (referenced in the Permission Set scope).
• Experience producing migration validation and reconciliation evidence acceptable to a defense-customer compliance reviewer.

Engagement Parameters

• Engagement type: Fixed-scope SOW; estimated 320 hours total LOE across all five phases.
• Duration: Approximately 9 weeks from kickoff to production cutover. Production readiness no later than July 1, 2026.
• Allocation: Full-time across the engagement.
• Reporting: To the Arganteal engagement lead; primary client interface with the FOCI-mitigated Customer, with coordination touchpoints to the parent organization on source-system access and approvals.
• Travel: None but you must be located within the United States.

Hard Constraints (Non-Negotiable)

• All personnel must be residing and performing work within the United States
• All customer data, transactional data, migration extracts, staging data, and backups must remain within the United States and within Customer-approved environments at all times.
• Migration tooling for live business data must operate within a FedRAMP Moderate or GCC High compliant data plane, or use Customer-approved temporary direct API access. No live customer or transactional data may be processed, transmitted, staged, or stored in a non-authorized environment.
• SaaS-based metadata deployment tools are permitted for configuration migration (XML metadata, Apex, Flow definitions) provided they do not process or store live customer or transactional data.

How Success Is Measured

• A production Salesforce GC+ environment containing the Customer-approved migrated data set, required product and pricing structures, approved security model, migrated and validated business functionality, and the operational capability to support assumed contracts and initiate new sales activities — operational on or before July 1, 2026 .
• Successful data reconciliation within agreed tolerance thresholds, validated security model, and Customer-signed acceptance of all eight contracted deliverables.