> Markdown version of [/jobs/ext/4136900-senior-data-engineer](https://www.wearedevelopers.com/jobs/ext/4136900-senior-data-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Data Engineer

- **Company:** Ryft Pay Ltd
- **Location:** Manchester, UK
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Airflow, Amazon Web Services, Amazon S3, BigQuery, Continuous Integration, Amazon DynamoDB, Identity and Access Management, Python (Programming Language), Operational Databases, SQL Databases, Snowflake, Change Data Capture, Git, Amazon Simple Queue Service (SQS), Amazon Redshift
- **Published:** October 12, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=51d646af6585cbc1

## About the Role

Several years building and running production data platforms, comfortable being the most senior engineer on the platform day to day

 * Real AWS depth in production, across S3, IAM, networking, and the ingestion and messaging services (Kinesis / Firehose, EventBridge, SNS, SQS, Lambda or equivalent)
 * Hands-on change data capture and event-driven ingestion - you understand delivery guarantees, idempotency, ordering, duplicates, and replay, and what each costs to get right
 * Strong production Python and SQL, a cloud warehouse (Snowflake, Redshift, BigQuery or similar), and an orchestrator (Dagster, Airflow or equivalent)
 * You've run what you built, been called when it broke, and changed something structural afterwards - Git, pull requests, CI/CD and testing are defaults, not aspirations
 * Comfortable working inside an infrastructure estate you don't own, and able to negotiate what you need from teams whose backlogs you don't control
 * Pragmatic - you ship working things and know when a simple solution now beats an elegant one later

Nice to have
*
Payments or fintech experience, particularly transaction, ledger, or reconciliation data

 * Change data capture out of DynamoDB or a similar store
 * A warehouse or platform migration behind you
 * dbt familiarity, so you know how your outputs get consumed
 * Multi-account AWS, data residency work, data contracts or schema registries

## Description

Near-greenfield platform ownership at an FCA-regulated payments business, with the ownership boundaries drawn and agreed - you'll spend your time building, not arguing about whose job something is

 * Direct exposure to senior leadership, with real influence over the target architecture
 * A seat at a fast-growing, well-funded fintech scaling in a genuinely underserved part of the payments market