Dev/Null Security is looking for an architect with an infrastructure and networking engineering background to help us build a repeatable way to recover a client’s critical services after catastrophic failure.
You will own the enterprise recovery architecture and work with engineers to build and test it. The design must work after a site outage, widespread data corruption or a cyber incident that leaves production systems and administrator accounts untrusted.
Experience you bring
- You have designed and helped deliver enterprise disaster recovery across on-premises and cloud environments, from compute, virtualisation and storage to the applications that depend on them. Experience designing for high availability across independent failure domains is desirable.
- You have engineered resilient networks and diagnosed failures in routing, firewalls, DNS and hybrid connectivity. You can design recovery access when the production network is unavailable.
- You have designed and tested backup and restore for databases, files and infrastructure configuration. You understand retention, encryption, key recovery and the limits of replication.
- You have led the technical recovery of a business service in a major incident or realistic exercise. You can explain what failed, what you restored first and what changed afterwards.
- You can turn a business impact assessment into recovery time objectives (RTOs) and recovery point objectives (RPOs) that service owners understand and engineers can test.
- You can brief directors and C-suite sponsors on outage impact, achievable recovery times and the investment needed to close a gap.
- You can resolve competing priorities across business continuity, incident response, infrastructure and application teams, and secure agreement on who can authorise a return to service.
Architecture design and leadership
- Translate business needs, threats and functional and non-functional requirements into practical architectures and clear trade-offs.
- Own target architectures, high-level designs, patterns and decisions; guide detailed design and assure implementation.
- Build transformation roadmaps with dependencies, delivery risks, acceptance criteria and operational handover.
- Present and defend designs at design authorities and executive forums; explain complex concepts clearly to different audiences.
- Provide thought leadership through technical challenge, emerging technology assessment and recommendations grounded in delivery experience.
- Influence stakeholders, facilitate workshops, build consensus and mentor engineers across security, technology and business teams.
- Apply peer review and governance; document deviations and risks, balancing security, resilience, user experience, cost and supportability.
Accountabilities and responsibilities
Agree what must recover first
- Identify the minimum services the business needs to operate. Map their dependencies, including identity, networks, data, key suppliers and the people needed to restore them.
- Agree recovery tiers with service owners. Identify which services need high availability, where failover still relies on shared infrastructure and when a clean restore is necessary.
- Build a phased roadmap with named owners. Start with one critical service, prove the design and use the evidence to agree the next investment.
Build the recovery environment
- Design an isolated recovery environment with independent administrative access and communications. Establish how engineers will restore identity, DNS, keys and connectivity if production management tools are lost.
- Produce network and infrastructure designs, clean build templates and recovery runbooks. Size compute, storage and network bandwidth against the volume of data to restore and the time available.
- Work with engineers to automate repeatable rebuild steps. Document the order of recovery, the decisions that need human approval and the fallback if automation is unavailable.
Protect data and establish a trusted restore point
- Design isolated, immutable or offline backup copies with separate administration. Test that staff can retrieve both the backups and the keys needed to read them.
- Agree with incident responders how to select a known-good restore point after compromise or corruption. Account for transactions lost since that point and how the business will reconcile them.
- Define checks for data integrity and consistency across dependent systems. Have application owners validate a representative business transaction before reconnecting the service.
Prove recovery and lead the return to service
- Exercise failover and failback for highly available services. Run separate clean recovery tests for site loss or compromise; measure restoration time and data loss against agreed targets.
- During a major incident, advise the incident commander on recovery options, dependencies and residual risk. Plan a controlled return to normal operations; assign and retest fixes for exercise or incident findings.
Qualifications and certifications
Relevant degree or equivalent experience. Infrastructure, networking, cloud or continuity qualifications are desirable. Practical evidence of building and testing recovery capability is essential.
Working at DevNull Security
DevNull Security is remote-first. Client-site travel may be required up to 3 times per week, depending on project and customer needs.
We welcome applicants from all backgrounds and are committed to an inclusive, equitable and accessible hiring experience. We offer adjustments throughout application and assessment; tell us what you need.