Imran Rehman

Full Stack Data Scientist
System Design Engineer
Platform Engineer
Solutions Architect & Technical Lead
@TDInsurance
Scroll

Solution engineering

I'm the lead technical solution and design engineer behind the organization's all-in-one analytics, insights, and coaching platform supporting its largest line of business. Business-critical to more than 2,000 colleagues, the platform powers decision-making across every level of the organization—from customer-facing advisors and team leaders to reporting, analytics, and business strategy teams. I lead the platform end to end, designing scalable solutions and delivering features across the entire technology stack.

I serve as the bridge between business leaders and engineering. When leadership identifies an opportunity or challenge, I translate that vision into scalable software solutions, designing the systems, data models, and user experiences needed to bring it to life. My job is to ensure technology isn't just built correctly—it's built to solve the right problems.

Continuous Integration & Impact

  • $15M+

    Cost savings at release

  • 50%

    Adoption lift

  • 60% → 99.9%

    Uptime

  • 2,000+

    Colleagues daily

  • Weekly → daily

    Data cadence

  1. 01

    The call I made

    Drove the redesign

    I called for abandoning a failing legacy tool and rebuilding it the right way—full ownership of architecture, design, build, and migration. That decision set the course for everything that followed.

    • Initiated the rebuild when the old tool could no longer serve the floor
    • Owned the platform end to end from day one
    • Established a clean, modern foundation to build on

  2. 02

    What I led

    Scale, centralize, unlock

    I led the work that turned that foundation into a business-critical platform—reliability that made mass adoption possible, consolidation of fragmented tooling in-house, and a base that finally let once-impossible ideas ship.

    • Engineered for performance and reliability from day one
    • Retired third-party tools and manual reporting into one owned ecosystem
    • Opened capabilities and change velocity the old tool could never support

  3. 03

    Impact today

    The decision still compounds

    That initiative is why the role exists today: translating business goals into shipped tooling across the org. New teams, faster change, and ongoing impact that simply were not possible before.

    • Solution engineering from design through implementation
    • New collaboration chains across partner teams
    • A canvas for the business to realize ideas at a pace that compounds

The Stacks

Five areas I work across to translate business vision into systems that hold up—metrics, databases, pipelines, runtime, and product UI. High-level by design; the craft shows in the decisions.

  1. 01

    KPI Design & Data Modeling

    I turn multi-source lake data into production metrics the business can trust—definitions, models, and validation so advisors and leadership read the same signal.

  2. 02

    Database Engineering

    I design databases for organizational scale—schemas and access patterns that hold massive volumes while staying fast under concurrent product and reporting load.

  3. 03

    Pipeline Engineering & Data Curation

    I build Databricks pipelines that automate movement, validate quality, and leave curated tables ready for reporting, scoring, and product features.

  4. 04

    APIs & Runtime Systems

    I build the service layer the platform runs on—APIs and runtime controls that stay responsive when thousands of colleagues hit mixed workloads at once.

  5. 05

    Application UI

    I design and ship the interfaces people use—coaching, insights, and reporting surfaces where clarity and trust decide adoption.

  6. For a deeper technical look at examples across these layers, read about my favourite integration initiatives in the Knowledge Net.

    Browse Knowledge Net

Knowledge Net

A growing library of write-ups I've made along the way—technical deep-dives, strategic notes, and reflections on how the work actually gets done. A wide variety of documents that explain decisions, patterns, and lessons from building and scaling the platform.