Hiring brief scenarios
Build the Platform Engineer 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 Baltimore demand, clients, or candidate supply.
Sourced cybersecurity and technology context
Secure services, identity, and technical products: Platform 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. Map the local operating context to platform isolation and access. Ask how the engineer would separate teams, data classes, and environments while keeping common services supportable. 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 platform architecture with tenancy, identity, network, secret, and observability decisions tied to user needs. 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: Platform Engineer
Baltimore Together's economic-development strategy sets a city objective to lead in life sciences and medical devices. Define the developer workflow that needs improvement. Candidates should show how they measured build, deploy, provisioning, or incident steps before choosing a platform change. 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: Ask for a before-and-after developer workflow with measured steps, adoption evidence, and support cost. 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: Platform Engineer
Baltimore Together tracks industrial, manufacturing, and logistics work as a distinct part of the city's economic-development strategy. State the reliability boundary between the platform team and application teams. Include upgrades, capacity, backups, incident routing, and deprecation in the role scope. Port and factory systems can connect engineering changes, production, quality, inventory, freight, customs, carriers, maintenance, exceptions, and financial settlement across organizations.
Evidence to request: Use an upgrade or outage scenario and require a maintenance plan, communication path, rollback, and ownership matrix. Trace the product or shipment through plant, warehouse, port, carrier, customer, exception, and accounting steps with system authorities, timing, and support ownership.