InterviewStack.io LogoInterviewStack.io

AWS Data Services Questions

Specialized knowledge of Amazon Web Services targeted at data storage, processing, analytics, and streaming. This covers object storage and data lake design with Simple Storage Service including storage classes, lifecycle and partitioning strategies; analytics and warehousing with Redshift including columnar storage, distribution styles, compression, query optimization and concurrency considerations; big data processing with Elastic MapReduce for managed Spark and Hadoop clusters and associated tuning; serverless extract transform and load using Glue and data catalog concepts, schema management and job orchestration; and real time data ingestion and processing with Kinesis including producers, shards, retention, consumers, and stream processing patterns. Candidates should understand when to choose batch versus streaming architectures, how to integrate services into end to end data pipelines, trade offs around scalability, latency, consistency, security, data governance and cost optimization, and monitoring and debugging techniques for data workloads.

MediumTechnical
20 practiced
You observe slow Redshift queries caused by large scans. What steps and Redshift tools would you use to diagnose and improve performance? Include specific system tables or views to inspect and optimizations like compression, sort keys, vacuum/analyze, and WLM tuning.
MediumTechnical
25 practiced
Design a strategy for schema evolution of Parquet datasets in S3 that are consumed by multiple teams. Explain how to handle adding nullable fields, changing types, deleting columns, and how to update the Glue Data Catalog and consumer contracts with minimal disruption.
EasyTechnical
20 practiced
Describe AWS Glue Data Catalog: what metadata it stores, how it integrates with Athena, Redshift Spectrum and EMR, and the differences between using a crawler and explicitly defining tables. Explain how the catalog helps a data engineering team.
HardTechnical
34 practiced
Define a monitoring and alerting strategy for a data platform composed of Glue jobs, EMR clusters, Redshift, and Kinesis streams. List key system and data metrics to collect, log sources to aggregate, methods to reduce alert noise, and outline runbooks for three common failure scenarios.
HardTechnical
27 practiced
(PySpark) Implement a sessionization routine for clickstream data that assigns a session_id per user based on a 30-minute inactivity timeout. Input schema: user_id string, event_time timestamp, bytes int. Output: session_id, user_id, session_start, session_end, event_count, total_bytes. Describe an efficient approach for large-scale batch processing.

Unlock Full Question Bank

Get access to hundreds of AWS Data Services interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.