Time since we first saw it
Day 0
Early. Similar jobs usually come down between day 6 and day 56.
From 14,166 similar postings that came down. Coming down is not always a hire.
Toronto, Ontario
Actively hiring, first seen by us 13 hours agoBuild the source-to-Silver ingestion layer for a complex data and AI platform transformation at a regulated financial institution.
Design, build, test, and own source connectors from S3 landing to validated Silver records.
The Role : Build the source-to-Silver ingestion layer for a complex data and AI platform transformation at a regulated financial institution. Own the design and delivery of 30+ source connectors across low, medium, and high complexity tiers — file-based, SQL-based, and API-based — on a medallion architecture running on AWS. You are not a pipeline configuration resource. You are an engineer who understands what the data means, where it breaks, and why, and you build connectors that hold up in production under schema drift, late arrivals, and source quality gaps. You Will :
You Will : Design, build, test, and own source connectors from S3 landing to validated Silver records. Each connector covers the full four-component stack: S3 trigger configuration, Bronze layer write (immutable raw copy with provenance metadata), Silver layer transformation (schema enforcement, field mapping, type casting, null and range checks, deduplication, bad record quarantine), and source arrival monitoring feeding the pipeline audit table. Translate source-to-target mapping specifications — provided by the client data analyst team — into connector logic that handles both single-field mappings and multi-field derivations: conditional expressions, arithmetic combinations across multiple source fields, and lookup-based enrichment.
Strong Python engineering skills — you write production-quality code, not scripts. You know the difference between code that works once and code that holds up under bad data, late files, and schema changes three months into a project.
Experience with orchestration frameworks (MWAA, Step Functions, Airflow, or Control-M): you understand how your connector fits into the dependency graph and what happens downstream when it fails.
ML arteka is one of the fastest-growing IT Services and Consulting companies in Canada and serves some of the most iconic brands, including Google, Loblaws, Staples, Telus, Bell, Rogers, CIBC, BMO, CMLS, Fossil, Fitbit and more.
In the employer’s words · Read in context
Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 0
Early. Similar jobs usually come down between day 6 and day 56.
From 14,166 similar postings that came down. Coming down is not always a hire.
4 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
Who You Are : - Strong Python engineering skills — you write production-quality code, not scripts. You know the difference between code that works once and code that holds up under bad data, late files, and schema changes three months into a project. - Experienced building data ingestion pipelines on AWS: S3-triggered processing, Glue ETL jobs or equivalent, schema enforcement, and pipeline observability. You have dealt with sources that do not behave the way their documentation says.
The Role : Build the source-to-Silver ingestion layer for a complex data and AI platform transformation at a regulated financial institution. Own the design and delivery of 30+ source connectors across low, medium, and high complexity tiers — file-based, SQL-based, and API-based — on a medallion architecture running on AWS. You are not a pipeline configuration resource. You are an engineer who understands what the data means, where it breaks, and why, and you build connectors that hold up in production under schema drift, late arrivals, and source quality gaps. You Will :
- Strong Python engineering skills — you write production-quality code, not scripts. You know the difference between code that works once and code that holds up under bad data, late files, and schema changes three months into a project. - Experienced building data ingestion pipelines on AWS: S3-triggered processing, Glue ETL jobs or equivalent, schema enforcement, and pipeline observability. You have dealt with sources that do not behave the way their documentation says. - Familiar with Apache Iceberg table format for Bronze and Silver layers: partition design, schema evolution, and how Iceberg handles late-arriving and out-of-order records.
- Comfortable working in co-development settings where the client's engineers own connectors alongside yours — you review their code honestly, accept feedback on yours, and treat the shared codebase as a shared responsibility. - Experience with orchestration frameworks (MWAA, Step Functions, Airflow, or Control-M): you understand how your connector fits into the dependency graph and what happens downstream when it fails. - Detail-oriented on data provenance — you build Bronze layers that make forensic investigation possible, not just fast processing.
- Experienced building data ingestion pipelines on AWS: S3-triggered processing, Glue ETL jobs or equivalent, schema enforcement, and pipeline observability. You have dealt with sources that do not behave the way their documentation says. - Familiar with Apache Iceberg table format for Bronze and Silver layers: partition design, schema evolution, and how Iceberg handles late-arriving and out-of-order records. - You read a source data dictionary and immediately know which fields will cause problems, which data types will drift, and which business rules embedded in the legacy system are about to become your transformation problem.
You Will : - Design, build, test, and own source connectors from S3 landing to validated Silver records. Each connector covers the full four-component stack: S3 trigger configuration, Bronze layer write (immutable raw copy with provenance metadata), Silver layer transformation (schema enforcement, field mapping, type casting, null and range checks, deduplication, bad record quarantine), and source arrival monitoring feeding the pipeline audit table. - Translate source-to-target mapping specifications — provided by the client data analyst team — into connector logic that handles both single-field mappings and multi-field derivations: conditional expressions, arithmetic combinations across multiple source fields, and lookup-based enrichment.
Complete your application on mlarteka.catsone.com. The employer’s form will show what is required.
Already applied? Track this application
Build the source-to-Silver ingestion layer for a complex data and AI platform transformation at a regulated financial institution. Own the design and delivery of 30+ source connectors across low, medium, and high complexity tiers — file-based, SQL-based, and API-based — on a medallion architecture running on AWS. You are not a pipeline configuration resource. You are an engineer who understands what the data means, where it breaks, and why, and you build connectors that hold up in production under schema drift, late arrivals, and source quality gaps.
You Will :New Data Engineer postings at the employers we follow are up 14% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Toronto, Ontario
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.