Making sure the IT department works like a charm ;)My main areas of responsibility:- optimizing and building processes of software development- taking part in company strategy creating- managing cooperation with external contractors- preparing the vision of the IT department- managing the budget

I'm responsible for delivering the overall new version of our product. My focus is mainly on the technical side, nonetheless cooperating with the product team is crucial as well as managing contractors or communication with other company departments.Besides the management role, I could still be found behind the keyboard developing new features, working on architecture for various solutions etc.

I'm the FE tech leader and architect for the CRM system. Among my responsibilities is taking care of the technical development of the new version of the system. With the usage of the Clean Architecture approach, I'm able to provide robust solutions so frontend app development is not blocked in any way by e.g. BE development. Also, we're prepared for the unexpected by having code divided into bounded contexts with proper abstraction layers. The architecture is prepared for all kinds of communication, async one included.The tech stack is again based on TypeScript and React for the UI layer. However, the code itself is more about utilizing design patterns rather than a specific framework.Aside from tech stuff, I'm on work organization, preparing plans for the dev team (long term, as well as on daily basis), cooperating with the design team, etc.

I was a tech lead and frontend architect in various projects for various clients.CSR platform and the back-office systemI was the lead for a team of around 20 FE devs. My responsibilities were designing the approach toward the development of an enterprise-scale CSR platform and conducting subteams of developers. I was co-creating workflow processes and was the point of contact with the client.Technical details of the project frontend were as follows:- ES6+ as a general language- React for views- Redux with Redux Observables for business logic and data store- Jest with Enzyme as testing toolsThe architecture approach was domain oriented so the whole app would be easy in maintain and scale. In general, app was divided into pieces, each corresponding with a separate feature.For the same client, I was in charge of creating architectural proposals and workflow for revamping the client's entire back-office system. For this, I've come up with the idea of using a Clean Architecture approach with distributed microfrontends ecosystem. The tech stack for the solution was based on TypeScript and React. As each part of the system was fully independent of the other, details like whether to use Redux or not, were totally up to the team responsible for a given area.Multimedia files repositoryI lead a team responsible for implementing the frontend side of the system for managing media files for one of the biggest Polish internet media groups. This system was a part of the bigger CMS for all of the group sites.The architecture was again based on Clean Architecture so it was domain-centric. The tech stack was about TypeScript, React, and Redux but the core of the app was framework agnostic. This approach helped the team to work on the views in separation from the business logic layers. Also, each domain was separated from each other for more scalability and maintainability.

I was responsible for developing hybrid mobile application for 3 main platforms back then - Android, iOS and Windows Phone.Application was built using JS (transpiled from Coffee Script) and Cordova. As 90% of the app (all the views and transport layer) was implemented in JS (same code for all the platforms), some low-level stuff was made using native technologies (Java, Objective C, C#). These things were mostly related to security (like hashing communication, detection of rooted devices and blocking the app from running on them).I also built my custom Node.js script for bundling, building and preparing the app for deployment (both for testing and production, for all stores).

- designing apps- server side developing (node.js)- making tech decisions- hybrid mobile apps developing- creating procedures for application development and deployment- docs writingProjects:- Wyjnik Kibica (Android)

Developing mobile apps for iOS and Android using PhoneGap.Writing some middlewares and backend in node.js.Some apps:- Duzy Kadr for iPad- HappyDay for iPhone- Happyday for Android- Zczuba for Android- Plotek for iPhone- Plotek for Android- Sport.pl Live for Android - node.js backend.

- creating pages and page templates in XHTML and CSS- developing JS solutions for websites- creating Facebook appsWork for (examples):- Play- Coca-Cola- Heineken- Volvo

Developing frontends in XHTML, CSS and JS.Some Velocity templates too...

Freelance in its form :)Talking with clients, designing and developing CMS systems, websites etc.

Frontend and backend programmer.