Product
Octo — Cloud Cost Management Platform
Octo's product was strong. The delivery system around it wasn't. PR reviews were inconsistent, bug reporting required switching tools, and weekly releases meant every friction point had a real cost. I owned frontend delivery — and the surrounding systems that kept the team moving.
Summary
- BuiltBuilt and maintained cloud cost dashboards, recommendation views, budget management, and reporting systems using Vue, Vuetify, and ECharts.
- ProblemOcto's product was strong, but delivery friction was quietly compounding.
- ImpactBug reporting automation adopted company-wide — eliminated manual ticket triage and was recognized directly by the CEO.
Problem
Octo's product was strong, but delivery friction was quietly compounding.
Octo's product was strong, but delivery friction was quietly compounding. PR reviews were inconsistent, onboarding had unnecessary steps, and bug reporting required switching between multiple tools.
Weekly releases meant these problems had real cost — not from lack of effort, but because the system around the work was creating drag.
Fixing the product meant fixing how the team moved.
What I Built
6 key contributions that defined the build
- Built and maintained cloud cost dashboards, recommendation views, budget management, and reporting systems using Vue, Vuetify, and ECharts.
- Introduced PR templates with structured sections (problem, scope, screenshots, release notes) — standardized reviews and made weekly deployments more predictable.
- Built a Slack-to-ClickUp bug reporting automation in Make, then rebuilt it in n8n for stronger parsing — became the company-wide standard, recognized by leadership and noticed by the CEO.
- Simplified the user onboarding flow, removing friction points that slowed early product adoption.
- Integrated Mixpanel analytics and i18n localization across core product modules.
- Mentored junior developers and backend engineers on frontend architecture, codebase structure, and frontend-to-API workflows.
Key Decisions
Tradeoffs and approaches that shaped the final outcome
Challenge
Operational improvements — PR templates, workflow standards, automation — rarely feel urgent next to feature work, even when they protect long-term delivery speed.
Approach
Treated system improvements as delivery investments, not optional cleanup — PR templates and Git workflow standards reduced review friction and protected future velocity.
Challenge
Financial data dashboards need to feel trustworthy, not just functional. Users make real spending decisions from these views.
Approach
Focused dashboard and report design on data clarity and consistent formatting, not visual complexity.
Challenge
A new internal reporting tool only creates value if people adopt it. Building it inside the tool teams already used was the only way to make that work.
Approach
Built the bug workflow inside Slack itself, reducing adoption friction to near zero — the tool was already open.
Impact
Bug reporting automation adopted company-wide — eliminated manual ticket triage and was recognized directly by the CEO.
- Bug reporting automation adopted company-wide — eliminated manual ticket triage and was recognized directly by the CEO.
- Faster, more consistent PR reviews and weekly releases across the product team.
- Improved frontend onboarding time for new developers and reduced dependency bottlenecks across the team.