Manager, Forward Deployed Engineering (Producers) at Questrade Financial Group Toronto, Ontario
I lead a client-facing data engineering squad inside a financial group. We take a business priority, ship the data product that answers it, then hand the pattern back to the platform team so the next team does not need us.
The work spans a regulated digital banking launch, a lakehouse migration across two clouds, and the governance layer that has to hold up to an auditor. Most of what I do now is deciding which problems are worth a platform and which are worth a pattern.
| Repository | The question it answers |
|---|---|
| platform-investment-case | Build the lakehouse, extend the warehouse, or buy the vendor product? A DCF, a decision tree and a Monte Carlo find that the decision turns on adoption, not architecture. |
| pipeline-sla-capacity | How much capacity holds a 15-minute freshness SLA? Queueing theory says none does, because the service times alone breach it. |
| medallion-pipeline | How do raw events become governed, business-ready tables without a hand-built pipeline per source, and how do you know when they stop being either? |
| ai-data-analyst | Can a business user get a trustworthy answer from the warehouse in plain language, with the SQL and permissions shown? |
| noosphere-public | What does an AI work partner need to know about your business before it is useful? |
The first two answer a money question and an operations question. The rest are the platform underneath them. Each runs on synthetic data and carries no employer detail.
Dual Executive MBA, Cornell Johnson and Queen's Smith, conferred May 2026. Databricks, PMI, Scrum Alliance, and Google Cloud credentials.
Platform: Databricks on Azure and GCP, Delta Lake, Unity Catalog, BigQuery, Pub/Sub, Kafka, Power BI, Python, SQL.
LinkedIn · parozmehta@gmail.com · Toronto, Ontario
