Hiring brief scenarios
Build the Salesforce Architect brief around the work.
These scenarios connect location context to role responsibilities. Use them as prompts to verify with the employer, not as measures of San Jose demand, clients, or candidate supply.
Sourced artificial intelligence and software context
Models, products, and production services: Salesforce Architect
The City of San Jose identifies artificial intelligence as a priority growth sector and includes AI training and job-matching programs in its fiscal year 2025 to 2026 economic plan. 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. AI product work can join source data, models, application code, evaluation, user feedback, cost controls, access rules, and production support under separate owners.
Evidence to request: Use a domain-model and sharing exercise with conflicting business-unit requirements and a stated system of record. Define the user decision, model boundary, source data, evaluation set, deployment path, access control, cost target, failure response, and approving product owner.
Sourced semiconductors and advanced manufacturing context
Engineering, fabrication, and supply controls: Salesforce Architect
A July 2025 City of San Jose economic-development release names advanced manufacturing and semiconductors among the industries the city plans to attract, retain, and grow. Define the integration portfolio and nonfunctional limits. Candidates should compare synchronous, event, batch, and middleware patterns against volume, latency, failure recovery, and support ownership. Semiconductor and manufacturing programs may connect product definitions, equipment, process recipes, production schedules, quality results, suppliers, inventory, maintenance, and cost records.
Evidence to request: Review an architecture decision record for an integration choice, including rejected options and operating consequences. Set the design or plant boundary, product revision, process control, equipment interface, traceability unit, quality release, supplier handoff, change window, and support owner.
Sourced data centers and energy infrastructure context
Capacity, continuity, and facility operations: Salesforce Architect
San Jose's July 2026 large energy-use project page distinguishes data centers from research laboratories, advanced manufacturing sites, electric-vehicle charging hubs, and other power-intensive facilities. 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. These facilities can combine power, cooling, networks, physical security, capacity, asset maintenance, environmental controls, backup systems, and tenant or workload commitments.
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 facility and workload boundary, capacity unit, power and cooling dependencies, availability target, access model, maintenance path, recovery test, and change authority.