Sourced mobility context
Aerospace, automotive, logistics, and manufacturing: Salesforce Developer
The City of San Antonio's economic-development framework defines mobility through aerospace, automotive, logistics, and manufacturing activity. 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. Mobility programs may connect engineering definitions, vehicles or aircraft, parts, plants, quality, maintenance, suppliers, warehouses, field assets, service, and cost records.
Evidence to request: Review a redacted Apex or Lightning example and ask about limits, security, testing, and maintainability. Set the product and program boundary, configuration baseline, facility, production method, traceability rule, quality release, logistics handoff, service model, and change authority.
Sourced it security and infrastructure context
Cyber operations, hosting, and protected systems: Salesforce Developer
San Antonio's framework identifies IT security and infrastructure as a strategic cluster connected to cybersecurity, technology, aerospace, defense, and military operations. Define integration volume, direction, authentication, and failure handling. Require evidence from APIs, events, middleware, or batch interfaces comparable to the opening. Secure infrastructure work can involve identity, cloud and hosted services, networks, classified or controlled data, monitoring, incident response, change records, and continuity duties.
Evidence to request: Use an integration exercise with duplicate events, retries, access failure, and partial processing. Name the service, data classification, identity authority, trust boundary, control framework, alert and response path, evidence retention, recovery objective, and approving security owner.
Sourced bioscience anchors and catalysts context
Health, laboratory, and research operations: Salesforce Developer
The San Antonio framework defines a bioscience cluster that includes health care, higher education, research and development, and defense or military medicine. Set code-quality and release expectations. Candidates should discuss bulk behavior, governor limits, test design, deployment dependencies, data fixes, and monitoring after release. Bioscience and medical work may join patient care, research data, specimens, devices, laboratories, validated products, access controls, billing, workforce, and quality review.
Evidence to request: Ask for a release defect with the failing test or signal, root cause, repair, and prevention added to the pipeline. Define the care, study, product, or enterprise process, regulated boundary, source record, validation protocol, device or lab interface, access rules, retention, and reviewer.