SaaS HR software for time off, performance cycles, communications, employee profiles, workflows and documents. I was the lead frontend engineer for a long time, and later moved into backend work as well.
One HRIS covering time off, performance, communications, profiles, workflows and documents. Every page loaded its data its own way.
Customers used it daily. Nothing could pause while new features kept shipping.
One shared way to load data, rolled out feature by feature, alongside visible work like dark mode and contract signing.
The platform is SaaS HR software that companies run their people operations on: time off, performance cycles, internal communications, employee profiles, workflows and documents. HR teams use it every day.
I was the lead frontend engineer on it for a long time, and later moved into backend work as well. As the product grew into all of those areas, each new screen took longer to build than it should have, because every page loaded its data in its own way.
Customers relied on it daily, so there was never a good moment to stop and rebuild. A single design change could reach almost every file in the app.
Every improvement had to happen while new features kept shipping.
As lead frontend engineer I worked across the whole product alongside designers, product managers and other engineers, and later picked up backend work too. Some of my work is easy to see: new features and a full dark mode. Much of it isn’t. That includes making the app start faster, keeping live updates accurate, and giving the team one shared way to load data, so new screens take less effort.
Brought dark mode to the whole product and moved every screen onto one shared set of colours and styles.
Built online contract signing, so job candidates can sign their employment contract from a link.
Worked on performance reviews and a visual workflow builder that HR teams use to automate their processes.
Made the app load faster by downloading only what each person needs: their own language, and the document viewer only when they open a document.
Fixed live updates so people always see their own time off correctly, even while colleagues make changes.
Kept the product up to date through major upgrades of its design framework without pausing feature work.
Made new screens simpler to build by moving the whole team to one way of loading data, one feature at a time.