Baltimore, MD
Security Architect recruiting based on accountable delivery experience. Crosscheck recruits Data, Cloud & Security candidates for contract, contract-to-hire, and permanent roles tied to Baltimore.
What We Place
Representative roles
Platforms and technologies
Our Approach
This editorial hiring guide starts with sourced Baltimore business context. Baltimore Together's economic-development materials separate technology, life sciences, and industrial, manufacturing, and logistics work. Each setting changes the data boundary, operating risk, and evidence a hiring manager should request. A Security Architect search should define the operating boundary before comparing resumes. The brief must distinguish Security Architect, Enterprise Security Architect, Cloud Security Architect and connect role-specific scope to the work this person will personally own. Screening centers on security architecture, threat models, control patterns, design reviews, identity boundaries, risk decisions, standards, and remediation roadmaps.
Define the systems, delivery stage, operating boundary, and ownership expected from the Security Architect
Screen candidates for evidence of security architecture, threat models, control patterns, design reviews, identity boundaries, risk decisions, standards, and remediation roadmaps
Separate direct delivery experience from adjacent product, project, or consulting exposure
Support contract, contract-to-hire, and permanent searches across the US and Canada
Start the search
Include the business context, systems, delivery phase, work model, compensation, and interview timeline. A Crosscheck search lead will use that context to calibrate the role before sourcing begins.
Local Market Brief
Record the required decisions, systems, delivery stage, and support duties for Security Architect work. Treat Threat Modeling, Zero Trust, Security Patterns, Identity Architecture as context for the assignment, not a keyword checklist. Separate that scope from adjacent Application Security Architect, Zero Trust Architect, Security Solution Architect responsibilities so each candidate is evaluated against the same completed brief. Build the calibration map from the actual assignment: Security Architect against Threat Modeling and Zero Trust; Enterprise Security Architect against Security Patterns and Identity Architecture; Cloud Security Architect against Cloud Security and Application Security; Application Security Architect against Design Reviews and Security Roadmaps; Zero Trust Architect against security architecture and threat models; Security Solution Architect against control patterns and design reviews. For the delivery handoff, trace the working sequence from Application Security to Cloud Security to Identity Architecture to Security Patterns to Zero Trust to Threat Modeling and name who accepts each boundary. The three sourced Baltimore contexts below turn that scope into intake and screening decisions. They do not measure current vacancies, candidate supply, or Crosscheck client activity.
Editorial market scenario
Give candidates the integration, approval, audit, and change-management boundaries during the interview. Ask for comparable decisions from prior work. This is planning guidance, not measured local demand.
Editorial industry scenario
A public-sector brief should identify access, procurement, documentation, security, and stakeholder constraints before sourcing begins. Confirm that this context applies to the employer before using it in the search.
Screening focus
Screening covers data scale, platform choices, governance needs, and the candidate's record of making data useful to downstream teams.
Published labor benchmark
BLS does not publish an occupation matching Security Architect. Crosscheck uses Information Security Analysts (15-1212) as the closest published broad benchmark; it is not a count or pay estimate for this exact specialty.
BLS OEWS May 2025, published May 15, 2026
Published metro employment
4,600
BLS publishes a narrower metro employment estimate for the proxy occupation. Screen for adjacent experience that transfers without lowering the production bar. The estimate equals 3.391 jobs per one thousand across the metro workforce.
Employment concentration
2.77 location quotient
Baltimore-Columbia-Towson, MD reports more than twice the national employment concentration for this proxy occupation. Treat that as occupational context, not proof of available candidates.
Annual wage reference
$78,110 to $218,620
The metro median is 7% above the national Information Security Analysts median. Test whether the role's scope and location requirement support that difference. BLS reports a $138,170 median for the proxy occupation in Baltimore-Columbia-Towson, MD.
Hiring brief scenarios
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
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. Define how Cloud Security, Application Security, Design Reviews, Security Roadmaps fit the employer's current environment. Ask which constraints changed the design, what Security Architect owned directly, who approved the decision, and how the result was checked after delivery. Cybersecurity work can cross identity, networks, cloud services, endpoints, protected data, incident response, audit records, and restricted facilities or contracts.
Evidence to request: Request a redacted design, configuration, test, runbook, review record, or operating measure that supports the candidate's account of Security Architect ownership. 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
Baltimore Together's economic-development strategy sets a city objective to lead in life sciences and medical devices. Set the boundary for ownership checkpoints before interviews. A useful account involving security architecture, threat models, control patterns, design reviews names the starting condition, alternatives considered, implementation sequence, failure handling, and the operating team that received the work. 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 a comparable scenario involving standards, and remediation roadmaps, Security Architect, Enterprise Security Architect and score assumptions, technical judgment, communication, delivery steps, and the evidence proposed for acceptance. 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
Baltimore Together tracks industrial, manufacturing, and logistics work as a distinct part of the city's economic-development strategy. Connect adjacent role boundaries to an employer decision rather than a broad tool list. Require the candidate to explain work with identity boundaries, risk decisions, standards, and remediation roadmaps, including dependencies, controls, measurable evidence, and responsibility when the original plan changed. 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 a problem involving Enterprise Security Architect responsibilities. Record the signal, diagnosis, decision, corrective action, handoff, and verification the candidate personally completed. Trace the product or shipment through plant, warehouse, port, carrier, customer, exception, and accounting steps with system authorities, timing, and support ownership.
Interview scorecard
Ask each candidate the same core questions. Score the evidence, ownership, and judgment in the answer instead of relying on job-title or keyword matches.
1. Security Architect: Threat Modeling
Choose a Threat Modeling decision from your work as Security Architect. Which constraint changed the design, and what evidence supported the result?
Use the answer to assess controlled access, lineage, reporting definitions, retention, and data-sharing boundaries. The public-sector and security work context is an editorial scenario, not a measured claim about Baltimore.
2. Enterprise Security Architect: Zero Trust
Describe project work you completed as Enterprise Security Architect involving Zero Trust that did not follow the original plan. What did you own, and how did you correct it?
Use the answer to assess controlled access, lineage, reporting definitions, retention, and data-sharing boundaries. The public-sector and security work context is an editorial scenario, not a measured claim about Baltimore.
3. Cloud Security Architect: Security Patterns
For a Security Patterns system you supported, explain the handoff, operating limits, and measures used after launch. Where did your responsibility begin and end?
Use the answer to assess controlled access, lineage, reporting definitions, retention, and data-sharing boundaries. The public-sector and security work context is an editorial scenario, not a measured claim about Baltimore.
Screened for security architecture, threat models, control patterns, design reviews, identity boundaries, risk decisions, standards, and remediation roadmaps, with the boundary set by the employer's systems, delivery stage, and operating model. The evaluation connects Threat Modeling, Zero Trust, Security Patterns to a concrete hiring responsibility.
Show how Threat Modeling, Zero Trust, Security Patterns shaped one delivery decision. Which constraint mattered, and what did the candidate own?
Evidence check: Look for an artifact, test, configuration record, or operating measure that supports the account. Compare it with work such as technical product and platform teams.
Screened for security architecture, threat models, control patterns, design reviews, identity boundaries, risk decisions, standards, and remediation roadmaps, with the boundary set by the employer's systems, delivery stage, and operating model. The evaluation connects Identity Architecture, Cloud Security, Application Security to a concrete hiring responsibility.
Where did Enterprise Security Architect work involving Identity Architecture, Cloud Security, Application Security fail or change direction? What evidence prompted the correction?
Evidence check: A useful answer names the failure signal, the candidate's decision, and the result. Certification alone does not establish project ownership.
Screened for security architecture, threat models, control patterns, design reviews, identity boundaries, risk decisions, standards, and remediation roadmaps, with the boundary set by the employer's systems, delivery stage, and operating model. The evaluation connects Design Reviews, Security Roadmaps, security architecture to a concrete hiring responsibility.
Explain the handoff and operating boundary for a project using Design Reviews, Security Roadmaps, security architecture. Who approved changes, monitored results, and supported the system?
Evidence check: Request documentation, controls, or production measures that distinguish direct ownership from observation or team-level credit.
Screened for security architecture, threat models, control patterns, design reviews, identity boundaries, risk decisions, standards, and remediation roadmaps, with the boundary set by the employer's systems, delivery stage, and operating model. The evaluation connects threat models, control patterns, design reviews to a concrete hiring responsibility.
Which tradeoff would change the design of threat models, control patterns, design reviews for this hiring task: support contract, contract-to-hire, and permanent searches across the us and canada?
Evidence check: Score the response on technical judgment, stated assumptions, and evidence from comparable work rather than vocabulary coverage.
Organizations hiring across Baltimore can use the market context below to shape location, compensation, and screening requirements for Security Architect searches.
Technical product and platform teams
Transformation and implementation programs
Internal engineering and operations teams
Systems integration and advisory teams
FAQ
For qualified exclusive searches in our core disciplines, Crosscheck targets a first candidate slate within 48 hours after a completed intake. Contract placements include a 40-billable-hour replacement guarantee, and permanent placements include a 90-day replacement guarantee, subject to the signed agreement.
Continue your research