Back to jobs

Data Engineer (Santo Domingo)

Santo Domingo, Cibao Sur, Dominican Republic

Actively hiring, first seen by us 3 days ago
Pay
Pay not listed
Work setting
On-site — work setting source
Work setup in the employer’s posting: On-site
From the employer’s posting
Employment
Not stated

What you’ll work on

Full posting
  • Design, write, and optimize T-SQL stored procedures for ingestion, processing, and reporting

  • Own schema for large relational databases, including tables, indexes, constraints, and migrations

  • Package and deploy database changes across dev, staging, and production; resolve schema drift

  • Build automated data-integrity and reconciliation checks that run continuously

  • Diagnose and fix query performance problems at production volume

From the employer’s posting
Design, write, and optimize T-SQL stored procedures for real-time ingestion, transactional processing, reporting, and application data access
Own the schema for large relational databases (100+ tables) — tables, indexes, constraints, TVPs, and migration scripts
Package and deploy database changes across multiple instances using SQL Database Projects and SqlPackage/DACPAC, and detect and resolve schema drift between environments
Build automated data-integrity and reconciliation checks that run continuously, not just when someone reports a problem
Diagnose and fix query performance problems: execution plans, missing indexes, correlated subqueries, unbounded scans, and timeouts at production volume

What you’ll bring

All qualifications

Core experience

  • 3+ years professional experience in a database-focused engineering role (Data Engineer, Database Developer, or similar)
  • Experience with SQL Server or Azure SQL in production
  • Experience working across multiple database environments and promoting schema changes between them
  • Experience with database packaging/deployment tooling — SqlPackage, DACPAC, SSDT, Flyway, Liquibase, or equivalent
  • Experience building or maintaining data pipelines / ETL processes

Preferred experience

  • SQL Server Database Projects (SSDT / .sqlproj) and SqlPackage/DACPAC publishing in a CI/CD pipeline
  • Python or PowerShell for data tooling and one-off analysis
  • Experience in domains where output must reconcile exactly and a wrong number has real consequences
Qualification wording
3+ years professional experience in a database-focused engineering role (Data Engineer, Database Developer, or similar)
Experience with SQL Server or Azure SQL in production
Experience working across multiple database environments and promoting schema changes between them
Experience with database packaging/deployment tooling — SqlPackage, DACPAC, SSDT, Flyway, Liquibase, or equivalent
Experience building or maintaining data pipelines / ETL processes
SQL Server Database Projects (SSDT / .sqlproj) and SqlPackage/DACPAC publishing in a CI/CD pipeline
Python or PowerShell for data tooling and one-off analysis
Experience in domains where output must reconcile exactly and a wrong number has real consequences
Apply at TransPerfect

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
5
Last seen by us
Nov 22, 2026
Employer says posted
Sep 24, 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.

TransPerfect is hiring

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

  • C#
  • Python
  • SQL
  • T-SQL
  • Azure
  • Power BI
  • SQL Server
  • SSIS
Where the posting names them
- Data Movement & Analytics: Azure Storage Queues, Azure Table Storage, Azure Blob Storage, Azure Functions, queue drainer services, bulk upsert/apply patterns, Microsoft Fabric (Lakehouse / Warehouse / Data Factory pipelines / Power BI semantic models), CSV/Excel export generation - Consuming Layers: ASP.NET Core (.NET 8) with Dapper, C# — enough to read and reason about how your procedures are called - Infrastructure: Azure (SQL Database, Storage, Key Vault, Application Insights), Azure DevOps Pipelines, sqlcmd / Azure Data Studio / SSMS, Entra ID authentication
- Version control discipline for database objects (Git, migration scripts, or database projects) - Able to read enough C# or another application language to understand how your data layer is consumed Preferred Qualifications
- Azure DevOps (Pipelines, Boards, Repos) - Python or PowerShell for data tooling and one-off analysis What We Value
We're hiring a Data Engineer to own the data layer across our product portfolio. This is a database-first role and a deliberately broad one: you'll write and optimize the T-SQL that our applications run on, design the schema new features are built against, and keep the pipelines that move data from ingestion through processing to reporting correct, fast, and auditable. We're not hiring for a single project. You'll move between products and problem domains — real-time event ingestion, transactional processing, reporting and analytics, historical migrations — so we're looking for someone adaptable who gets productive in an unfamiliar schema quickly and is comfortable owning more than one system at a time.
Tech Stack - Database: Azure SQL, T-SQL, stored procedures, table-valued parameters (TVPs), user-defined functions, temp-table staging patterns, query plan analysis - Packaging & Deployment: SQL Server Database Projects (.sqlproj / SSDT), SqlPackage and DACPAC publishing, schema compare and drift detection, versioned migration scripts, multi-instance (dev / staging / prod) deployment
- Database: Azure SQL, T-SQL, stored procedures, table-valued parameters (TVPs), user-defined functions, temp-table staging patterns, query plan analysis - Packaging & Deployment: SQL Server Database Projects (.sqlproj / SSDT), SqlPackage and DACPAC publishing, schema compare and drift detection, versioned migration scripts, multi-instance (dev / staging / prod) deployment - Data Movement & Analytics: Azure Storage Queues, Azure Table Storage, Azure Blob Storage, Azure Functions, queue drainer services, bulk upsert/apply patterns, Microsoft Fabric (Lakehouse / Warehouse / Data Factory pipelines / Power BI semantic models), CSV/Excel export generation
- Consuming Layers: ASP.NET Core (.NET 8) with Dapper, C# — enough to read and reason about how your procedures are called - Infrastructure: Azure (SQL Database, Storage, Key Vault, Application Insights), Azure DevOps Pipelines, sqlcmd / Azure Data Studio / SSMS, Entra ID authentication Responsibilities
Responsibilities - Design, write, and optimize T-SQL stored procedures for real-time ingestion, transactional processing, reporting, and application data access - Own the schema for large relational databases (100+ tables) — tables, indexes, constraints, TVPs, and migration scripts
- Own the schema for large relational databases (100+ tables) — tables, indexes, constraints, TVPs, and migration scripts - Package and deploy database changes across multiple instances using SQL Database Projects and SqlPackage/DACPAC, and detect and resolve schema drift between environments - Verify data integrity as a first-class deliverable — enforce and validate keys, constraints, and referential integrity; write the checks that catch orphaned, duplicated, and contradictory rows before they reach production consumers
- Pick up unfamiliar schemas and legacy data models across different products and get to a working understanding fast - Write reusable, well-documented SQL that the next engineer can safely change Required Qualifications
- 3+ years professional experience in a database-focused engineering role (Data Engineer, Database Developer, or similar) - Strong T-SQL — stored procedures, CTEs, window functions, temp tables, TVPs, dynamic SQL where it's warranted - Demonstrable query optimization skills: reading execution plans, index design, and diagnosing slow queries at volume
- Relational schema design — normalization, keys, constraints, soft-delete and status-flag patterns, slowly-changing/point-in-time data - Experience with SQL Server or Azure SQL in production - Hands-on data integrity work — constraint and referential-integrity design, duplicate and orphan detection, and writing validation queries that prove a dataset is sound
- Microsoft Fabric experience — Lakehouse, Warehouse, Data Factory pipelines, Dataflows Gen2, OneLake, or Power BI semantic models - SQL Server Database Projects (SSDT / .sqlproj) and SqlPackage/DACPAC publishing in a CI/CD pipeline - Azure SQL specifics — DTU/vCore tuning, Query Store, elastic pools, managed identity authentication
- SQL Server Database Projects (SSDT / .sqlproj) and SqlPackage/DACPAC publishing in a CI/CD pipeline - Azure SQL specifics — DTU/vCore tuning, Query Store, elastic pools, managed identity authentication - Azure Storage — Queues, Tables, and Blobs as part of a data pipeline
- Packaging & Deployment: SQL Server Database Projects (.sqlproj / SSDT), SqlPackage and DACPAC publishing, schema compare and drift detection, versioned migration scripts, multi-instance (dev / staging / prod) deployment - Data Movement & Analytics: Azure Storage Queues, Azure Table Storage, Azure Blob Storage, Azure Functions, queue drainer services, bulk upsert/apply patterns, Microsoft Fabric (Lakehouse / Warehouse / Data Factory pipelines / Power BI semantic models), CSV/Excel export generation - Consuming Layers: ASP.NET Core (.NET 8) with Dapper, C# — enough to read and reason about how your procedures are called
- Azure SQL specifics — DTU/vCore tuning, Query Store, elastic pools, managed identity authentication - Azure Storage — Queues, Tables, and Blobs as part of a data pipeline - Experience in domains where output must reconcile exactly and a wrong number has real consequences
- Point-in-time / temporal data modeling (values and configuration that must be resolved as of a historical timestamp) - Azure Data Factory, SSIS, or equivalent orchestration tooling - Dapper or micro-ORM data access patterns
- Dapper or micro-ORM data access patterns - Azure DevOps (Pipelines, Boards, Repos) - Python or PowerShell for data tooling and one-off analysis
Preferred Qualifications - Microsoft Fabric experience — Lakehouse, Warehouse, Data Factory pipelines, Dataflows Gen2, OneLake, or Power BI semantic models - SQL Server Database Projects (SSDT / .sqlproj) and SqlPackage/DACPAC publishing in a CI/CD pipeline

Your next step

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

Already applied? Track this application

Job description

View original posting ↗

We're hiring a Data Engineer to own the data layer across our product portfolio. This is a database-first role and a deliberately broad one: you'll write and optimize the T-SQL that our applications run on, design the schema new features are built against, and keep the pipelines that move data from ingestion through processing to reporting correct, fast, and auditable.

We're not hiring for a single project. You'll move between products and problem domains — real-time event ingestion, transactional processing, reporting and analytics, historical migrations — so we're looking for someone adaptable who gets productive in an unfamiliar schema quickly and is comfortable owning more than one system at a time.

You'll work across multiple database instances — development, staging, and production — and own the packaging and deployment path between them, so that what's checked into source control is provably what's running. Correctness is not negotiable: the queries you write decide what our applications return and what our reports say. You'll partner closely with the API and frontend engineers who consume your procedures, and you'll be the person who answers "why does this number look wrong?"

Tech Stack

  • Database: Azure SQL, T-SQL, stored procedures, table-valued parameters (TVPs), user-defined functions, temp-table staging patterns, query plan analysis

  • Packaging & Deployment: SQL Server Database Projects (.sqlproj / SSDT), SqlPackage and DACPAC publishing, schema compare and drift detection, versioned migration scripts, multi-instance (dev / staging / prod) deployment

  • Data Movement & Analytics: Azure Storage Queues, Azure Table Storage, Azure Blob Storage, Azure Functions, queue drainer services, bulk upsert/apply patterns, Microsoft Fabric (Lakehouse / Warehouse / Data Factory pipelines / Power BI semantic models), CSV/Excel export generation

  • Consuming Layers: ASP.NET Core (.NET 8) with Dapper, C# — enough to read and reason about how your procedures are called

  • Infrastructure: Azure (SQL Database, Storage, Key Vault, Application Insights), Azure DevOps Pipelines, sqlcmd / Azure Data Studio / SSMS, Entra ID authentication

Responsibilities

  • Design, write, and optimize T-SQL stored procedures for real-time ingestion, transactional processing, reporting, and application data access

  • Own the schema for large relational databases (100+ tables) — tables, indexes, constraints, TVPs, and migration scripts

  • Package and deploy database changes across multiple instances using SQL Database Projects and SqlPackage/DACPAC, and detect and resolve schema drift between environments

  • Verify data integrity as a first-class deliverable — enforce and validate keys, constraints, and referential integrity; write the checks that catch orphaned, duplicated, and contradictory rows before they reach production consumers

  • Build automated data-integrity and reconciliation checks that run continuously, not just when someone reports a problem

  • Diagnose and fix query performance problems: execution plans, missing indexes, correlated subqueries, unbounded scans, and timeouts at production volume

  • Build and maintain data pipelines that move high-volume event data from ingestion queues into processed, queryable, reportable records

  • Write reconciliation queries that prove downstream output ties back to source data — and investigate when it doesn't

  • Handle historical data migrations, backfills, and legacy-to-current data reconciliation

  • Keep paged and non-paged (export) variants of reporting procedures in lockstep so the on-screen grid and the exported file never disagree

  • Model and surface data in Microsoft Fabric for analytics and reporting workloads as we build that capability out

  • Partner with API engineers on contract changes — parameter shape, result sets, and DTO mapping

  • Contribute to CI/CD for database deployments and keep checked-in objects aligned with what's actually deployed

  • Pick up unfamiliar schemas and legacy data models across different products and get to a working understanding fast

  • Write reusable, well-documented SQL that the next engineer can safely change

Required Qualifications

  • 3+ years professional experience in a database-focused engineering role (Data Engineer, Database Developer, or similar)

  • Strong T-SQL — stored procedures, CTEs, window functions, temp tables, TVPs, dynamic SQL where it's warranted

  • Demonstrable query optimization skills: reading execution plans, index design, and diagnosing slow queries at volume

  • Relational schema design — normalization, keys, constraints, soft-delete and status-flag patterns, slowly-changing/point-in-time data

  • Experience with SQL Server or Azure SQL in production

  • Hands-on data integrity work — constraint and referential-integrity design, duplicate and orphan detection, and writing validation queries that prove a dataset is sound

  • Experience working across multiple database environments and promoting schema changes between them

  • Experience with database packaging/deployment tooling — SqlPackage, DACPAC, SSDT, Flyway, Liquibase, or equivalent

  • Experience building or maintaining data pipelines / ETL processes

  • Comfortable working with large datasets and reasoning about correctness, not just output

  • Adaptable across products and domains — you've worked on more than one system and can context-switch without losing rigor

  • Version control discipline for database objects (Git, migration scripts, or database projects)

  • Able to read enough C# or another application language to understand how your data layer is consumed

Preferred Qualifications

  • Microsoft Fabric experience — Lakehouse, Warehouse, Data Factory pipelines, Dataflows Gen2, OneLake, or Power BI semantic models

  • SQL Server Database Projects (SSDT / .sqlproj) and SqlPackage/DACPAC publishing in a CI/CD pipeline

  • Azure SQL specifics — DTU/vCore tuning, Query Store, elastic pools, managed identity authentication

  • Azure Storage — Queues, Tables, and Blobs as part of a data pipeline

  • Experience in domains where output must reconcile exactly and a wrong number has real consequences

  • High-volume event or transactional data processing experience

  • Point-in-time / temporal data modeling (values and configuration that must be resolved as of a historical timestamp)

  • Azure Data Factory, SSIS, or equivalent orchestration tooling

  • Dapper or micro-ORM data access patterns

  • Azure DevOps (Pipelines, Boards, Repos)

  • Python or PowerShell for data tooling and one-off analysis

What We Value

  • Clear, direct communication — say what you mean, flag problems early, ask questions when something is unclear

  • Verifying against the real object — read the deployed procedure, run the query, check the plan; don't trust documentation or assumptions about what the data does, and don't assume one instance matches another

  • Fixing problems at the source instead of working around dirty data downstream

  • Challenging risky or incorrect decisions instead of silently going along

  • Treating data output as something that must be provably correct, with a query that demonstrates it

  • Curiosity across the whole portfolio — willingness to learn a new domain rather than staying in one comfortable corner

  • Pragmatism over over-engineering — solve the problem at hand without gold-plating

In order to apply, please submit your CV in English

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

Santo Domingo, Cibao Sur, Dominican Republic

Working pattern and location restrictions need checking in the full posting.

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.