P
Padsplitvia Lever
Data Engineer (Fully Remote)
REMOTEPosted 2d ago
Data EngineerMid LevelFull-time
Not sure if you're a good fit?
Upload your resume and TixelJobs AI will compare it against Data Engineer (Fully Remote) at Padsplit. Get a match score, missing keywords, and improvement tips before you apply.
Free preview · Your resume stays private
About the Role
The Role We Need
PadSplit is growing its analytics platform and needs a hands-on Data Engineer to work alongside our existing DE lead. This person will build and maintain ingestion and transformation pipelines across Dagster (or Airflow), dbt, and Snowflake, with supporting work in Python, Airbyte, and AWS. The role combines building new pipelines and data models with providing real coverage on critical paths — especially the daily Postgres → Snowflake → dbt flow and third-party API loads — all shipped through reviewed pull requests rather than one-off scripts.
The Person We Are Looking For
We're looking for a practitioner who thinks natively in dimensions, facts, and slowly changing dimensions — someone who knows when to use a full refresh versus an incremental load and how that choice affects idempotency and backfills. This person writes clear, reviewable PRs and gives equally thoughtful reviews, with attention to scoped diffs, sensible tests, and failure modes. They're comfortable in complex Python data flows and have enough AWS literacy to reason about task roles, buckets, and cross-account access without needing to own all of platform engineering.
PadSplit is growing its analytics platform and needs a hands-on Data Engineer to work alongside our existing DE lead. This person will build and maintain ingestion and transformation pipelines across Dagster (or Airflow), dbt, and Snowflake, with supporting work in Python, Airbyte, and AWS. The role combines building new pipelines and data models with providing real coverage on critical paths — especially the daily Postgres → Snowflake → dbt flow and third-party API loads — all shipped through reviewed pull requests rather than one-off scripts.
The Person We Are Looking For
We're looking for a practitioner who thinks natively in dimensions, facts, and slowly changing dimensions — someone who knows when to use a full refresh versus an incremental load and how that choice affects idempotency and backfills. This person writes clear, reviewable PRs and gives equally thoughtful reviews, with attention to scoped diffs, sensible tests, and failure modes. They're comfortable in complex Python data flows and have enough AWS literacy to reason about task roles, buckets, and cross-account access without needing to own all of platform engineering.
Ready to apply?
This job is active. Apply now to get in early.