CASE STUDY · Thynk Web · FRONTEND + PRODUCT ENGINEERING
HRM Platform — Users, leave and payroll. Connected.
I built three HRM modules with notifications, plus REST APIs for employee data workflows.
- ROLE
- Associate Software Engineer
- EMPLOYMENT PERIOD
- May 2023–Jan 2025
- COMPANY
- Thynk Web
ReactTypeScriptRedux ToolkitFlowbiteChart.jsC#/.NET
PEOPLE OPERATIONS
ORIGINAL ILLUSTRATION HRM · CONCEPTUAL VIEWOriginal illustration · not a product screenshot01 — CONTEXT
The product context.
My HRM work covered users, leave and payroll, together with the REST APIs needed for employee-data workflows.
02 — MY ROLE
What I owned.
I built across the React and TypeScript client and C#/.NET REST APIs. I also reviewed pull requests.
03 — WHAT I BUILT
From interface to implementation.
- 01
Three connected modules.
I built users, leave and payroll modules with notifications, using React, TypeScript, Redux Toolkit and Flowbite, with Chart.js in the frontend stack.
- 02
Employee-data workflows.
I built REST APIs for import/export, batch processing and employee synchronization.
- 03
Code review as part of delivery.
I reviewed pull requests alongside my implementation work on the modules and APIs.
04 — STACK
The tools behind the work.
ReactTypeScriptRedux ToolkitFlowbiteChart.jsC#/.NET
05 — OUTCOMES
What I delivered.
3Modules: users, leave, payroll
RESTImport/export, batch processing, employee sync
OPEN TO SOFTWARE ENGINEER ROLES
Let’s build something
that goes live.
Suman Kumar KhanHRM · THYNK WEB