Sourced government-connected technology context
Controlled delivery and contract boundaries: SAP Basis
The Washington DC Economic Partnership connects the District's technology sector with government agencies, private contractors, established companies, and startups. 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. Government-connected systems may separate environments and organizations while adding procurement limits, accessibility requirements, approval records, fixed release windows, and contract handoffs.
Evidence to request: Review a landscape diagram and ask for sizing, isolation, identity, network, availability, and recovery decisions. Document the agency or customer boundary, hosting model, system owner, approval path, maintenance window, evidence retention, and transfer between teams.
Sourced cybersecurity context
Identity, sensitive data, and audit evidence: SAP Basis
The partnership identifies cybersecurity as a central part of Washington's technology sector and connects the field to agencies and contractors. Define ownership for kernels, support packages, upgrades, transports, certificates, interfaces, and database maintenance. Require evidence from a controlled production change. Security-sensitive work can require controlled identities, least-privilege access, protected data, artifact provenance, vulnerability handling, incident records, and proof of each production change.
Evidence to request: Use an upgrade or transport scenario with prerequisites, testing, downtime, communication, fallback, and evidence capture. Name the identity authority, sensitive records, access-review owner, security gates, emergency path, retained logs, and remediation deadline attached to the system.
Sourced artificial intelligence context
Model, data, and service governance: SAP Basis
Artificial intelligence appears as a named focus within the partnership's technology profile for Washington. Set the incident and continuity boundary. Candidates should cover alerting, work processes, dumps, locks, jobs, capacity, backups, failover, vendor escalation, and post-incident checks. AI-enabled services can add model artifacts, source-data permissions, evaluation gates, cost limits, human review, monitoring, and rollback decisions to an existing business process.
Evidence to request: Ask for a production incident the engineer diagnosed, including signals, commands, recovery, business communication, and preventive work. Clarify whether the role owns the business workflow, source data, model service, integration, evaluation, access control, monitoring, or incident response.