Team project / Frontend contribution

E-Sejm

An application using the Polish Parliament public API. My contribution covered parts of the frontend layer in React, Redux and Tailwind.

Selected views and interface elements

What this demonstrates

Fast onboarding into a new stack and practical team collaboration without claiming ownership of the whole solution.

E-Sejm: enter a new stack and deliver the integration

E-Sejm was a six-person team project where I owned selected frontend views and their connection to a Java backend. The interesting part was not learning React alone, but building a bridge between an existing API and my interface layer.

FIELD NOTE

A CHANGE OF PERSPECTIVE

From Razor Pages to an SPA

I normally work in the .NET ecosystem, so I had to move quickly from server-side rendering to React, Redux and utility-first CSS. Strong fundamentals let me adopt the new way of thinking without slowing the team down.

INTEGRATION

The frontend as a contract, not decoration

I designed Redux Thunk services, DTO mapping and loading and error states. I connected authentication, MP data, voting results, the forum and a react-admin panel to the team's REST endpoints.

TEAMWORK

Four sprints, one working whole

Across four sprints I moved from UI foundations and authentication through data integration to responsiveness and refactoring. JSON contracts, error codes and changing endpoints required the most coordination.

TAKEAWAY

Learning speed matters when it ends in delivery

The project taught me to agree API contracts, surface ambiguity early and describe my scope honestly. That experience now helps with consulting, integrations and taking over existing systems.

NEXT ITERATION

Need a system with similar capabilities?

Tell me what you are trying to improve and we can map the next practical step.

I WANT A FREE DEMO