Requirements to Architecture Mapping Questions
Bridges business and customer requirements to concrete architectural or non functional specifications. Candidates should extract throughput, concurrency, availability, latency, durability, security, compliance and budget constraints from scenarios and translate them into measurable goals such as requests per second targets, latency SLOs, durability levels, retention and encryption requirements. The topic includes creating a requirements matrix that directly informs component choices, capacity planning, and trade off justification.
EasyTechnical
0 practiced
A banking product requires encryption at rest and in transit and PCI-DSS compliance. As a software engineer mapping requirements to architecture, list concrete measurable requirements (for example AES-256 at rest, TLS1.2+ for transit, KMS-managed keys with rotation every 90 days) and components to implement (HSM/KMS, TLS termination, audit logging, tokenization). Provide a checklist of at least eight items you would include before a compliance audit.
HardTechnical
0 practiced
Case study: design a live bidding platform that requires p99 bid-placement latency <5ms for fairness, supports bursts up to 500k RPS during peak auctions, and enforces global fairness across bidders. Map functional and non-functional requirements to architecture: message routing, per-auction ordering guarantees, leader-election per-auction, placement of match engines, and network topology considerations. Describe how you'd measure and enforce fairness SLAs.
EasyTechnical
0 practiced
Given the following business goals for a messaging app: 1) deliver messages within <500ms 95% of the time globally, 2) 24/7 availability with 99.95% uptime, 3) retention 2 years, 4) GDPR compliance for EU users. Create a 3-column requirements matrix mapping business goal → measurable metric (include units and percentiles) → an initial architectural choice (1-2 components). Explain why each mapping is appropriate.
HardTechnical
0 practiced
Design an architecture to store and serve encrypted documents with per-document ACLs, offline access tokens, and efficient search across encrypted metadata, while keeping keys secure under a zero-trust model. Map requirements to components, key-management policies (envelope encryption, KMS/HSM usage, rotation), and outline performance trade-offs.
HardSystem Design
0 practiced
You inherit a large microservice platform with inconsistent SLOs across services. Draft a twelve-month migration plan to standardize SLOs and alerting: top-down mapping from product journeys to service SLIs, templates and CI checks, tooling to collect SLIs, rollout phases (pilot, incremental adoption), remediation paths for services that fail SLOs, success KPIs and enforcement mechanisms.
Unlock Full Question Bank
Get access to hundreds of Requirements to Architecture Mapping interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.