ExperienceExperience

WorkJam is a frontline workforce platform used by around 3 million people: scheduling, tasks, communication, learning, compliance and integrations with the tools a company already runs. The frontend is a large monorepo - several module apps, a unified app, shared packages and many teams. Legacy Angular apps live alongside the new React app, and new React features run inside the Angular ones, so the product moves forward without a rewrite.

The same apps open in a browser, inside Microsoft Teams and inside the iOS and Android apps, while the chat is a separate product on its own server.

I worked there as a frontend developer and one of the maintainers of the shared design system. Below are the parts I found most interesting; alongside them I built many other features across the platform's sections.

The schedule. I built the schedule from scratch on FullCalendar - the screen employees, managers and admins open every day:

• daily, weekly and by-position views
• adding, editing, duplicating and deleting shifts, shift swaps and open shifts
• filters and pagination
• behaviour that changes with each role and each company's feature flags

A page can hold hundreds of shifts, so I kept it fast by paginating employees, memoising shift cells and caching GraphQL and REST calls.

AI writing assistant. The platform's rich text editor (Lexical) is shared by documents, posts and comments, and I owned the AI assistant inside it. A teammate built the Gemini backend with our architect; I built everything on the frontend - the editor integration, reading the response stream as it arrives, keeping the formatting intact, and the whole UI. People can pick a predefined action or write their own prompt to rewrite any part of the content, and the result lands in the editor already formatted.

Chat inside the mobile apps. The chat is a separate project, deployed on its own server. In the iOS and Android apps it runs in a WebView, which keeps the native apps light, and a bridge lets the two sides talk: people are already signed in when they open it, and the chat can reach native features like the camera.

My part was the connection between the two. I kept socket connections alive across reconnects, kept authentication in sync between the main app and the chat, and handled the Android events the chat needs to upload and edit media.

Microsoft Teams. WorkJam also runs inside Microsoft Teams, where the module apps and the unified app have to behave like one product that knows who the user is and which company they belong to. I worked on that integration as features moved into it.

Design system. I built and maintained atomic components and their Storybook documentation. They're used across every app on the platform and follow accessibility standards, so a fix in one place reaches every team.

Angular and React side by side. I shipped features into both stacks, and moved existing Angular features into the React infrastructure.

Tests and analytics. I covered the features I built with unit tests (Jest, Testing Library), and wired Google Analytics events into them, so the team could see how people actually used each feature.

Platform work

• Co-led the migration of feature flags - the switches that decide what each company sees - from three systems to one. Old and new ran side by side and rolled out step by step, with zero downtime
• Set up translations in the new React app at an early stage
• Worked on an AI workflow that turns new translation keys into 50+ languages and opens the pull request

I also mentored developers on the team.

Esko builds pre-production software for the packaging and printing industry. I worked on a portal for managing users of their products, built on a microservice architecture.

• Billing, end to end. I introduced FastSpring billing into the portal: subscription flows, plan changes and payments, with role-based access deciding who can do what. I documented the integration fully.
• Fitting it into microservices. Billing and access touched several services at once, so the frontend had to stay in step with each of them as subscriptions changed.
• TypeScript and tests. I brought TypeScript and unit testing (Jest, React Testing Library) into the codebase.
• Features, architecture and docs. I built new product features, improved the architecture as they landed, and wrote the technical documentation.

Short projects for real-estate developers: one- to three-page sites where design and motion sell the property. I built about eight to ten of them, some from scratch and some taken over and extended, and owned each one from architecture through launch and post-launch support.

• Motion. GSAP and fullPage.js scenes, and SVG animations that react to what the visitor does.
• Performance. Heavy visuals still had to load fast. I tuned every site against PageSpeed Insights by optimising images, animations and video, and built static pages with Gatsby.
• Integrations. Third-party platforms and services, Firebase for securely stored data, Mapbox maps, and custom HTML email templates.
• Existing sites. Besides new builds, I extended and maintained sites the clients already had.

I also mentored developers who joined these projects.

Benamix - Frontend Developer

• A crypto finance platform: payment flows, an integrated bounty program, the algorithms behind them, live data over WebSockets, and charts
• A corporate site with its own design and animations, where interactivity and speed came first
• Smaller shops and landing pages with complex layouts

Sol-Ra - Frontend Developer (React, remote)

• An internal CRM for the company's employees, with data tables and analytics dashboards

M-Pluse - Junior Frontend Developer

• Client projects from e-commerce to interactive, design-focused sites, built with Angular