Technical Foundation and Self Assessment Questions

Covers baseline technical knowledge and the candidate's ability to honestly assess and communicate their technical strengths and weaknesses. Topics include fundamental infrastructure and networking concepts, operating system and protocol basics, core development and platform concepts relevant to the role, and the candidate's candid self evaluation of their depth in specific technologies. Interviewers use this to calibrate how technical the candidate is expected to be, identify areas for growth, and ensure alignment of expectations between product and engineering for collaboration.

MediumTechnical

33 practiced

Explain strategies for schema evolution in Avro/Parquet based systems: additive changes, renames, nested structures, backward and forward compatibility. Describe concrete processes and tools (schema registry, contract tests, migration plan) you would use to prevent downstream breakage when producers change schemas.

HardTechnical

40 practiced

A Redshift cluster has growing query tail latencies. Explain a prioritized checklist to diagnose and optimize: analyze query plans, distribution style, sort keys, vacuum/analyze, concurrency (WLM), materialized views, and data layout changes. Provide concrete steps to reduce hotspots and tail latency.

HardSystem Design

38 practiced

Design an exactly-once deduplication approach for a Kafka → Flink streaming pipeline that occasionally receives duplicate events from devices. Describe state layout, watermarking strategy, windowing decisions, checkpointing settings, TTL for state, and how to handle late-arriving events and compaction of dedup state.

HardSystem Design

43 practiced

Design an IoT ingestion system for 10M devices, each sending a 200-byte message once per minute. Provide an architecture (managed cloud services or hybrid) that supports durable ingestion, per-device ordering, efficient storage (hot/warm/cold tiers), near-real-time analytics, and cost controls. Estimate ingest QPS, storage, and discuss throttling and backpressure strategies.

HardSystem Design

37 practiced

Design a dimensional model (star schema) for e-commerce orders to support cohort analysis and time-series metrics. Define fact tables (orders, order_items) and dimension tables (user, product, promotion). Show how to support SCD Type 2 for user attributes, handle returns/cancellations, and ensure queries for cohorts and lifetime value are efficient.

Unlock Full Question Bank

Get access to hundreds of Technical Foundation and Self Assessment interview questions and detailed answers.

Join thousands of developers preparing for their dream job.