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 Tampa demand, clients, or candidate supply.
Sourced life sciences and health care context
Clinical, research, and regulated operations: LLM Engineer
The City of Tampa's Resilient Tampa strategy names life sciences and health care among the growth industries targeted through regional economic-development work. 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. Health-related systems can join patient or research data, service delivery, laboratories, billing, workforce, compliance, access reviews, and uptime requirements under several process owners.
Evidence to request: Request an evaluation set, retrieval diagram, or redacted design note that shows how the candidate tested grounding and access boundaries. Set the care, research, product, or administrative boundary, record authority, protected data, integration path, access controls, validation need, downtime limit, and reviewer.
Sourced financial and professional services context
Client, transaction, and reporting systems: LLM Engineer
Resilient Tampa also identifies financial and professional services as a growth cluster for business attraction and workforce coordination. 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. Financial and client-service work may involve accounts, contracts, transactions, advice, approvals, regulated records, time entry, billing, reporting, and evidence for review.
Evidence to request: Use a design exercise with a fixed quality target and cost limit. Score the tradeoffs, measurement plan, and fallback behavior. Name the service and customer, transaction or case lifecycle, system of record, control owner, approval chain, reporting deadline, data rights, and acceptance evidence.
Sourced logistics and distribution context
Orders, freight, and warehouse flow: LLM Engineer
The Tampa strategy includes logistics and distribution among the clusters used to diversify the city's economic base. 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. Distribution systems must align orders, inventory, warehouses, ports, carriers, status events, exceptions, customer commitments, and billing while goods remain in motion.
Evidence to request: Ask for an incident or regression account with the signal, diagnosis, change, and post-release check the candidate owned. Map the order and shipment lifecycle, facilities, partner messages, volume peaks, event timing, exception queue, reconciliation, recovery target, and after-hours owner.