Engineering Ic interview prep.

Behavioural questions to expect

1. Walk me through your CV.
2. Tell me about your most impactful technical project.
3. Tell me about a weakness, a failure, or feedback you've received and worked on.
4. Why cloud hyperscaler engineering - and why the firm vs enterprise SaaS, consumer, or pure devtools?
5. Which team or service would you want to work on, and why?
6. Why the firm?
7. How would you describe the firm's engineering organisation + architecture in your own words?
8. How does engineering actually drive value at a hyperscaler?

Technical concepts to master

• Distributed-systems primitives (hyperscaler scale)

  Consensus (Raft / Paxos) · Sharding + multi-tenant isolation · Static stability + graceful degradation · Hardware-software co-design

• Cost + efficiency engineering

  Cost decomposition + attribution · Right-sizing + utilization · Hot / cold tiering + lifecycle · Algorithm + hardware efficiency

• SLA-grade reliability + customer credits

  SLA tiers + credit-back · Cell-based blast radius bound · Region failover + recovery drills · Publish-grade postmortem + comms

• Observability + golden signals (hyperscaler scale)

  Four golden signals + customer attribution · SLI / SLO / error budget · Cardinality at hyperscaler scale · Change management + canary discipline at scale

Practical drills

• A hyperscaler kv-store service handles 5M QPS globally (60% US, 30% EU, 10% APAC). P99 budget 5ms intra-region. Target SLA 99.99%. (a) Per-region capacity. (b) Multi-region replication strategy. (c) Rough cost framework + the levers if you had to cut cost 20%.
• Design a multi-region key-value store for the firm's customers at hyperscaler scale (millions of customers, 5M QPS global, 99.99% SLA). Walk me through it.
• Your service P99 latency spikes 10x in one region; customer SLA at risk; multiple major customers reporting impact. Walk me through the next 60 minutes.

Smart-question anchors

• Team + service - the team's scope, what the role would specifically own in 6-12 months
• Architecture posture - cell-based, multi-region, static stability, hardware co-design
• SLA + reliability - the SLA tier, recent incidents, customer-facing postmortem culture
• Cost + FinOps - the efficiency posture, per-customer attribution, recent cost programs
• Career ladder + growth - what differentiates Mid / Senior / Staff at this hyperscaler

Sourced from

interviewing.io + Hello Interview + IGotAnOffer — Senior SWE System Design · Canonical SRE reference + Google SRE Book — golden signals + SLOs + cell architecture · Hyperscaler engineering blogs + practitioner content (cloud-architecture patterns) · Tech Interview Handbook — Behavioral Interview Questions for SWE · Cost engineering + FinOps community (FinOps Foundation) · AWS Builder's Library + hyperscaler postmortems