Jobs / United States / Transperfect

Transperfect

Data Engineer (Santo Domingo)

Santo Domingo, Cibao Sur, Dominican Republic Posted 23 days ago

Apply on employer site ↗ Tailor my CV first Source: Company careers site

Optional: we can tailor a CV and cover letter for this job from your real experience first (the first one is free).

Skills this job asks for

SQLAzureWarehouse operationsPower BIExcelC#ReconciliationData engineeringCI/CD

Add your CV (free) to see which of these your CV is missing.

Sponsorship verdict

No sponsorship evidence yet

No government record and no wording either way. Not a refusal: ask the recruiter.

  • No government sponsor record hereThis employer does not appear with approvals in the government data SponsorApply holds.
  • The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
  • No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
  • What Transperfect paid sponsored hires in similar roles1 certified filing for “Quality Assurance Development Engineer” (Software Quality Assurance Analysts and Testers) in TX: $99k–$99k, median $99k.
  • Confirmed live todayWhen a source last listed this job as open.
Details and sources
No salary bar for this route
H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
What Transperfect paid sponsored hires in similar roles
1 certified filing for “Quality Assurance Development Engineer” (Software Quality Assurance Analysts and Testers) in TX: $99k–$99k, median $99k. Most were filed at wage level II (100%) — 2 lottery entries, ≈31% projected selection odds for cap-subject employers. Source: US Department of Labor LCA disclosure data (Oct 2025 – Jun 2026).

US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).

A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.

Before you apply

Sponsorship unknown

No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.

These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →

About the role

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

Apply on employer site ↗