# Senior Data Engineer at OPSWAT

> Vietnam · Senior · Data engineering · open. Source: https://alderhq.app/jobs/greenhouse%3Aopswat%3A4562534005 (read 2026-11-22).

## Facts (observed)

- Company: [OPSWAT](https://alderhq.app/companies/opswat)
- Location text: Ho Chi Minh City, Ho Chi Minh City, Vietnam; Vietnam
- Where it can be done from (inferred): Vietnam (evidence: "Location: Ho Chi Minh City, Ho Chi Minh City, Vietnam; Vietnam")
- Posted: 2025-05-14 (557 days ago)
- First seen by alder: 2026-11-15 · last verified: 2026-11-19
- Reposted: 0 times · edited: 0 times
- Apply on the employer's site: https://www.opswat.com/jobs/4562534005?gh_jid=4562534005
- Skills listed (inferred): PostgreSQL, Azure, Terraform, Airflow, dbt

## Pay and sponsorship

- Posted pay: not posted

## Description (the employer's text)

OPSWAT, a global leader in IT, OT, and ICS critical infrastructure cybersecurity, delivers an end-to-end platform that gives public and private sector organizations and enterprises the critical advantage needed to protect their complex networks, secure their devices, and ensure compliance. Over the last 20 years our commitment to innovative technology has earned the trust of more than 1,700 organizations, governments, and institutions globally, solidifying our role in protecting the world’s critical infrastructure and securing our way of life.

### The Position

OPSWAT's data platform ingests from more than forty business systems such as CRM, finance, HR, marketing, support, product telemetry, lands the raw output in a Delta lakehouse, refines it through bronze and silver, and publishes marts that downstream consuming applications read. Apache Airflow on AKS orchestrates it, dbt Core models it, and the warehouse is moving from Microsoft Fabric Warehouse to Azure Database for PostgreSQL while all of that stays running.

You own that path end to end, not a link of it: a source nobody has ingested before, carried all the way to a table a business user can open in a dashboard, and everything in between that decides whether the number is right and arrives on time. The extraction that survives pagination, throttling and a schema that changed without telling anyone; the schedule that fires when the data lands rather than when the clock says; the silver table that refuses bad rows instead of passing them downstream; the mart whose columns are documented and whose keys are tested; the semantic-layer definition that makes it usable; and the freshness and the cost of the whole arrangement.

Senior Data Engineering owns the modelling standards and the parity proof that a dbt mart matches the legacy procedure it replaces. You own the path those models sit on; the pipeline that feeds them and the serving layer that consumes them and you build marts to that standard rather than to your own. The seam is real and it is worked together: you bring the source contract, the schedule and the serving behaviour; they bring the layer rules and the value comparison.

You will work in an AI-assisted engineering workflow, where agentic tooling carries the mechanical parts and your judgement stays on the design: what a source's contract is, where a pipeline should fail loudly, and what a dashboard can afford to query.

### What you will be doing

- Onboard sources end to end: authentication, pagination, rate limits, incremental watermarks, landing, bronze, silver with quality gates, warehouse sync as one DAG family per data source, not a bespoke script per table.
- Own orchestration: DAGs triggered on data arrival, idempotent re-runs, backfills that do not double-count, pod sizing that fits the work, and alerts that page a human only when a human is needed.
- Build the last mile: the marts and the semantic-layer definitions on top of them, so a metric in Zenlytic or a chart in Superset resolves to a column that means what its name says.
- Keep the lakehouse healthy: compaction, Z-ordering chosen from real query patterns, vacuum only inside retention, and schema evolution that does not break a consumer.
- Make performance a measured number: before and after on the pipeline you tuned, capacity spend on the warehouse, caching or pre-aggregation where a dashboard is paying for the same scan every morning.
- Set and defend freshness and completeness expectations per source; when one breaks, diagnose to root cause and write it down.
- Run the platform underneath: AKS workloads, Helm or Kustomize, Terraform, image builds and CI/CD, Key Vault and managed identity, least-privilege access to every store you touch.
- Review pull requests on pipelines and models, and keep runbooks and standards current enough that the next engineer does not need to ask you.
- Work with the Analytics Engineers and Product Analysts who own the business definitions your marts serve, so a definition change and a pipeline change land in the right order.

---
Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/greenhouse%3Aopswat%3A4562534005 and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.
