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 Durham demand, clients, or candidate supply.
Sourced life sciences and health care context
Research, care, and regulated records: Salesforce Developer
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. 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. 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: Review a redacted Apex or Lightning example and ask about limits, security, testing, and maintainability. 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: Salesforce Developer
The Durham report also identifies information technology as a high-demand industry in the city's workforce and business-support work. Define integration volume, direction, authentication, and failure handling. Require evidence from APIs, events, middleware, or batch interfaces comparable to the opening. 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 an integration exercise with duplicate events, retries, access failure, and partial processing. 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: Salesforce Developer
Advanced manufacturing is another high-demand industry named in Durham's FY 2025 impact report and related workforce alignment activity. Set code-quality and release expectations. Candidates should discuss bulk behavior, governor limits, test design, deployment dependencies, data fixes, and monitoring after release. 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 a release defect with the failing test or signal, root cause, repair, and prevention added to the pipeline. Trace the product from released design and sourced material through equipment, production, inspection, traceability, inventory, shipment, variance, and accountable process owner.