Sourced auto, mobility, and advanced manufacturing context
Vehicles, factories, and connected operations: Salesforce Architect
Detroit's economic development budget report identifies auto and mobility together with advanced manufacturing as a priority sector. Its project examples span automotive components, fuel cells, clean-energy manufacturing, and vehicle software. Tie the operating scenario to domain boundaries and record ownership. Ask how the architect would divide standard objects, custom objects, external data, identity, and reporting across the platform. Vehicle and factory work may connect engineering definitions, production schedules, equipment, parts, quality, suppliers, software releases, logistics, dealers, service, and finance records across long product lifecycles.
Evidence to request: Use a domain-model and sharing exercise with conflicting business-unit requirements and a stated system of record. Set the vehicle, component, plant, or mobility boundary, then trace engineering changes through production, quality, delivery, service, and accounting with system authorities and outage limits.
Sourced research, engineering, and design context
Requirements, models, prototypes, and releases: Salesforce Architect
The same Detroit report names research, engineering, and design as a sector for focused business-attraction work. Define the integration portfolio and nonfunctional limits. Candidates should compare synchronous, event, batch, and middleware patterns against volume, latency, failure recovery, and support ownership. Engineering delivery can cross requirements, models, simulations, prototypes, test results, parts, software, intellectual property, changes, and release records owned by separate product and manufacturing groups.
Evidence to request: Review an architecture decision record for an integration choice, including rejected options and operating consequences. Define the engineering artifact, authoring and release systems, configuration baseline, test evidence, change authority, supplier access, retention rule, and handoff into production.
Sourced clean energy and sustainability context
Energy assets, performance, and reporting: Salesforce Architect
Detroit's current economic development focus also includes clean energy and sustainability, and the report lists energy technology and manufacturing among recent project examples. Set governance around customization, security, releases, and technical debt. Require a decision process that product owners and delivery teams can use after the architect leaves. Energy work can join physical assets, meters, forecasts, maintenance, production, contracts, incentives, emissions measures, financial postings, and external reporting with different calculation owners.
Evidence to request: Ask for a governance mechanism the architect introduced and evidence that teams used it to make or reverse a design decision. Name the assets and energy process, source measurements, calculation method, reporting boundary, contract or incentive rules, maintenance window, reconciliation, and approval evidence.