Solution Architect: Business Systems Integration; Strategic Orchestrator

Location

This role is based in Woodinville, WA and requires you to work onsite 4 days per week, with 1 day remote. To be considered, you must live within commuting distance, as regular in‑person collaboration is a key part of the role.

We are seeking a Solution Architect who acts as the primary connective tissue between business vision and operational reality. In this role, you are a Strategic Orchestrator.

• 7+ years in a Solution Architecture or Lead Systems Integration role.
• Expertise in Enterprise Integration Patterns (EIP) and orchestrating data across complex SaaS and legacy landscapes.
• Experience in eCommerce or Omnichannel Retail where front‑end experience and back‑office fulfillment are deeply intertwined.
• Exceptional communication and negotiation skills—you are comfortable challenging a Product Manager’s “What” and a Technical Architect’s “How.”

• API Ecosystem Management:
  Proficiency in designing and governing RESTful APIs, Graph
  
  QL, and Webhooks with a focus on versioning and backward compatibility.
• ECommerce & ERP Ecosystems:
  Hands‑on experience with the “Order‑to‑Cash” lifecycle, connecting front‑end platforms (e.g., Shopify, Salesforce, Magento) to back‑office systems (e.g., Net Suite, SAP, Oracle).
• Observability & Monitoring Design:
  Skill in architecting “health dashboards” using tools like Datadog or New Relic to track data flow across systems.
• Data Mapping & Governance:
  Expert‑level data modeling to ensure consistency between high‑speed web databases and structured financial ledgers.
• Middleware Mastery:
  Advanced configuration and design experience with iPaaS platforms (e.g., Mule Soft, Boomi, Workato, or Azure Service Bus).
• Cross‑Functional Solution Design:
  The ability to facilitate “Discovery Workshops” that align Product roadmaps with back‑office technical constraints.
• Operational Readiness Planning:
  Skill in defining Non‑Functional Requirements (NFRs)—specifically scalability, maintainability, and “supportability” (how easily a non‑engineer can troubleshoot an issue).
• Incident Post‑Mortem Leadership:
  Capability to lead root‑cause analysis across teams when a complex, multi‑system integration fails.
• Documentation for “Day 2”:
  Crafting high‑level sequence diagrams and “Source of Truth” maps that BAs and Support teams can use post‑launch.
• Strategic Translation:
  Translating a Product Manager’s “Customer Delight” goal into a Technical Architect’s “Low Latency” requirement.
• Conflict Resolution & Negotiation:
  Balancing the speed‑to‑market needs of the PM with the stability requirements of the Back‑Office team.
• Systems Thinking:
  The ability to visualize and communicate how a small change in the web checkout ripples through inventory, tax, and shipping systems.

• Create current and future state solution documentation.
• Maintain solution documentation, process flows, and system maps to support post‑launch operations.
• Produce and maintain requirement documentation, integration designs, data mappings, internal systems maps, reference architectures.
• Lead discovery sessions to clarify requirements, dependencies, and system impacts.
• Review integration designs, data mappings, and APIs to ensure business and technical alignment.
• Partner across product teams, engineering teams, and operations to resolve blockers and keep delivery on track.
• Identify architectural risks, operational gaps, and cross‑system dependencies early.
• Support incident triage and root‑cause analysis across integrated platforms.

• For Product Managers:
  Validate that their roadmap is technically viable and identify architectural shortcuts or risks to their speed‑to‑market.
• For Business Analysts:
  Transform functional requirements into a cohesive system design that accounts for every downstream impact in the back‑office.
• For Technical Architects:
  Provide high‑level guardrails, ensuring their deep‑dive builds fit into the broader enterprise puzzle.
• For Project Managers:
  Clarify dependencies and sequence integration milestones for predictable delivery.

• Service Design:
  Define the supportability requirements during the design phase…