Hiring Alert - Senior Data Engineer - Hybrid - BI-CBFEB

Hello Everyone,

Greetings from Bounteous!!

We have an excellent Opening for the below Skills:

Job Title: Senior Data Engineer

Experience: 6+Years

Job Location: Chennai / Bangalore / Hyderabad / Gurugram

Kindly share the updated Profile to [email removed] along with the below details,

Current CTC:

Expected CTC:

Available Time to Join:

Preferred Location:

Role Summary

The Senior Data Engineer partners directly with the US-based Lead Data Engineer/Strategist to understand the client's existing systems landscape and build the account's core data schema from scratch. This is a foundational, hands-on role before any pipeline or integration work can happen, this person has to make sense of the client's current systems (CRM, ERP, MDM, and any legacy data stores) and translate that understanding into a clean, well-documented data model that the rest of the delivery team builds on. The account's technology stack is still being finalized, so this role is technology-agnostic in tooling but not in rigor: strong data modeling fundamentals matter more than any single platform. Delivery on this account uses an agent-orchestrated development model, so hands-on experience directing AI coding agents is expected here as well.

Key Responsibilities

• Work side-by-side with the US-based Lead Data Engineer/Strategist to reverse-engineer and document the client's current-state systems: source systems, data owners, existing entities, and known data-quality issues.
• Design the account's core data schema from scratch entities, relationships, keys, and normalization/denormalization decisions — based on business requirements and the current-state system understanding.
• Produce clear data model documentation (ER diagrams, data dictionaries, field-level definitions) that the Architect(s) and engineering pods can build against.
• Identify and document data lineage: where each piece of data originates, how it moves between systems, and where transformation or validation needs to happen.
• Surface data-quality risks and system-of-record conflicts early — e.g., the same entity represented differently across systems — and propose resolution approaches to the Lead Data Engineer/Strategist.
• Build and validate early-stage data pipelines/prototypes to prove out the proposed schema against real (or representative) data before it'sfinalized.
• Direct and prompt AI coding agents (e.g., Claude Code or equivalent) to accelerate schema exploration, data profiling scripts, and pipeline prototyping, then review and validate the output.
• Partner with the Architect(s) and Product Manager to ensure the data schema supports both current requirements and reasonably anticipated future needs, without over-engineering.
• Iterate on the schema as new systems or requirements are discovered during discovery and early build phases.
• Hand off a stable, documented schema and migration/seeding approach to the wider engineering team once foundational design work is complete.

Required Qualifications

1. 6+ years of data engineering experience, including direct experience designing data schemas/data models from scratch rather than only extending existing ones.

• Strong grounding in data modeling fundamentals: normalization, entity-relationship design, key/index strategy, and trade-offs between transactional and analytical models.
• Demonstrated experience investigating and documenting unfamiliar or legacy systems to understand data flow and structure before designing a new schema.
• Hands-on experience with SQL and at least one modern data platform (cloud data warehouse, relational database, or similar) sufficient to prototype and validate schema decisions.
• Experience building or prototyping data pipelines (batch or real-time) to validate a proposed data model against real data.
• Hands-on experience using AI coding agents (e.g., Claude Code or an equivalent agentic development tool) — required, as this engagement uses an agent-orchestrated development model.
• Comfortable working in close, iterative partnership with a senior counterpart (Lead Data Engineer/Strategist) rather than working from a fully specified handoff.
• Strong written communication skills — this role is expected to produce documentation other teams will build against, not just working code.