/02JLL TechnologiesSoftware Engineer · BI Development Analyst3 Years
From Dashboardsto Decisions
From writing the pipelines to owning the insight — closing the gap between data and the decisions it should drive.
Context
Real estate teams had operational data everywhere and very little of it arrived in a form that changed what they did next.
Problem
Reporting answered questions nobody was asking. The gap wasn't data availability — it was the distance between a number on a dashboard and a decision someone had to make in a meeting.
My role
Started as an engineer shipping features, moved into BI to close the gap between operational data and the decisions real estate teams needed to make, then took on product-oriented ownership across two AI-driven applications — roadmap thinking, prioritization, stakeholder alignment, and product decisions.
System / architecture
- 01Raw Data
- 02SQL
- 03Dashboard
- 04Insight
- 05Product Decision
Key decisions
Prioritized dashboard rebuilds around the specific questions stakeholders actually asked in meetings, not around what was easiest to build.
Made the call on what not to build into the AI applications' first release to hit a realistic timeline.
Challenges
Moving across roles meant the definition of my job kept changing while the same stakeholders expected continuity. Scope pressure on the AI applications was constant, and saying no had to come with a defensible reason.
Outcome
Built and shipped 35+ customer-facing Tableau and SQL dashboards.
Mentored two interns across the transition between roles.
00+
Dashboards shipped
0
Years
0
AI applications
What I learned
Having shipped the code and written the queries changes how I scope work. I can tell when an estimate is really an unknown, and I can argue for cutting scope in the engineer's language rather than the roadmap's.
Next project