Internal tooling at Cegeka

Context

When I started at Cegeka in September 2025, my first work was on internal tools, before I moved to client projects. These tools support teams inside Cegeka in their day-to-day work.

What I worked on

I worked on two internal tools:

• Project overview: gives managers one view of all ongoing projects, so they can follow progress and plan who works where. Built with Blazor, a Dotnet backend and SQL Server.
• Jira–payroll integration: connects Jira to the internal payroll system, so logged hours and project allocations reach payroll without manual timesheet work. Built with Angular, a Dotnet backend and SQL Server.

Both tools run on Azure.

On the Jira–payroll integration I:

• made the queries against Jira more efficient and replaced a deprecated Jira API endpoint
• introduced the strategy pattern on the payroll side, so the tool can switch between internal payroll systems without changes to the rest of the code
• upgraded the Angular front end from version 17 to 21

I worked in a small team of developers and analysts, with a mentor who guided me through my first months and helped me find my way in Cegeka’s internal processes and tools.

Outcome

Managers use the project overview to keep track of ongoing projects and to plan people and resources. The Jira–payroll integration cuts down the manual work around timesheets and project allocations.

What I learned

How to find my way in an existing codebase, and how to integrate a third-party API such as Jira’s into existing systems.