Before you design anything for a new customer, what do you need to find out about their environment?
Answer it out loud first, then compare. That's what makes it stick.
Five things. One, the business workflow and who owns it. Two, where the data lives and who controls access. Three, the security and compliance rules, like data residency or no external calls. Four, what infrastructure and identity systems I must plug into. Five, how success will be measured and who runs it after I leave. Those answers decide whether I build in their cloud, call an API, or something in between.
- Workflow, users and business owner
- Data: location, quality, access, sensitivity
- Security and compliance constraints
- Infrastructure, identity, network
- Success metric and ongoing owner
A good FDE answer shows you inherit constraints rather than choose a stack. Ask in this order, because early answers rule out later options.
1. Workflow and stakeholders
- What decision or task is being improved, and what does it cost today (hours, errors, delays)?
- Who is the business owner, who is the security reviewer, who will operate it? Missing any of them from the first call is a future blocker.
2. Data
- Where does it live (SaaS, on-prem database, shared drives)? How big, how fresh, how messy?
- Is it personal, health, financial or export-controlled data? Can a copy leave its current system at all?
- Who can approve read access, and how long does that usually take? In large enterprises this approval alone can take weeks, so start it on day one.
3. Security and compliance
- Data residency, required certifications, retention limits, whether a third-party model provider is already approved.
- Whether prompts and outputs may be logged, and for how long.
4. Infrastructure
- Cloud provider and region, existing VPC rules, identity provider (SSO, service accounts), how traffic reaches the internet, and what observability tools they already run.
- Whether you may deploy containers at all, or only use approved managed services.
5. Success and ownership
- One number the sponsor will judge by, a baseline for it, and a date.
- Who gets paged at 2 a.m. when it breaks?
Turn answers into a decision
Write a one-page constraints sheet and share it back. For example: data may not leave the EU region, model calls must go through the cloud provider's private endpoint, read-only access to one database, SSO required. That sheet makes the architecture choice almost mechanical and shows the customer you listened.
If they cannot answer something, record it as an open risk with an owner, not as an assumption.
- The security team has not been involved yet. What do you do?
- They say 'we don't know where the data is.' Next step?
- Which unanswered question is most likely to delay the project?
- FDE loop (Exponent) (prep, 2026) Describes FDE system design as mixing classic design with product sense: identify stakeholders and pain points before brainstorming.
- Forward Deployed Engineer System Design Interview (prep, 2026) Says the candidate often inherits the customer's infrastructure rather than choosing it.