Career · 2021–present

Quick Facts

• Span: Aug 2021 → present (~5 years in OneStream)
• Roles held: 4 — OneStream Analyst, EPM Developer, Contract Consultant, Manager
• Locations worked from: Noida → Chennai → Markham (remote) → Lucknow
• Engagement types: Retail / FMCG implementation, in-house EPM product work, deep single-client contract, multi-client management
• Sectors touched: Retail, consumer hardware, loyalty / membership, accounting marketplace, mining, oilfield services, records / govtech, industrial machinery, AdTech / data-connectivity, clinical research

---

Overview

Four roles, one platform. Each role was a different vantage on OneStream — analyst inside a large consulting firm, developer inside a product company, contractor on a single deep engagement, manager running several at once — and the patterns I rely on now were built across all four. This page is a short walk through that path; the case-study pins on the home grid cover the project work itself.

Role 1 — OneStream Analyst, global consulting firm (Aug 2021 → Aug 2022, Noida)

First role out of engineering school. Joined the OneStream practice at a global consulting firm and got dropped onto two parallel engagements — a retail Fortune 1 GL Planning module and an FMCG price-and-volume simulator. The retail engagement was straight implementation: metadata, dashboards, business rules, custom copy-and-clear utilities, prebuilt-model enhancements, plus a workforce-to-planning-cube bridge. Shipped without an escalation, which became the bar I held later work to. The FMCG initiative was the one that taught me what the platform could do beyond its out-of-the-box shape — a rule-based price-elasticity model living entirely inside OneStream, no Python sidecar, no external ML. Conducted Finance, Spreadsheet, Extender, and Dashboard technical trainings for the support team and new joiners on the side.

Role 2 — EPM Developer, global consumer hardware brand (Aug 2022 → Mar 2023, Chennai)

Moved product-side. Joined the in-house EPM team at a global consumer hardware brand. The role flipped my context — instead of building solutions for a single client engagement, I was building utilities the same finance team would use for years. The work was tighter on rigor and looser on novelty: a completely generic clear utility that worked across any dimensional intersection, a cube-view connection layer inside the Excel add-in giving finance users a familiar interface, macro-driven self-serve spreadsheets, and a handful of targeted code modifications informed by calculation-log profiling that lifted application responsiveness.

Role 3 — OneStream Consultant (contract), Canadian EPM consultancy (Dec 2022 → Feb 2023, Markham)

A short contract with a Canadian-based EPM consulting firm — overlapped with the tail of the hardware role. Single deep engagement at a global loyalty / membership platform: dynamic reports + Template Cube Views adapting to changing dimensional structures, customised Cube View extenders + Dashboard XFBR rules, and a generic parameter solution using sophisticated row-name suffixes to control formatting at render time. Also led a data-reconciliation exercise between the in-flight and legacy systems to keep the stakeholder-facing numbers honest through cutover.

Role 4 — Manager, EPM consulting practice (Apr 2023 → present, India)

Joined as Manager at an EPM consulting practice and took on the India delivery lead role. Three years in: nine more client engagements shipped across mining, oilfield services, US convenience retail, DTC outdoor lifestyle, clinical research, accounting marketplace, records management / govtech, industrial machinery / logistics, and AdTech / data-connectivity SaaS — most of which have their own case study on this page. In parallel: scaled the India team from one to seven, established hiring, code-review, and documentation standards, and led the practice's AI adoption — rolling Anthropic Claude plus local-database-driven internal tooling into the daily workflow. Continued publishing on the OneStream community blog through this period; the Event Handlers post landed at #3 most-viewed within five months.

What stitches the four together

Same platform, four different vantage points on it.

• The analyst role taught me what a clean engagement looks like end-to-end — scope, deliverables, no-escalation discipline.
• The developer role taught me what good tooling for an in-house team looks like — the difference between a one-shot rule and a utility someone else can use without your help six months later.
• The contract role taught me how to ship deep work fast on a single problem with no organisational overhead — and how to defend the numbers through a cutover with no margin for surprises.
• The manager role taught me that the leverage from any of the above multiplies when you also build the team that will keep doing them after you.

Learnings

What worked. Taking the next role for what it taught me, not just what it paid. Each switch was a different shape — agency analyst → in-house developer → independent contractor → manager — and each shape sharpened a different muscle. The implementation discipline came from the analyst role. The tooling instinct came from the developer role. The "ship under cutover pressure" came from the contract. The team-building came from the manager role.

What I'd do differently. Earlier writing. The blog posts and the internal training curriculum that came out of the manager role were the highest-leverage work of the five years — they compounded across cohorts and across firms. Most of what's in the Event Handlers post I could have written eighteen months earlier. The bar I had set for "post-worthy" was unhelpfully high.

Skill developed. The transferable thing isn't OneStream specifically — it's the four-frame mental model the roles built: implement cleanly, build for the next person, ship under pressure, multiply through the team. Every problem on this site falls into one of those frames; most fall into more than one.