Staff Enterprise Architect at GitLab | Torre

Staff Enterprise Architect

Emma highlights
This highlight was written by Emma’s AI. Ask Emma to edit it.
Full-time

Legal agreement: Employment

Provide your expected compensation while applying
location_on
Remote (for United States residents)
Remote (for United Kingdom residents)
Remote (for Canada residents)
Remote (for Germany residents)
Shared by
Emma of Torre.ai
2 days ago

Responsibilities


An overview of this roleAs a Staff Enterprise Architect, you will design and evolve how GitLab's internal systems are configured, integrate, perform and scale to support a rapidly growing business. Reporting to the Director, Enterprise Architecture and AI Intelligent Automation, you will apply all four architecture lenses (business, application, data, and technology) to the systems in your scope, treating AI as a standing consideration inside each rather than a separate workstream.Enterprise-wide strategy, portfolio direction, and standards ownership sit with the Director. Your job is depth: turning that direction into designs detailed enough to build, and being the person trusted with the hardest technical problems in the enterprise. You will not manage people. You will lead through architecture, as the partner to our Applications engineering teams and to Integration, RPA, and Intelligent Automation, and as a reviewer on the Architecture Review Board, where the aim is to make architecture an enabler rather than a gate.What you'll doBusiness architectureIn collaboration with product management and process owners, map the current-state processes and capabilities supported by the systems in your scope, tying each capability to its supporting systems, owners, and systems of record, and identify and resolve where those systems create friction, manual handoffs, or duplicated work, including handoffs an AI agent could remove entirely.Architect end-to-end processes that span front-office and back-office systems, including new product introduction, CPQ and quote-to-cash, billing and revenue recognition, renewals, and record-to-report, together with the customer service processes that run alongside them, including case and escalation management, entitlements, and service level commitments, rather than optimizing any one system in isolation.Redesign workflows before automating them, so we aren't encoding broken processes into new tooling. For each step, decide what an AI agent should handle, what deterministic automation should handle, and what stays with a person.Application architectureIn collaboration with the Applications engineering teams, serve as their embedded architect, producing high level designs and patterns for changes to Salesforce, NetSuite, Zuora, Zendesk, and other core platforms. Favor configuration and supported extension patterns over customization, evaluate each platform's native AI before anything bespoke is built, and keep system roadmaps aligned with enterprise standards.Design for maintainability and supportability: clear service ownership, observability and error handling in integrations, documented runbooks, and realistic total cost of ownership.Go deep on the platforms in your scope, staying current on release notes, published limits, API behavior, and known constraints, so designs account for what the platform will actually do rather than what the documentation promises.Govern application change by reviewing significant build proposals, data model changes, and third-party package additions before they are committed, giving teams a clear and timely decision, and keeping platforms on supported versions and ready to upgrade.In collaboration with each domain's technical lead, or the vendor where that is the better source, run quarterly health checks on Salesforce, NetSuite, Zuora, Zendesk, and Workato, measuring customization footprint against each platform's published ceilings for API and governor limits, automation, storage, transaction and ticket volumes, AI consumption, and licenses. Publish a report card showing