

Guidehouse is hiring a Data Engineer for its Chennai office to work on an enterprise data platform that supports analytics, reporting and AI solutions. You will build and maintain ingestion pipelines, develop Bronze, Silver and Gold transformations, and put data-quality checks in place so business teams can trust the numbers they use. The work is hands-on and covers deployment, production monitoring and technical documentation, all within architecture patterns set by the platform architect. It suits someone who likes SQL, Python or PySpark, and who wants to see how a lakehouse runs in a professional services setting.
This opening is for candidates who want to work on the engineering side of a modern data platform, where pipelines have to run on schedule and the data has to be right. At Guidehouse, the Data Engineer sits between source systems and the dashboards and AI use cases the business depends on.
Why This Role Matters
Most analytics problems are really data problems. If a source file arrives late or a transformation drops records, every report built on top of it is wrong. This role keeps that chain dependable. You will work with platform, analytics, security and business teams to deliver reliable, reusable datasets instead of one-off extracts.
Hands-On Engineering Role Full-Time Chennai
Core Engineering Work
The daily work revolves around a few connected responsibilities:
Area | What You Will Do |
|---|---|
Ingestion | Build pipelines from databases, APIs, files and enterprise applications using approved integration patterns |
Transformation | Develop Bronze, Silver and Gold layers with reusable engineering practices |
Data Quality | Add completeness, accuracy, consistency and reconciliation checks |
Operations | Monitor production jobs, investigate failures and apply corrective fixes |
Documentation | Maintain source-to-target mappings, lineage and operating procedures |
How Data Moves Through The Platform
Understanding the medallion pattern is probably the most useful preparation you can do before an interview for this role.
Raw data lands in Bronze with minimal changes. Silver cleans, standardizes and validates it. Gold shapes it into business-ready datasets, which feed the semantic models used by analytics teams.
flowchart LR A[Source Systems] --> B[Bronze] B --> C[Silver] C --> D[Gold] D --> E[Semantic Models]
Technology Exposure
The listing points to an Azure-based ecosystem. Experience with Databricks, Microsoft Fabric or comparable tools is expected. Preferred exposure includes Delta Lake, Unity Catalog, OneLake, ADLS Gen2, Azure SQL, Dataverse and Power Platform.
SQL Python PySpark Databricks Microsoft Fabric Azure GitHub Power BI
Production Support Responsibilities
This is not a build-and-hand-off role. You will watch pipelines in production, work out why a job failed or why a refresh is stuck, and trace data discrepancies back to their source. You will also support assigned semantic models, meaning the data preparation and refresh dependencies behind them, working with the Analytics team. Clear root-cause notes and updated job aids are part of how success is measured here.
Teams trust engineers who can explain what broke, why it broke and how it was fixed.
Engineering Standards And Governance
Changes follow GitHub-based CI/CD, testing, release management and environment promotion. Security, access, naming and development standards are applied consistently. Experience with Microsoft Purview or similar lineage and governance tools is a plus, as is any exposure to regulated environments with compliance controls.
What Recruiters May Evaluate
Area | Likely Focus |
|---|---|
SQL | Joins, window functions, aggregations, query tuning |
Python / PySpark | Data cleaning, transformations, handling failures |
Lakehouse concepts | Medallion layers, Delta Lake basics |
Data quality | Reconciliation and validation logic |
Version control | Branching, pull requests, release flow |
Communication | Explaining pipeline issues to non-technical teams |
Things Worth Learning Before Applying
Build a small project that ingests a CSV and an API into raw tables, cleans them in a second layer and produces a summary table in a third. Add a few validation checks and keep the code in GitHub with a clear README. If you can, explore a free Azure or Databricks tier. A certification such as Azure Data Engineer Associate, Fabric Data Engineer or Databricks Data Engineer Associate would strengthen your profile, since the listing names these as preferred.
Projects
Where This Role Can Lead
Data engineers here can grow towards platform engineering, data architecture, or analytics engineering. Working under a Principal Data Platform Architect also gives you a close view of how approved patterns and guardrails are designed, which is useful if you later want an architecture role.
Keywords For Resume
Data Engineer • SQL • Python • PySpark • Databricks • Microsoft Fabric • Azure • ADLS Gen2 • Azure SQL • Delta Lake • Unity Catalog • OneLake • Lakehouse Architecture • Bronze Silver Gold • ETL • Data Ingestion • Data Quality • Data Reconciliation • GitHub • CI/CD • Power BI • Semantic Models • Data Lineage • Microsoft Purview • Production Support
Final Perspective
This role offers real exposure to how an enterprise data platform is built, governed and kept running. If you have solid SQL, some Python or PySpark, and a project that shows you understand the layered lakehouse approach, it is worth a serious application.
The above article is written by me, a person interested in technology, automobiles, modern gadgets, movies, music, and clean aesthetics.



