Sourced cybersecurity and technology context
Secure services, identity, and technical products: DevOps Engineer
Baltimore Together tracks technology as a city growth area and calls for stronger connections between employers, students, and Baltimore's software, data, digital-transformation, and information businesses. Connect the operating context to release risk. Ask how the engineer would design tests, approvals, and deployment stages for systems with the stated data and availability constraints. Cybersecurity work can cross identity, networks, cloud services, endpoints, protected data, incident response, audit records, and restricted facilities or contracts.
Evidence to request: Review a pipeline change with test gates, artifact handling, deployment strategy, and measured effect on release safety. Define the protected service, threat and compliance boundary, user population, data classification, control owner, alert path, evidence retention, response authority, and recovery test.
Sourced life sciences context
Research, medical products, and health systems: DevOps Engineer
Baltimore Together's economic-development strategy sets a city objective to lead in life sciences and medical devices. Set the infrastructure-as-code boundary across accounts, networks, compute, identity, and managed services. Require a plan for state, review, drift, and recovery. Life-sciences delivery may join experiments, clinical work, medical devices, laboratories, quality systems, protected records, manufacturing, and commercial operations with formal traceability.
Evidence to request: Use an infrastructure pull request or redacted module design to assess structure, secrets handling, state, and rollback. Set the research or product stage, regulated boundary, source records, validation method, device or laboratory interfaces, access model, release authority, and reviewer.
Sourced manufacturing and logistics context
Port, production, and distribution operations: DevOps Engineer
Baltimore Together tracks industrial, manufacturing, and logistics work as a distinct part of the city's economic-development strategy. Define incident responsibility before hiring. Candidates should show how they used logs, metrics, traces, and change history to restore service and prevent recurrence. Port and factory systems can connect engineering changes, production, quality, inventory, freight, customs, carriers, maintenance, exceptions, and financial settlement across organizations.
Evidence to request: Ask for an incident timeline that names the signal, mitigation, contributing change, follow-up owner, and verification step. Trace the product or shipment through plant, warehouse, port, carrier, customer, exception, and accounting steps with system authorities, timing, and support ownership.