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 Miami demand, clients, or candidate supply.
Sourced international trade and logistics context
Port, airport, and partner transactions: Salesforce Architect
Miami-Dade County describes international trade as a central part of the local economy and ties that work to PortMiami, Miami International Airport, and the region's trade and logistics organizations. 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. Trade systems can cross carriers, ports, customs, warehouses, customers, currencies, and time zones while goods and financial records move on different schedules.
Evidence to request: Use a domain-model and sharing exercise with conflicting business-unit requirements and a stated system of record. Trace one shipment or trade transaction through partner interfaces, status events, exceptions, financial postings, reconciliation, retention, and support ownership.
Sourced aviation and aerospace context
Flight, maintenance, and controlled operations: Salesforce Architect
Miami-Dade lists aviation and aerospace among the industries sought through its Targeted Jobs Incentive Fund and identifies airport areas among its strategic locations. Define the integration portfolio and nonfunctional limits. Candidates should compare synchronous, event, batch, and middleware patterns against volume, latency, failure recovery, and support ownership. Aviation work may join maintenance, assets, schedules, passengers, cargo, safety controls, secure access, vendors, and finance systems that must stay available during extended operating hours.
Evidence to request: Review an architecture decision record for an integration choice, including rejected options and operating consequences. Identify the flight, cargo, maintenance, airport, or manufacturing boundary, then document uptime, access, audit, interface, and recovery requirements.
Sourced finance, technology, and life sciences context
Regulated records and specialist workflows: Salesforce Architect
The same Miami-Dade incentive program names financial and professional services, information technology, and life sciences among the industries the county seeks to support. 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 sectors can require transaction controls, protected records, validated calculations, model oversight, research traceability, or access reviews, depending on the system and business process.
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 sector, record type, regulated boundary, system of record, control owner, change authority, and evidence required for acceptance.