Back to jobs

Data Engineer

Pay
Pay not listed
Work setting
Remote — work setting source
Azumo builds and operates production AI systems for companies ranging from seed-stage startups to Meta. We are hiring a Data Engineer to own the layer everything else depends on: ingestion and transformation pipelines, storage and warehouse design, and the retrieval infrastructure that AI systems query. The role is fully remote across Latin America, aligned to your client's working day. You will not be building pipelines that work until the schema changes. Azumo has shipped production data systems since 2016, and the work here is judged downstream: whether a model can be trained on what you deliver, whether a retrieval query returns the right passage, whether a number survives being questioned by the client.
Read the full posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full-time
From the employer’s posting

What you’ll work on

Full posting
  • Build batch and streaming ingestion and transformation pipelines

  • Design warehouse and lakehouse storage with partitioning and cost control

  • Build chunking, embedding and indexing pipelines that feed RAG retrieval

  • Maintain data quality tests, lineage and alerting for downstream users

  • Implement PII masking, row and column access, retention and audit trails

From the employer’s posting
Batch and streaming ingestion on Spark, Kafka, dbt and Airflow
Warehouse and lakehouse design on Snowflake, BigQuery, Redshift or Databricks
The chunking, embedding and indexing pipelines that feed RAG systems
Tests, expectations, lineage and alerting.
PII classification, masking, row and column level access, retention and deletion

What you’ll bring

All qualifications

Core experience

  • 5+ years building and operating production data pipelines
  • Python and SQL as primary languages
  • Experience designing data warehouses or lakehouses
  • Distributed processing with Spark, Kafka, Flink or equivalent
  • Orchestration with Airflow, Dagster or Prefect

Preferred experience

  • Experience with cloud-based managed services like Airflow, Glue, Elastic stack, Amazon Redshift, Snowflake, BigQuery, Azure SQL Db, EMR, Databricks.
  • Prior experience with notebooks using Jupyter, Google Collab, or similar.
Qualification wording
5+ years building and operating production data pipelines
with Python and SQL as your primary languages
Deep expertise in designing and building data warehouses or lakehouses
Distributed processing at production scale with Spark, Kafka, Flink or equivalent
Orchestration as an engineering discipline rather than a cron replacement: Airflow, Dagster or Prefect
Experience with cloud-based managed services like Airflow, Glue, Elastic stack, Amazon Redshift, Snowflake, BigQuery, Azure SQL Db, EMR, Databricks.
Prior experience with notebooks using Jupyter, Google Collab, or similar.
Education & alternatives
- Clear written and spoken English, C1 or above, and the confidence to explain a technical trade-off directly to a client. - Bachelor's degree in Computer Science, Data Science, or a related field, or equivalent professional experience. Preferred qualifications

Benefits in the posting

Full benefits wording
  • Paid time off (PTO)
  • AI Training
  • Mentored career development
  • Profit sharing

From the employer’s posting.

About Azumo

We provide nearshore AI engineering teams to organizations that need production AI faster than they can hire for it: as an embedded engineering team, as AI staff augmentation alongside an existing team, or as a full project build.

In the employer’s words · Read in context

Apply at Azumo

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
4
Last seen by us
Nov 21, 2026
Employer says posted
Sep 22, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 3

Early. Similar jobs usually come down between day 6 and day 56.

From 14,766 similar postings that came down. Coming down is not always a hire.

Azumo is hiring

4 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add 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.

  • Python
  • SQL
  • AWS
  • Azure
  • BigQuery
  • Databricks
  • dbt
  • Docker
  • Kafka
  • Prefect
  • Redshift
  • Snowflake
  • Terraform
  • Airflow
  • Dagster
  • Go
Where the posting names them
Basic qualifications - 5+ years building and operating production data pipelines, with Python and SQL as your primary languages, plus the engineering fundamentals that go with it: testing, code review, CI/CD, Git, containers, and orchestration. - Deep expertise in designing and building data warehouses or lakehouses, including dimensional modeling, incremental processing, and the cost and performance trade-offs behind each choice.
- Streaming, real-time or high-throughput workloads. - Experience with cloud-based managed services like Airflow, Glue, Elastic stack, Amazon Redshift, Snowflake, BigQuery, Azure SQL Db, EMR, Databricks. - Prior experience with notebooks using Jupyter, Google Collab, or similar.
- Sensitive data by default. PII classification, masking, row and column level access, retention and deletion, and an audit trail that holds up when a client asks who read what. - Production operation. Containerized deployment on Azure or AWS, CI/CD, orchestration, observability, and explicit cost and runtime budgets that you own rather than discover after the invoice. - Work inside the client's environment. Their repositories, their standups, sometimes their customer calls. Azumo is SOC 2 certified, client code stays in client repositories, and some engagements carry additional requirements such as HIPAA.
- Transformation under version control, with tests and lineage: dbt or something you built yourself. - Cloud deployment experience, Azure preferred and AWS acceptable, with Docker, CI/CD pipelines, and infrastructure as code (GitHub Actions, Terraform, or Bicep). - Working discipline around pipeline cost, runtime and throughput. You can explain what a pipeline costs to run and what you did about it.
- Storage and modeling. Warehouse and lakehouse design on Snowflake, BigQuery, Redshift or Databricks, with partitioning, file layout and query cost treated as engineering decisions. - The retrieval layer. The chunking, embedding and indexing pipelines that feed RAG systems on pgvector, Pinecone, Qdrant or Azure AI Search, and the freshness, deduplication and permission problems that come with them. - Data quality as a contract. Tests, expectations, lineage and alerting. If a pipeline is wrong, the people downstream should hear it from you and not from the client.
Preferred qualifications - Vector and retrieval infrastructure: pgvector, Pinecone, Qdrant, FAISS or Azure AI Search, and the retrieval-quality problems that come with it. - Streaming, real-time or high-throughput workloads.
- Ingestion and transformation pipelines. Batch and streaming ingestion on Spark, Kafka, dbt and Airflow, with idempotency, backfills, schema evolution and late-arriving data handled by design rather than by hand. - Storage and modeling. Warehouse and lakehouse design on Snowflake, BigQuery, Redshift or Databricks, with partitioning, file layout and query cost treated as engineering decisions. - The retrieval layer. The chunking, embedding and indexing pipelines that feed RAG systems on pgvector, Pinecone, Qdrant or Azure AI Search, and the freshness, deduplication and permission problems that come with them.
What you will build - Ingestion and transformation pipelines. Batch and streaming ingestion on Spark, Kafka, dbt and Airflow, with idempotency, backfills, schema evolution and late-arriving data handled by design rather than by hand. - Storage and modeling. Warehouse and lakehouse design on Snowflake, BigQuery, Redshift or Databricks, with partitioning, file layout and query cost treated as engineering decisions.
- Orchestration as an engineering discipline rather than a cron replacement: Airflow, Dagster or Prefect, with retries, idempotency and backfill strategy you can defend. - Transformation under version control, with tests and lineage: dbt or something you built yourself. - Cloud deployment experience, Azure preferred and AWS acceptable, with Docker, CI/CD pipelines, and infrastructure as code (GitHub Actions, Terraform, or Bicep).
- Deep expertise in designing and building data warehouses or lakehouses, including dimensional modeling, incremental processing, and the cost and performance trade-offs behind each choice. - Distributed processing at production scale with Spark, Kafka, Flink or equivalent, including the failure modes that only appear under load. - Orchestration as an engineering discipline rather than a cron replacement: Airflow, Dagster or Prefect, with retries, idempotency and backfill strategy you can defend.
- Distributed processing at production scale with Spark, Kafka, Flink or equivalent, including the failure modes that only appear under load. - Orchestration as an engineering discipline rather than a cron replacement: Airflow, Dagster or Prefect, with retries, idempotency and backfill strategy you can defend. - Transformation under version control, with tests and lineage: dbt or something you built yourself.

Your next step

Complete your application on apply.workable.com. The employer’s form will show what is required.

Applying through Workable

  • No account needed. You can import your resume to fill in the form, or skip that and fill it in yourself.

Already applied? Track this application

Job description

View original posting ↗

Azumo builds and operates production AI systems for companies ranging from seed-stage startups to Meta. We are hiring a Data Engineer to own the layer everything else depends on: ingestion and transformation pipelines, storage and warehouse design, and the retrieval infrastructure that AI systems query. The role is fully remote across Latin America, aligned to your client's working day.

You will not be building pipelines that work until the schema changes. Azumo has shipped production data systems since 2016, and the work here is judged downstream: whether a model can be trained on what you deliver, whether a retrieval query returns the right passage, whether a number survives being questioned by the client.

Where this role sits

Azumo's engineering organization is built around four lanes. The Data Scientist lane owns the question and the method. The AI Engineer lane owns production behavior. The Software Engineer lane owns AI-augmented product delivery. This role is the Data Engineer lane, and it owns pipelines, storage, and the retrieval layer.

One question places the boundary: when the output is wrong, whose problem is it? "The data was missing, stale, or wrong by the time it arrived" is yours."The system did the wrong thing with data that was correct" is the AI Engineer's.

Not quite your profile? Check our other openings:

- If you decide what to measure and which method answers it — Data Scientist

- If you own how an AI system behaves in production — AI Engineer

- If you ship product software with agents in your toolchain — AI-Augmented Software Engineer

- If you've done all of the above and answered to the client directly — Forward Deployed Engineer

What you will build

- Ingestion and transformation pipelines. Batch and streaming ingestion on Spark, Kafka, dbt and Airflow, with idempotency, backfills, schema evolution and late-arriving data handled by design rather than by hand.

- Storage and modeling. Warehouse and lakehouse design on Snowflake, BigQuery, Redshift or Databricks, with partitioning, file layout and query cost treated as engineering decisions.

- The retrieval layer. The chunking, embedding and indexing pipelines that feed RAG systems on pgvector, Pinecone, Qdrant or Azure AI Search, and the freshness, deduplication and permission problems that come with them.

- Data quality as a contract. Tests, expectations, lineage and alerting. If a pipeline is wrong, the people downstream should hear it from you and not from the client.

- Sensitive data by default. PII classification, masking, row and column level access, retention and deletion, and an audit trail that holds up when a client asks who read what.

- Production operation. Containerized deployment on Azure or AWS, CI/CD, orchestration, observability, and explicit cost and runtime budgets that you own rather than discover after the invoice.

- Work inside the client's environment. Their repositories, their standups, sometimes their customer calls. Azumo is SOC 2 certified, client code stays in client repositories, and some engagements carry additional requirements such as HIPAA.

How we work

Our engineers build with AI every day. Claude Code, Codex, and similar tools are part of the standard toolchain here, not an experiment. We run an automated audit across the whole codebase on day one and every day after, grading security, cost, and architecture findings by severity with the exact file and line, so a small team can move quickly without quality drifting. We stay vendor-neutral across OpenAI, Anthropic, and open-weight models, and we run Valkyrie, our own production layer, when a single interface to any model is the right call.

About Azumo

Azumo is a San Francisco based software development company that has been building intelligent applications since 2016. We provide nearshore AI engineering teams to organizations that need production AI faster than they can hire for it: as an embedded engineering team, as AI staff augmentation alongside an existing team, or as a full project build. Our engineers work from Latin America, aligned to United States time zones, and have delivered for Twitter, Meta, Discovery Channel, Omnicom, UnitedHealth, and CENTEGIX.

We hire for seniority and test for it before anyone joins a client team. We support engineers in going deep on the modern AI stack, and we give time back to open-source work, community teaching, and philanthropy.

Apply at https://azumo.com/join-our-team or write to us at people@azumo.com.

Requirements

Basic qualifications

- 5+ years building and operating production data pipelines, with Python and SQL as your primary languages, plus the engineering fundamentals that go with it: testing, code review, CI/CD, Git, containers, and orchestration.

- Deep expertise in designing and building data warehouses or lakehouses, including dimensional modeling, incremental processing, and the cost and performance trade-offs behind each choice.

- Distributed processing at production scale with Spark, Kafka, Flink or equivalent, including the failure modes that only appear under load.

- Orchestration as an engineering discipline rather than a cron replacement: Airflow, Dagster or Prefect, with retries, idempotency and backfill strategy you can defend.

- Transformation under version control, with tests and lineage: dbt or something you built yourself.

- Cloud deployment experience, Azure preferred and AWS acceptable, with Docker, CI/CD pipelines, and infrastructure as code (GitHub Actions, Terraform, or Bicep).

- Working discipline around pipeline cost, runtime and throughput. You can explain what a pipeline costs to run and what you did about it.

- Active use of AI-assisted coding tools such as Claude Code, Cursor, or GitHub Copilot in real delivery work.

- Clear written and spoken English, C1 or above, and the confidence to explain a technical trade-off directly to a client.

- Bachelor's degree in Computer Science, Data Science, or a related field, or equivalent professional experience.

Preferred qualifications

- Vector and retrieval infrastructure: pgvector, Pinecone, Qdrant, FAISS or Azure AI Search, and the retrieval-quality problems that come with it.

- Streaming, real-time or high-throughput workloads.

- Experience with cloud-based managed services like Airflow, Glue, Elastic stack, Amazon Redshift, Snowflake, BigQuery, Azure SQL Db, EMR, Databricks.

- Prior experience with notebooks using Jupyter, Google Collab, or similar.

- Delivery under a compliance regime such as SOC 2 or HIPAA.

- Contributions to open-source data libraries, published technical writing, or active participation in the data engineering community.

Benefits

  • Paid time off (PTO)
  • U.S. Holidays
  • AI Training
  • Mentored career development
  • Profit sharing
  • $US remuneration

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

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.

About the role

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.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

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.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Peru

Azumo builds and operates production AI systems for companies ranging from seed-stage startups to Meta. We are hiring a Data Engineer to own the layer everything else depends on: ingestion and transformation pipelines, storage and warehouse design, and the retrieval infrastructure that AI systems query. The role is fully remote across Latin America, aligned to your client's working day. You will not be building pipelines that work until the schema changes. Azumo has shipped production data systems since 2016, and the work here is judged downstream: whether a model can be trained on what you deliver, whether a retrieval query returns the right passage, whether a number survives being questioned by the client.
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.