I own data for a consumer banking line of business: deciding which sources can be trusted, fixing the ones that can't, and putting a name to every answer. Eight years across warehouses, catalogs, and now a bank's operations.
Four roles, one arc: from running warehouses to governing what they hold.
Data Owner for a consumer banking line of business, accountable for an assigned subset of its data domains and for the accuracy, consistency and completeness of what they hold. The role sits between business stakeholders, data engineering, architecture and governance, and underneath it all is dataset-level judgment: which source answers which question, by grain, refresh and certification status.
Led Informatica Enterprise Data Catalog delivery across ten countries: catalog administration, resource and connection design, remote-agent scanning across regions, profiling, and data-domain discovery, with curated metadata flowing into Collibra for enterprise stewardship.
Led a 12–15 member operations team covering system health, batch execution, database administration, and deployments for a Teradata warehouse fed by Informatica PowerCenter.
The first project, and still the foundation. Application and production support for banking systems on Unix and Oracle: batch jobs, server maintenance, uptime monitoring, incident troubleshooting, and user provisioning across Ab Initio and PowerCenter.
Three habits that have held up across every estate.
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.
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.
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.
What I can be handed, end to end.
Informatica EDC end to end: catalog, analyst, model repository, scanning and profiling services; resource design, permissions, and remote agents across regions.
Column-level lineage through ETL layers, and defensible manual lineage for legacy platforms that no scanner reads.
Critical data element identification, business glossary ownership, data-domain rules and curation workflows, GDPR and data-residency design across jurisdictions.
Oracle, SQL Server, Teradata, PostgreSQL, SAP HANA, DB2 for i, Azure ADLS and Synapse. Collibra as power user and REST integrator. PowerCenter, IDQ, SQL.
The formal side, kept short.
Plus forty-odd shorter courses across data, cloud, and business analysis, listed on LinkedIn.
Multiple awards across TCS and Cognizant, including the Special Initiative Award, a Certificate of Recognition for outstanding contribution to project deliverables, and the Silver Award.
B.Tech in Electrical and Electronics Engineering
BV Raju Institute of Technology, 2012–2016
English, Telugu, Hindi
Always happy to talk catalogs, lineage, and the practical side of owning data at scale.