Smart Apartment Data: Engineering from Clarity.

Operating as a hands-on, CSPO-minded contributor, I partnered directly with stakeholders and engineering leads within an Agile framework. My goal was to translate ambiguous business requirements into tangible, actionable design artifacts.

Instead of waiting for Jira tickets to be handed down, I embedded myself into discovery, refinement, and sprint planning. By surfacing technical and behavioural risks early, I helped ensure our cross-functional team shared the exact same mental model from concept to production.

• Converted weekly stakeholder synthesis sessions into actionable daily UI deliverables.
• Embedded persona-led prioritization directly into sprint planning.
• Participated in user interviews with investors and property managers.

Inheriting a platform burdened by heavy design debt, I operated as the primary Individual Contributor to fundamentally overhaul the UX. I architected a robust, tokenized design system grounded in Google’s Material Design principles—codifying color, density, motion, and elevation as systemic tokens rather than isolated, per-screen decisions.

By systematically paying down this design debt, I ensured structural consistency across every chart, grid, drawer, and report.  Engineering inherited a predictable surface area; users inherited a single language for navigating the whole product.

• Tokenized color, type, density, and motion across desktop and mobile.
• Material-aligned components purpose-built for high-density real estate data.
• Documented usage patterns for charts, grids, and embedded Tableau surfaces.

My Computer Engineering background allowed me to close the most expensive gap in modern product teams: the chasm between design intent and shipped code. Because we were building for such diverse mental models, the platform relied heavily on intricate search criteria for locators, heavy data grids for analysts, and dynamic chart results for suppliers. Handing off static files for interfaces this complex simply doesn't work.

Instead, I owned the UX acceptance criteria directly inside the build process. I authored test scenarios in Azure DevOps specifically to stress-test how these heavy data queries and map integrations rendered in production. By validating the output through BrowserStack and pair-debugging with developers, I ensured that even the most complex search interactions shipped flawlessly.

• Authored UX acceptance criteria in Azure DevOps to validate complex search and filtering logic across all four user portals.
• Performed cross-browser validation via BrowserStack, stress-testing interactive maps and dynamic charts.
• Pair-debugged API data rendering, chart performance, and map virtualization directly alongside engineering.