Career · as a developer at D3 Company
ZAG — Corporate reimbursement
ZAG takes corporate reimbursement out of the spreadsheet: the employee logs the expense, the manager approves it and the system flags what doesn't add up. I worked on the webapp, building screens and wiring each one to the product's API.
Problem.
Expense reimbursement in a company usually means lost receipts, rebuilt spreadsheets and approvals by email. ZAG handles it in a single product, and the webapp had to follow the flow from logging an expense to its approval.
Solution.
Development of specific webapp screens in React and their integrations with the backend API, inside a team and a product that were already under way.
Result.
Screens delivered in the product's webapp. It was one of my first professional projects, and where I learned to debug what the screen doesn't show.
The hard part.
Every project has a point where the obvious solution doesn't cut it. Here, it was these.
A character nobody could see
New reimbursements were coming in with an invisible character inside the value string. On screen the number looked identical to the correct one, which is why the problem took time to find. This was before AI tools, so the investigation was done by hand: comparing what the screen showed with what was actually being sent. Since then, I treat any value coming from a text field as suspect until it's normalized.
What I did.
- Development of specific webapp screens
- Integration of the screens with the backend API
- Investigating and fixing interface bugs, including values carrying an invisible character
Stack.
A stage of my career
This was part of my career, not a client project.
Work done as part of a team, before I took on clients on my own. It is here to show what I learned and how I work. Today I work directly with small and mid-sized businesses, with published prices.