Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Choose Spark APIs for Lakeflow

MediumPipelines00:00
Practice interviewer
In session
5 left
00:00

Your question is Choose Spark APIs for Lakeflow. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Context

A Databricks customer is modernizing legacy Spark jobs into a unified Databricks Lakehouse pipeline using Delta Lake, Databricks Workflows, and Delta Live Tables (Lakeflow Declarative Pipelines). Several existing jobs still use low-level RDD transformations, while newer code uses DataFrames. The team wants a clear migration strategy for batch and streaming ETL, with strong data quality guarantees and lower operational overhead.

You are asked to design the target pipeline architecture and explain where Spark RDDs, DataFrames, and Datasets should or should not be used in Databricks production pipelines.

Scale Requirements

  • Input sources: CDC from operational databases, JSON application logs, and hourly Parquet partner drops
  • Throughput: 150K records/sec peak streaming ingest, 4 TB/day batch ingest
  • Latency target: Bronze tables < 2 minutes from arrival; Silver tables < 10 minutes
  • Retention: 180 days raw, 2 years curated
  • Consumers: 40 BI dashboards, 12 ML feature pipelines, 20 downstream batch jobs

Requirements

  1. Design a Databricks-native pipeline from ingestion to curated Delta tables using Bronze/Silver/Gold layers.
  2. Explain the trade-offs between RDDs, DataFrames, and Datasets for ETL transformations, schema enforcement, optimization, and maintainability.
  3. Identify which API you would standardize on for Databricks batch and streaming pipelines, and where exceptions are justified.
  4. Include data quality controls such as schema validation, null checks, deduplication, and quarantine handling.
  5. Show how orchestration, backfills, and monitoring would work in Databricks Workflows.
  6. Describe how your design supports both SQL-first analytics users and PySpark/Scala engineers.

Constraints

  • Platform must stay fully on Databricks with Delta Lake as the system of record.
  • Team has mixed Python and Scala experience; most analysts are SQL-first.
  • Compliance requires auditability, replayability, and lineage for all production tables.
  • Minimize custom JVM code and operational complexity; avoid designs that block Photon/Catalyst optimizations.