Saikiran Chennuri

Data you can trace, name, and answer for.

I work in data governance and metadata management: cataloging large estates, drawing lineage through them, and putting owners and rules on the data that regulators and decision-makers depend on. Seven years across warehouses, catalogs, and now a bank's operations.

SOURCES CATALOG GOVERNANCE Oracleactuarial, finance SQL Serverpolicy, claims Teradatalegacy warehouse Azure ADLSdata lake PowerCenterETL lineage EnterpriseData Catalog Business glossaryterms, CDEs, rules Data ownersaccountable, named A simplified view of the estate I catalogued at TCS
Currently
Data Owner
With
Mphasis, embedded at a global bank
Platforms
Informatica EDC, Collibra
Based in
Hyderabad, India

Experience

Three roles, one arc: from running warehouses to governing what they hold.

August 2026 – present

Data Owner

Mphasis, deployed to a global bank's consumer operations division, Hyderabad

Ownership of operational data domains: defining critical data elements, maintaining the business glossary, and keeping lineage and control evidence current for governance forums and regulatory review.

October 2022 – May 2026

Lead EDC Developer

Tata Consultancy Services, pan-European insurance client

Led Informatica Enterprise Data Catalog delivery on a GDPR-driven governance program spanning ten countries. Owned catalog administration, resource and connection configuration, remote-agent scanning across regions, profiling and data-domain discovery, and the REST integration that carried curated metadata into Collibra for enterprise stewardship.

Closed the engagement as L2 support and migration liaison for the client's OBIEE reporting estate.

12Mmetadata assets
700source systems
10countries
9database technologies
2018 – 2022

Data Warehouse Operations

Cognizant

Operational delivery on Teradata and Informatica PowerCenter: load monitoring, incident handling, and change support for enterprise warehouse pipelines. The years that taught me what breaks when nobody owns the data.

Approach

Three habits that have held up across every estate.

Lineage before dashboards

A report nobody can trace is an opinion with a chart. I start from where the data enters and work forward, so every number downstream has a path back.

Owners, not custodians

Governance fails quietly when everyone is responsible and no one is accountable. I push for a named owner on every critical element, with the authority to say no.

State the edge of the map

I bound what I know precisely and name what I don't. It has cost me nothing in interviews and saved me plenty in delivery.

Capabilities

What I can be handed, and what I'm still earning.

Catalog administration

Informatica EDC end to end: catalog, analyst, model repository, scanning and profiling services; resource design, permissions, and remote agents across regions.

Lineage architecture

Column-level lineage through ETL layers, and defensible manual lineage for legacy platforms that no scanner reads.

Governance frameworks

Critical data element identification, business glossary ownership, data-domain rules and curation workflows, GDPR and data-residency design across jurisdictions.

Platforms

Oracle, SQL Server, Teradata, PostgreSQL, SAP HANA, DB2 for i, Azure ADLS and Synapse. Collibra as power user and REST integrator. PowerCenter, IDQ, SQL.

Still building

Deep Collibra platform administration, Informatica CDGC, and cloud warehousing on Snowflake and AWS. I would rather state the edge of my map than let a skills list imply otherwise.

Contact

Open to conversations about catalog implementations, lineage, and the practical side of governing data at scale.