Principal Business Systems Architect

Commerce

7d•$164,000 - $228,000•Remote

About The Position

Commerce is seeking a Principal Business Systems Architect to serve as the senior-most individual-contributor technical role in the Business Systems organization. The position is the final architectural authority across CRM, billing, and integration systems and the technical counterpart to stakeholders in Go to Market, Finance, and Marketing. The architect will work across Salesforce, Marketo, Zuora, and the integration layer to shape a coherent architecture from a complex, highly customized systems landscape. The role sets the target-state architecture that other teams build against, while those teams own delivery. It includes defining and maintaining architecture across Business Applications, translating it into a sequenced and fundable roadmap, and leading legacy modernization, including SFDC Legacy decommissioning and migration of Zuora integration ownership into Salesforce Lightning. The architect evaluates major platform decisions, creates solution designs and build specifications, and collaborates with developers and administrators during implementation. Success requires listening carefully to stakeholders, clarifying the underlying problem, and translating pain points into prioritized technical requirements. The architect resolves cross-system design disagreements and communicates tradeoffs related to scalability, security, cost, and maintainability. They also maintain current system diagrams, integration maps, and decision records. Commerce is a remote-first company. Team members in Austin, Atlanta, and London may use optional collaborative workspaces for gatherings, workshops, and in-person collaboration. Compensation includes a national base salary range of $164,000 to $228,000. Depending on local policies, the role may also be eligible for variable compensation, equity, and benefits; details are shared during the hiring process.

Requirements

10+ years in enterprise architecture, solutions architecture, or a senior technical individual-contributor leadership role.
Experience spanning CRM and billing/ERP systems rather than specializing in only one system.
Experience with GTM/revenue systems such as Salesforce or HubSpot, CPQ, quote-to-cash, and order-to-revenue flows.
Proven experience leading legacy system modernization or decommissioning at scale, including managing risk and sequencing migration.
Demonstrated experience acting as a final technical authority, while remaining open to better information and changing course when appropriate.
Strong written communication skills and ability to document complex technical tradeoffs clearly.
Ability to learn new platforms quickly and work within a standardize-first review process, including obtaining VP of Technology sign-off for customization decisions.
Strong communication, conflict-management, consensus-building, and stakeholder-listening skills.

Nice To Haves

Experience with Zuora or a comparable billing/subscription platform.
Experience standing up or scaling AI-assisted engineering tooling.
Prior experience at a company of similar scale and complexity managing multiple platforms and actively modernizing legacy systems.

Responsibilities

Define and maintain target-state architecture across Business Applications, including CRM, billing, Marketing Ops, Revenue, and the integration/middleware layer.
Translate target-state architecture into a sequenced, fundable roadmap.
Serve as the final architectural authority for cross-system design decisions and resolve disagreements using considerations such as scalability, security, cost, and maintainability.
Lead legacy modernization strategy, including SFDC Legacy decommissioning and migration of Zuora integration ownership into Salesforce Lightning.
Conduct technical due diligence on major platform decisions, including whether to build, buy, retire, or replatform.
Partner with stakeholders to understand pain points and convert them into prioritized technical requirements.
Create solution designs and build specifications for developers and administrators, and support them during implementation.
Own technical strategy for legacy decommissioning, modernization of integrations and workflows, and migration sequencing and follow-through.
Maintain architecture documentation, including system diagrams, integration maps, and decision records.
Communicate technical tradeoffs, manage conflict, drive consensus, and respectfully push back when requests do not fit the architecture.