Hiring brief scenarios
Build the Salesforce Developer 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 Developer
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. Map the local business process to objects, sharing, automation, and user experience. Ask the developer to explain where code is justified and where platform configuration produces a safer result. 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: Review a redacted Apex or Lightning example and ask about limits, security, testing, and maintainability. 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 Developer
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 integration volume, direction, authentication, and failure handling. Require evidence from APIs, events, middleware, or batch interfaces comparable to the opening. 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: Use an integration exercise with duplicate events, retries, access failure, and partial processing. 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 Developer
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 code-quality and release expectations. Candidates should discuss bulk behavior, governor limits, test design, deployment dependencies, data fixes, and monitoring after release. 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 release defect with the failing test or signal, root cause, repair, and prevention added to the pipeline. Name the sector, record type, regulated boundary, system of record, control owner, change authority, and evidence required for acceptance.