Time since we first saw it
Day 3
Early. Similar jobs usually come down between day 6 and day 56.
From 14,770 similar postings that came down. Coming down is not always a hire.
Hyderabad, TG, India
Actively hiring, first seen by us 3 days agoCompensation and Logistics Location: On-site at our Hyderabad (Softobiz) office. This is not a remote role. Reporting: Reports to the Engineering Owner, with regular working interactions across product, analytics, growth and external data partners.Read the full posting
Experience: 8 – 12 Years Employment Type: Full-Time Shift: Overlap with US Team (evening IST preferred)Read the full posting
We are looking for a Staff Data Engineer to own our end-to-end data platform — from raw event ingestion, through the warehouse, to the analytics marts that the business, product and marketing teams rely on every day.
This is a hands-on individual-contributor role.
Design and maintain the BigQuery warehouse and dbt project layering
Build ingestion pipelines from the CDP, product database, billing and ad platforms
Stitch anonymous and logged-in records into one canonical customer key
Build revenue, orders, subscription and LTV marts
Add data quality tests and reconciliations against payment and ad platform data
We are looking for a Staff Data Engineer to own our end-to-end data platform — from raw event ingestion, through the warehouse, to the analytics marts that the business, product and marketing teams rely on every day. You will be the person who makes sure the numbers we make decisions on are accurate, fresh, reproducible and trusted.
This is a hands-on individual-contributor role. You will partner daily with engineering, analytics, product, growth and external data partners. Success looks like: one canonical patient or customer key across every system, a well-modelled warehouse that answers business questions in SQL rather than spreadsheets, and a data platform that product, marketing and leadership genuinely trust.
Warehouse architecture and modelling — BigQuery (or equivalent) as the single source of truth
Ingestion pipelines — event streams from the CDP (Segment or equivalent) landing cleanly in the warehouse
Identity resolution in the warehouse — stitching anonymous, edge-level and identified user records into one canonical key
Core marts — revenue, orders, subscriptions, cohorts, LTV, funnel conversion
reconciliation checks between systems (for example: warehouse orders vs payment processor, warehouse conversions vs ad-platform reports)
8–12 years in data engineering or analytics engineering at consumer-facing digital businesses — ideally including at least one direct-to-consumer, e-commerce, subscription or marketplace product.
Experience operating a dbt repo shared between an internal team and an external data partner (or vendor) — conventions, code review, ownership boundaries.
Experience designing identity resolution in the warehouse — merging anonymous, cookie-level, logged-in and server-generated identifiers into one canonical customer key, and publishing that key for downstream systems to join on.
Experience with Segment Unify, identity-graph services, or custom identity-resolution frameworks.
Hands-on experience building marts for revenue, orders, subscriptions, cohorts, LTV and funnel analysis — and reconciling those marts against authoritative systems (payment processors, billing, ad platforms).
Familiarity with streaming patterns — Pub/Sub, Kafka, Kinesis — and when to prefer them over batch.
Innovation begins with like-minded people aiming to transform the world together.
In the employer’s words · Read in context
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 3
Early. Similar jobs usually come down between day 6 and day 56.
From 14,770 similar postings that came down. Coming down is not always a hire.
3 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd 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.
- Hands-on experience building marts for revenue, orders, subscriptions, cohorts, LTV and funnel analysis — and reconciling those marts against authoritative systems (payment processors, billing, ad platforms). - Python for data work — transformations, orchestration DAGs, small internal tools, and scripting around the warehouse. You do not need to be a backend engineer. - Working knowledge of at least one workflow orchestrator — Airflow, Prefect, Dagster, or equivalent — and the operational discipline that goes with it (idempotency, backfills, retries, alerting).
Orchestration Airflow, Prefect, Dagster, or an equivalent DAG runner. dbt Cloud scheduling for dbt-only pipelines. Ingestion Segment (CDP → warehouse), Fivetran or Airbyte (SaaS → warehouse), custom Python ingestion where needed. Reverse-ETL / Activation Polytomic (preferred), Hightouch, Census — mapping marts to ad-platform, lifecycle and experimentation destinations.
BI / Visualisation Omni, Looker, Mode, Metabase, Tableau — warehouse-native semantic modelling preferred. Languages SQL (advanced), Python (fluent), Jinja (dbt); shell scripting as needed. Storage & Cloud Google Cloud Platform primary (Cloud Storage, IAM, Pub/Sub, Cloud Run / Cloud Functions).
We are looking for a Staff Data Engineer to own our end-to-end data platform — from raw event ingestion, through the warehouse, to the analytics marts that the business, product and marketing teams rely on every day. You will be the person who makes sure the numbers we make decisions on are accurate, fresh, reproducible and trusted. This is a hands-on individual-contributor role. You will partner daily with engineering, analytics, product, growth and external data partners. Success looks like: one canonical patient or customer key across every system, a well-modelled warehouse that answers business questions in SQL rather than spreadsheets, and a data platform that product, marketing and leadership genuinely trust. Scope note: this role owns warehouse architecture, pipelines and data modelling. The sister MarTech Engineering role owns event capture at the edge and the delivery of conversion signals to ad platforms. Both roles share one source of truth (the warehouse) and collaborate on the hand-off between event streams and warehouse tables.
- Production experience with dbt — Core or Cloud — including model layering, incremental strategies, snapshots, tests, documentation, exposures, and managing a multi-contributor repo through pull requests. - Fluent SQL — advanced window functions, CTEs, pivoting, session stitching, slowly-changing-dimension patterns. You can read a 200-line query and tell us what is wrong with it. - Experience designing identity resolution in the warehouse — merging anonymous, cookie-level, logged-in and server-generated identifiers into one canonical customer key, and publishing that key for downstream systems to join on.
What You'll Own - Warehouse architecture and modelling — BigQuery (or equivalent) as the single source of truth, designed to serve both analytics and activation use cases. - dbt project ownership — model layering (staging → intermediate → marts), naming conventions, tests, documentation, exposures, and the promotion workflow from dev to production.
- 8–12 years in data engineering or analytics engineering at consumer-facing digital businesses — ideally including at least one direct-to-consumer, e-commerce, subscription or marketplace product. - Deep, hands-on experience designing and maintaining a warehouse on BigQuery, Snowflake or Redshift. You can explain partitioning, clustering, materialised views, and cost / performance trade-offs from memory. - Production experience with dbt — Core or Cloud — including model layering, incremental strategies, snapshots, tests, documentation, exposures, and managing a multi-contributor repo through pull requests.
Category Tools Data Warehouse BigQuery (required), Snowflake or Redshift. Strong grasp of partitioning, clustering, cost controls. Transformation dbt Core or dbt Cloud (required), dbt tests, snapshots, exposures, packages.
- You treat the warehouse as a product — versioned, documented, tested, with clear ownership of every model and every downstream exposure. - You are as comfortable debugging a BigQuery cost regression as you are explaining an attribution or LTV model to senior leadership. - You write dbt tests before you write dashboards. You would rather catch the problem in CI than in a Monday standup.
- Working knowledge of at least one workflow orchestrator — Airflow, Prefect, Dagster, or equivalent — and the operational discipline that goes with it (idempotency, backfills, retries, alerting). - Comfort integrating warehouse output into reverse-ETL tooling (Polytomic, Hightouch or Census) so that audiences, conversion events and customer traits can be activated in ad platforms, lifecycle tools and experimentation systems. - A bias for data contracts and tests over heroics — you treat a broken dashboard as a platform failure to be prevented, not a one-off to be patched.
Ingestion Segment (CDP → warehouse), Fivetran or Airbyte (SaaS → warehouse), custom Python ingestion where needed. Reverse-ETL / Activation Polytomic (preferred), Hightouch, Census — mapping marts to ad-platform, lifecycle and experimentation destinations. Product Analytics (consumer) Mixpanel, Amplitude, or Heap — you will not own these tools, but you will land their events and feed their user properties from the warehouse.
- Warehouse architecture and modelling — BigQuery (or equivalent) as the single source of truth, designed to serve both analytics and activation use cases. - dbt project ownership — model layering (staging → intermediate → marts), naming conventions, tests, documentation, exposures, and the promotion workflow from dev to production. - Ingestion pipelines — event streams from the CDP (Segment or equivalent) landing cleanly in the warehouse, plus structured loads from the product database, billing / payments, ad platforms and third-party SaaS systems.
- Reverse-ETL / activation models — warehouse tables purpose-built to feed ad-platform conversions APIs, lifecycle marketing, audiences and experimentation tools. - Data quality and observability — dbt tests, freshness monitors, row-count alerts, reconciliation checks between systems (for example: warehouse orders vs payment processor, warehouse conversions vs ad-platform reports). - Data governance — PII / PHI handling, column-level masking, row-level security where required, access policies, and the documentation that makes those policies auditable.
- Data governance — PII / PHI handling, column-level masking, row-level security where required, access policies, and the documentation that makes those policies auditable. - Orchestration and CI/CD — scheduled runs, retries, incremental strategies, pull-request-based dbt reviews, automated tests in CI. - Partnership with external data partners and the sister MarTech Engineering function — clear ownership lines, shared conventions, joint on-call for pipeline incidents.
- Deep, hands-on experience designing and maintaining a warehouse on BigQuery, Snowflake or Redshift. You can explain partitioning, clustering, materialised views, and cost / performance trade-offs from memory. - Production experience with dbt — Core or Cloud — including model layering, incremental strategies, snapshots, tests, documentation, exposures, and managing a multi-contributor repo through pull requests. - Fluent SQL — advanced window functions, CTEs, pivoting, session stitching, slowly-changing-dimension patterns. You can read a 200-line query and tell us what is wrong with it.
Data Warehouse BigQuery (required), Snowflake or Redshift. Strong grasp of partitioning, clustering, cost controls. Transformation dbt Core or dbt Cloud (required), dbt tests, snapshots, exposures, packages. Orchestration Airflow, Prefect, Dagster, or an equivalent DAG runner. dbt Cloud scheduling for dbt-only pipelines.
Transformation dbt Core or dbt Cloud (required), dbt tests, snapshots, exposures, packages. Orchestration Airflow, Prefect, Dagster, or an equivalent DAG runner. dbt Cloud scheduling for dbt-only pipelines. Ingestion Segment (CDP → warehouse), Fivetran or Airbyte (SaaS → warehouse), custom Python ingestion where needed.
Governance & PII Column-level security, masking policies, row-level access, data-classification tagging, audit logging. Dev workflow Git, GitHub / GitLab, pull-request reviews, dbt CI, unit and schema tests, dbt docs. Collaboration Linear, Slack, Google Docs & Sheets, Confluence or Notion.
- Healthcare, fintech, or other privacy-sensitive domain experience — designing a warehouse that respects PII / PHI boundaries and survives audit. - Experience operating a dbt repo shared between an internal team and an external data partner (or vendor) — conventions, code review, ownership boundaries. - Experience with Segment Unify, identity-graph services, or custom identity-resolution frameworks.
- You are as comfortable debugging a BigQuery cost regression as you are explaining an attribution or LTV model to senior leadership. - You write dbt tests before you write dashboards. You would rather catch the problem in CI than in a Monday standup. - You draw scope lines honestly — you know where your layer ends and the MarTech, product or ML layer begins, and you document the hand-off.
How to Apply Send your resume and a short note (5–10 sentences) describing the most complex data platform or warehouse migration you have personally led — what you inherited, what you shipped, and what you would do differently. Links to open-source contributions, dbt packages, public writing or talks are welcome. About Softobiz:
- Hands-on with LTV or propensity modelling (regression, survival or tree-based), and with getting those predictions into the warehouse as first-class tables. - Familiarity with streaming patterns — Pub/Sub, Kafka, Kinesis — and when to prefer them over batch. - Prior early-hire data platform experience at a growth-stage product company, where you set the conventions rather than inherited them.
Product Analytics (consumer) Mixpanel, Amplitude, or Heap — you will not own these tools, but you will land their events and feed their user properties from the warehouse. BI / Visualisation Omni, Looker, Mode, Metabase, Tableau — warehouse-native semantic modelling preferred. Languages SQL (advanced), Python (fluent), Jinja (dbt); shell scripting as needed.
- Python for data work — transformations, orchestration DAGs, small internal tools, and scripting around the warehouse. You do not need to be a backend engineer. - Working knowledge of at least one workflow orchestrator — Airflow, Prefect, Dagster, or equivalent — and the operational discipline that goes with it (idempotency, backfills, retries, alerting). - Comfort integrating warehouse output into reverse-ETL tooling (Polytomic, Hightouch or Census) so that audiences, conversion events and customer traits can be activated in ad platforms, lifecycle tools and experimentation systems.
Languages SQL (advanced), Python (fluent), Jinja (dbt); shell scripting as needed. Storage & Cloud Google Cloud Platform primary (Cloud Storage, IAM, Pub/Sub, Cloud Run / Cloud Functions). Governance & PII Column-level security, masking policies, row-level access, data-classification tagging, audit logging.
Complete your application on softobiz.keka.com. The employer’s form will show what is required.
Already applied? Track this application
New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
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.
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.
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.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Hyderabad, TG, India
Staff Data Engineer Data Platform & Analytics Engineering · Hyderabad (On-site, Softobiz office) About the Role
Compensation and Logistics - Location: On-site at our Hyderabad (Softobiz) office. This is not a remote role. - Reporting: Reports to the Engineering Owner, with regular working interactions across product, analytics, growth and external data partners.
No clear work-authorization passage found. Eligibility is unconfirmed.