Hiring brief scenarios
Build the LLM Engineer 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: LLM Engineer
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. Connect the local operating context to the data that may enter prompts or retrieval. Require a candidate to explain document preparation, permissions, citation behavior, evaluation cases, and the team that approves changes. 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: Request an evaluation set, retrieval diagram, or redacted design note that shows how the candidate tested grounding and access boundaries. 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: LLM Engineer
Miami-Dade lists aviation and aerospace among the industries sought through its Targeted Jobs Incentive Fund and identifies airport areas among its strategic locations. Set the model-selection decision around the workload rather than a preferred vendor. Ask how the engineer compared hosted and open models, measured quality, handled unsafe output, and controlled latency or token cost. 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 a design exercise with a fixed quality target and cost limit. Score the tradeoffs, measurement plan, and fallback behavior. 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: LLM Engineer
The same Miami-Dade incentive program names financial and professional services, information technology, and life sciences among the industries the county seeks to support. Treat launch support as part of the role. The brief should cover observability, feedback review, version changes, rollback, and ownership when retrieval or model behavior produces a poor result. 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 an incident or regression account with the signal, diagnosis, change, and post-release check the candidate owned. Name the sector, record type, regulated boundary, system of record, control owner, change authority, and evidence required for acceptance.