Hiring brief scenarios
Build the SAP Basis 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 Austin demand, clients, or candidate supply.
Sourced semiconductors and microelectronics context
Semiconductor design and production: SAP Basis
The City of Austin's May 2026 policy draft identifies semiconductors and microelectronics as a target sector and links the sector to local research, state programs, and federal investment. The document names design, manufacturing, and supply-chain activity as parts of the cluster. Map the operating setting to system sizing, landscape separation, identity, network paths, high availability, and recovery objectives. Ask the engineer to explain the limits that drove the design. Semiconductor work can combine factory systems, engineering data, long equipment lifecycles, and strict production change windows.
Evidence to request: Review a landscape diagram and ask for sizing, isolation, identity, network, availability, and recovery decisions. Separate experience with corporate software from experience inside design, test, fabrication, or equipment operations.
Sourced life sciences and health innovation context
Clinical and research operations: SAP Basis
Austin's 2026 policy draft lists life sciences and health innovation as a target sector. It points to diagnostics, biotechnology, health technology, and the research and clinical institutions that support those activities. Define ownership for kernels, support packages, upgrades, transports, certificates, interfaces, and database maintenance. Require evidence from a controlled production change. Research and clinical products can require reproducible analysis, controlled data access, validation records, and review by nontechnical subject experts.
Evidence to request: Use an upgrade or transport scenario with prerequisites, testing, downtime, communication, fallback, and evidence capture. Document whether the role supports research, a regulated product, clinical operations, or an internal business system because each path changes the proof required.
Sourced mobility and infrastructure technology context
Infrastructure program delivery: SAP Basis
The Austin policy draft treats mobility and infrastructure technology as a sector connected to I-35, Project Connect, airport expansion, and water infrastructure. It describes a regional investment cycle with construction, technology, utilities, and smart-city work. Set the incident and continuity boundary. Candidates should cover alerting, work processes, dumps, locks, jobs, capacity, backups, failover, vendor escalation, and post-incident checks. Infrastructure programs join field schedules, public procurement, asset data, and systems that must remain available during phased delivery.
Evidence to request: Ask for a production incident the engineer diagnosed, including signals, commands, recovery, business communication, and preventive work. Identify the asset, operating agency, implementation phase, and outage tolerance before deciding whether industry experience is required.