Technical interview guide

Self-Service Infrastructure

Letting teams provision what they need through an API or portal, with policy enforced automatically instead of manually.

Read: 40 min
Practice MCQs: 25
Interview QA: 25
Edition: v3
Editorial status: Reviewed
Relevant for: Platform Engineer

Scope: AWS and Microsoft platform engineering guidance and HashiCorp Terraform/HCP Terraform documentation current 2026-08-31; confirm product-tier and version-specific policy features for the target deployment.

Interview QA

Treat each question like a live interview question: answer out loud first (structure, assumptions, tradeoffs), then open the model answer to spot gaps and rehearse a tighter follow-up.

Curated: 2026-10-05 · Written: 2026-09-09 · Reviewed: 2026-10-03

QA-1

Design self-service database provisioning.

QA-2

Design authorization for self-service infrastructure.

QA-3

Design the plan-and-apply workflow.

QA-4

Secure infrastructure state and plans.

QA-5

Recover from a stuck infrastructure state lock.

QA-6

Design policy-as-code for self-service requests.

QA-7

Handle a policy service outage.

QA-8

Design quotas and rate limits.

QA-9

Design cost visibility and controls.

QA-10

Design ephemeral environment lifecycle.

QA-11

Handle infrastructure drift.

QA-12

Import existing infrastructure into self-service management.

QA-13

Design asynchronous request status and retry.

QA-14

Handle cancellation during apply.

QA-15

Design safe infrastructure deletion.

QA-16

Protect self-service runners and plugins.

QA-17

Design tenant isolation for infrastructure workspaces.

QA-18

Design break-glass infrastructure access.

QA-19

Recover from lost or corrupted infrastructure state.

QA-20

Design ownership transfer for managed infrastructure.

QA-21

Measure self-service infrastructure success.

QA-22

Design platform SLOs for provisioning.

QA-23

Roll out self-service infrastructure incrementally.

QA-24

Handle provider outage during provisioning.

QA-25