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 Durham demand, clients, or candidate supply.
Sourced life sciences and health care context
Research, care, and regulated records: LLM Engineer
Durham's FY 2025 Strategic Plan Impact Report identifies life sciences and health care as high-demand industries used to align workforce programs and employer engagement. 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. Life-sciences and care platforms may join research samples, clinical records, laboratory instruments, trials, patient access, quality events, validation, and regulated retention.
Evidence to request: Request an evaluation set, retrieval diagram, or redacted design note that shows how the candidate tested grounding and access boundaries. Define the research or care workflow, sample or patient identity, protected fields, instrument or clinical interface, validation evidence, quality gate, retention rule, and approval owner.
Sourced information technology context
Product, data, and service boundaries: LLM Engineer
The Durham report also identifies information technology as a high-demand industry in the city's workforce and business-support work. 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. Information-technology roles can sit in product engineering, enterprise applications, data platforms, security, managed services, or public systems with different delivery evidence.
Evidence to request: Use a design exercise with a fixed quality target and cost limit. Score the tradeoffs, measurement plan, and fallback behavior. State the product or service boundary, users, data ownership, production authority, integration surface, reliability target, release evidence, and after-launch responsibility.
Sourced advanced manufacturing context
Production, quality, and supply flow: LLM Engineer
Advanced manufacturing is another high-demand industry named in Durham's FY 2025 impact report and related workforce alignment activity. 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. Advanced production can connect designs, bills of material, suppliers, equipment, work orders, quality results, serial or lot records, inventory, maintenance, and cost.
Evidence to request: Ask for an incident or regression account with the signal, diagnosis, change, and post-release check the candidate owned. Trace the product from released design and sourced material through equipment, production, inspection, traceability, inventory, shipment, variance, and accountable process owner.