DATA ARCHITECT / TECHNICAL & DELIVERY LEADER

Architecture
for what
comes next.

Nearly a decade building enterprise data foundations, modernising platforms, and leading delivery across the systems and teams behind them.

Engineering depth.
Architecture ownership. Delivery at scale.

SELECTED EVIDENCE↓
1,000+

ETL jobs migrated
to AWS / Airflow

10+

Governed data marts
for enterprise analytics

~60

People across a
multi-project delivery portfolio

01 / SELECTED WORK

Systems built.
Decisions made.

Three connected chapters in enterprise data architecture. From the foundation to its next evolution.

01Enterprise platform architecture

A foundation that serves more than one business.

An enterprise data platform supporting multiple business domains through shared architecture.

Enterprise data platform / Enterprise client engagement through TCS

Read the case study ↗
02From legacy ETL to managed platforms

Modernisation is a sequence of decisions.

1,000+ legacy ETL jobs migrated to AWS / Airflow, with ongoing evolution toward Databricks.

Platform modernisation / Enterprise client engagement through TCS

Read the case study ↗
03Analytics & semantic architecture

A common language for business performance.

10+ governed data marts connecting commercial and healthcare analytics to consistent KPIs and Tableau reporting.

Commercial & healthcare analytics / Enterprise client engagement through TCS

Read the case study ↗
ALSO IN THE ARCHIVE / 2019Supply-chain delivery analytics.
02 / ARCHITECTURAL THINKING

Follow the data.
See the decisions.

Technology matters most in context. A simplified view of how my platform work connects business needs to governed consumption.

01 / INGESTION & ORCHESTRATION

Good engineering should
be reusable.

Metadata-driven pipelines make new-source onboarding more repeatable. Restartable processing patterns support reliability as workloads grow.

Source dataMetadata + pipeline patternWarehouse

AWS · Airflow · Python · PySpark
Applied in enterprise platform modernisation

02 / DATA MODELLING

The model is where
business meaning lives.

Facts, dimensions and master-data mappings connect operational records to consistent analytical relationships across business domains.

Operational recordsFacts + dimensionsBusiness model

Redshift · PostgreSQL · SQL · Kimball / Inmon
Applied across platform modernisation, analytics and MDM

03 / QUALITY, SECURITY & RELEASES

Trust is an
engineering responsibility.

Role-based cloud access, source-to-target reconciliation, controlled database promotion and code review make governance part of everyday delivery.

ChangeReview + reconcileControlled release

IAM · Flyway · JIRA · CI/CD
Repository administration and release governance

04 / ANALYTICS & SEMANTICS

One definition.
Many decisions.

Governed semantic data marts standardise the business logic behind KPI cards, commercial performance reporting and medical-field analytics.

Warehouse10+ semantic martsTableau

Semantic modelling · SQL · MDM · Tableau
Applied in an enterprise analytics layer

Conceptual system view, based on documented responsibilities. Not a production infrastructure diagram.

03 / LEADERSHIP & PROGRESSION

From building pipelines
to aligning the whole.

MULTI-PROJECT DELIVERY~60people

Across a delivery portfolio for one enterprise client.

Portfolio scale; not a claim of 60 direct reports.

Architecture only works when people can deliver it.

My responsibilities span shared platform architecture, competing project priorities, and the engineering standards that connect them.

Technical direction +

Translate stakeholder needs into implementable architecture; govern quality, pipeline reliability and data definitions across shared enterprise platforms.

Engineering standards +

Mentor junior engineers, conduct code reviews, and administer Flyway repositories—reviewing, approving and merging changes for controlled database promotion.

Delivery alignment +

Coordinate technical delivery across multiple projects for the same client, connecting shared architecture with project priorities and business requirements.

2016

Engineering foundations

Joined TCS in December, following a B.E. in Computer Science & Engineering at SJBIT, VTU.

2019–20

Technical progression

Digital Cadre designation in February 2019; promoted to IT Analyst in February 2020.

2022

Enterprise client engagement

Began an onsite enterprise client engagement through TCS, working directly with business stakeholders.

2023–now

Architecture & delivery

Promoted to Assistant Consultant in November 2023; ongoing platform architecture and portfolio leadership.

04 / THE PERSON

Before the architecture,
an education in thinking.

MATHEMATICS / EDUCATION30

A student of
Anand Kumar.

I studied under Anand Kumar, the educator known for Super 30, before building a career in engineering and enterprise data.

Archival photograph of a Super 30 event banner and a young man standing beside it.
Archival photograph from a Super 30 event.

For those unfamiliar with Super 30

A selective IIT-JEE preparation programme in Patna, known for a small cohort of 30 and admission through an entrance test. Its academic focus is preparation for entry to the Indian Institutes of Technology (IITs).

Its social mission provides free teaching, accommodation and meals to students from economically disadvantaged backgrounds.

Programme & selection ↗

B.E., Computer Science & Engineering
SJBIT · Visvesvaraya Technological University
2012–2016

Anand Kumar, the educator Parth studied under through Super 30.
Anand Kumar · Super 30

A different point of view.

Anand Kumar was one of my teachers through Super 30, an early chapter in my education.

05 / CONTINUING TO LEARN

Experience is the foundation.
Learning keeps it moving.

5 credentials · All five have verification links.

THE NEXT CHAPTERSINGAPORE / GLOBAL PERSPECTIVE

Let’s talk about
what comes next.

Data architecture. Platform modernisation.
Technical and delivery leadership.

Start a conversation ↗LinkedIn ↗
[email protected]