DataEngineering

Matalin Interview Questions

4.0 (1104)7,504 learners20 lessons40m

Curriculum

Topic

What is Matillion, and what does it mean that it is a _cloud-native, push-down ELT_ tool rather than a traditional ETL tool_2:09
Explain the difference between ETL and ELT, and why Matillion pushes transformation logic down into the data warehouse.2:00
What is the difference between an orchestration pipeline (job) and a transformation pipeline (job) in Matillion_1:56
Which cloud data warehouses does Matillion work with, and why does the choice of warehouse matter for how transformations execute_1:56
You need to extract data from a REST API, land it in Snowflake, then clean and join it. Which pipeline types and components would you use, and in what order_2:03
A transformation pipeline has grown to 40+ components and is hard to read and maintain. How would you restructure it_1:56
You need to load data from an API that has no native Matillion connector. What are your options_1:56
Your source data is semi-structured JSON nested several levels deep. How would you make it queryable as flat relational columns in Matillion_1:58
A single orchestration pipeline needs to run several transformation pipelines, some in parallel and some in sequence. How would you wire this up_2:10
You want to reuse the same load-and-transform logic for 50 different source tables. How would you avoid building 50 near-identical pipelines_1:56
The same pipeline must run against dev, test, and prod warehouses with different schemas and credentials. How would you structure this without duplicating pipelines_2:01
You need a pipeline to behave differently based on a value computed at runtime (e.g., a row count). How would you use variables to control the flow_1:41
Explain the difference between job variables and environment variables, and when you'd use a grid variable.1:47
You need to loop over a list of table names and run the same extract for each one. How would you implement iteration in Matillion_2:05
A variable's value set inside an iterator isn't persisting the way you expect across loop runs. What variable behavior (scope_branch) is likely causing this_2:05
A source table has 500 million rows and you only want to load records changed since the last run. How would you design an incremental load_1:59
You need to implement slowly changing dimension (SCD) Type 2 logic in a Matillion transformation pipeline. How would you approach it_2:06
Your full reload of a large table is slow and expensive every night. What strategies would you use to reduce load time and warehouse cost_1:59
A nightly load partially failed and left the target table in an inconsistent state. How would you make the load idempotent and safely re-runnable_1:59
You need to capture and process only new files arriving in S3_Blob storage. How would you orchestrate this_1:58