Why pre-screen storage architects before the technical interview
Storage mistakes are permanent in a way most infrastructure decisions are not. Buy the wrong tier and you live with the performance for the depreciation period; size from a vendor's assumptions and you find out under load. Architects worth hiring size from measured demand, and they have restored from backup as a test rather than assuming it works. A short screen asks for the last restore test and for a bottleneck they diagnosed with numbers.
What actually matters when screening Storage Architect candidates
- 01
Technical proficiency
Probe depth across block, file and object: NetApp ONTAP, Pure, Dell PowerStore, Ceph or MinIO, plus fabric detail like NVMe over TCP, zoning, multipathing and snapshot replication.
- 02
Systems and trade-offs
Ask how they sized capacity and performance tiers, set RPO and RTO targets, chose sync versus async replication, and justified cost per usable TB against cloud alternatives.
- 03
Evidence and rigour
Look for migrations and builds they own: petabyte moves, array refreshes, S3 backup redesign, with before and after latency, throughput and utilisation numbers.
- 04
Collaboration and communication
Test how they handled a latency complaint or failed rebuild: queue depth analysis, host-side tracing, working with DBAs, VMware admins and vendor support escalation.
Pre-screening questions to ask Storage Architect candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Platforms they designed
4 questions01What is your experience with storage area network design and setup?
Listen forDesigns they produced and then operated, with capacity and host counts named rather than a reference architecture.
Designs delivered with no operational involvement, or scale left undescribed.
02Have you worked with specific storage systems and arrays?
Listen forNamed platforms with a view on where each falls down, drawn from running them rather than from datasheets.
Products listed with no operational experience, or vendor claims repeated without qualification.
03Do you have experience with cloud storage solutions?
Listen forStorage classes chosen for access patterns with egress and retrieval costs understood, not just capacity price.
Cloud storage costed on capacity alone, or archive tiers used with no awareness of retrieval charges.
04Do you have experience architecting and designing high availability storage systems?
Listen forFailure domains reasoned about explicitly, with a case where a supposedly redundant design still failed.
Redundancy applied uniformly with no analysis, or single points of failure that were never identified.
Sized from measurement
4 questions05Do you have experience with storage performance testing and capacity planning?
Listen forSizing from measured input and output rates, latency requirements and observed growth rather than from a calculator.
Capacity planned from a vendor tool, or performance sized on headline throughput figures.
06Can you describe a time when you had to solve a storage bottleneck?
Listen forA bottleneck found with measurement across the path, with the layer identified rather than capacity simply added.
Bottlenecks solved by adding hardware, or the cause never established after the symptom cleared.
07What is your methodology for predicting future storage needs?
Listen forGrowth measured from actual consumption over time, with retention policy treated as a lever rather than a given.
Growth assumed at a fixed percentage, or capacity ordered reactively when a platform fills.
08How familiar are you with data deduplication and thin provisioning?
Listen forRealistic ratios from their own platforms, with the risk of over-provisioning understood and monitored.
Vendor reduction ratios assumed, or thin provisioning used with no alerting on actual consumption.
Restores tested
2 questions09Can you explain your experience with data backup and recovery solutions?
Listen forA date for the last test restore and what it revealed, with recovery time measured rather than estimated.
Backups configured but never restored, or no idea how long a full recovery would actually take.
10Do you have experience in the design and implementation of disaster recovery strategies?
Listen forRecovery objectives agreed with the business and then tested, with a gap the exercise exposed.
Recovery objectives set without testing, or a plan that has never been exercised end to end.
Migrations without loss
2 questions11Do you have experience with data migration projects?
Listen forMigrations with verification that data arrived intact, plus a rollback route and how cutover was managed.
Migrations with no verification step, or cutovers performed with no way back.
12How have you implemented storage security measures in previous roles?
Listen forEncryption at rest with key management thought through, plus access separated so one account cannot delete everything.
Encryption enabled with keys stored alongside the data, or backups deletable by the same credentials as production.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Technical proficiency
35%5Names arrays and protocols worked on directly, explains RAID versus erasure coding, IOPS versus latency, and replication mechanics without hand-waving.
Systems and trade-offs
25%5Walks through a tiering or DR design with explicit trade-offs on cost, latency, failure domains and rebuild windows.
Evidence and rigour
25%5Cites specific migrations with volumes, cutover windows, downtime taken, and how they validated data integrity afterwards.
Collaboration and communication
15%5Describes evidence-led diagnosis, separates array from fabric from host causes, and documents standards others in the org actually follow.
Buy the wrong tier and you live with it for the depreciation period. A one-way video screen asks what they measured before sizing anything.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish what they designed and operated, test their capacity planning method, and check whether recovery has ever been exercised.
How should I weight vendor certifications?
As evidence of product familiarity. They are useful and widely held. What they do not show is whether someone sized a platform from measured workload rather than from a reference architecture.
Evaluating answers
What is the strongest signal when screening a storage architect?
The last time they restored from backup as a test, and what it revealed. Architects who run real platforms have a date and a result. Anyone who has only configured backups has an assumption, not a recovery plan.
How do I judge capacity planning claims?
Ask what they measured before sizing. Real answers involve observed input and output rates, latency and growth over time. Anyone who sized from a vendor calculator has bought whatever that calculator assumed.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
