Expense Reporting Software
Dec 2015 – Mar 2018
Front-end engineering on enterprise expense reporting — employee submit flows in a large-scale Backbone.js fintech app.
Overview
Chrome River (now Emburse Enterprise) builds expense and invoice management software used by large, global organizations. For two-plus years I worked on the expense reporting side — modular Backbone.js views for employee submit flows, wired to REST endpoints, shipped on sprint cadence with pixel-accurate Figma specs.
My Role
- Title
- Software Engineer, Front End
- Context
- Agile team; close collaboration with PMs and back-end engineers.
- Scope
- Expense reporting surfaces — employee submit flows, REST integration, bug fixes, and pixel-accurate Figma implementation.
The Problem
A large Backbone.js expense reporting app needed new employee submit views wired to REST data and shipped every sprint — in fintech, design specs had to match production UI.
What I Built
Employee expense submit views
- Problem
- Expense reporting needed new employee-facing views wired to live REST data.
- Fix
- Modular Backbone.js views using AJAX against REST endpoints.
- Result
- New submit surfaces shipped inside the existing expense reporting app.
Pixel-accurate specs
- Problem
- Design specs weren't translating into a consistent UI.
- Fix
- Pixel-accurate implementation of Figma and design specs.
- Result
- A consistent experience across the expense views I owned.
Agile delivery
- Problem
- Bugs and stories stacked up in an agile fintech workflow.
- Fix
- Resolved bugs and delivered stories in sprint cadence.
- Result
- Work shipped on the team's schedule — no single hero bug story; honest routine enterprise FE.
Tech Stack
Outcome / Impact
Two-plus years of reliable sprint delivery on expense reporting surfaces — pixel-accurate Figma implementation and modular Backbone views. No single project metric claimed.