Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 8 days ago

Data Engineer (Santo Domingo)

TGS643 open roles

Where
Santo Domingo, Cibao Sur, Dominican Republic
Work mode
On site
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowData Engineer (Santo Domingo)TGS · Santo Domingo, Cibao Sur, Dominican Republic

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on TGS's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

7.8% of postings close within 7 days. Measured by our own scanner across the market.

Share of postings closed within
  1. 1.6%1 day
  2. 3.4%3 days
  3. 7.8%7 days
  4. 14.3%14 days
  5. 33.7%30 days
This job: posted 8 days ago

The 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

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against TGS's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on TGS's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    TGS's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.