A working analyst who writes down how the work is done

How I got here

I started a computer science degree in 2012 and took my first IT job in 2013, as a software tester. In 2014 I joined Euro-net, the company behind RTV EURO AGD, expecting to become a programmer, and found that the analysis was the part of the work I wanted to keep. Mid-level and then senior roles followed in 2015. In 2016 I took my first job in English and it did not work out: the language barrier was real, and so was a culture I did not understand yet. That year is a large part of why I write the way I do on this site.

Today I work remotely on international projects, from a house in the Polish countryside, and I choose the projects I take. I sit in the meetings where scope changes on a Thursday afternoon and the document is due on Friday. My analyses feed decisions that move real money, which is a polite way of saying that when my requirements are vague, somebody builds the wrong thing and someone else pays for it.

That is where the scorecard on this site comes from. It is not a theory of good documentation. It is the list of things I get asked about in review, written down so you can be asked them before it counts.

What I have built

Analify.pl is a business analysis training platform in Polish, with paying members. I built it myself: courses, exercises, a SQL sandbox, peer review, live sessions with guest practitioners that stay recorded, and a job board that pulls listings from four Polish boards every day. I also teach business analysis and SQL, to individuals and to teams inside companies. It is not a side project and it is not a landing page - it works, it has customers, and it gives me something most people writing about this job do not have: a daily, measurable view of what employers actually ask for.

ExamDeck.pro is the sister product, in English: practice exams for 36 certifications, from IIBA and IREB to Scrum, PMI, PRINCE2 and TOGAF, on a bank of more than six thousand questions at the time of writing (September 2026). It exists because people sit those exams anyway. It is not an argument that a certificate proves you can do the work. This site is the argument for the work sample.

Any numbers I publish here will come from the platform's pipeline. It reads four Polish job boards, so the numbers are Polish, and I will label them Polish rather than dressing them up as European or global.

Being based in Poland is the point

I am not an outsider looking at this market - I work as an analyst from Central Europe, inside the delivery model rather than watching it. How much of the analysis work delivered to Western companies comes from this region is a number I do not have, so I am not going to quote one. If you are reading this from London, Toronto or Austin, an analyst working the way I do may well be on your programme right now.

It also means I write in a second language, deliberately plainly. You will not find decorative vocabulary here. You will find the shortest sentence that survives review.

On stage, and on the other side of the table

On 11 September 2026 I hosted Wielki Feedback vol. 2 in Warsaw, a one-day conference where analysts, developers and architects worked the same case: 130 people, about half of them online. I ran the day and moderated the analysts' panel. I had also sent in my own analysis of that case, anonymously. It placed third, and it is public, in Polish, at analify.pl/odkryj/analiza-strefa. Having your own work judged at an event you are about to chair is a good way to stay honest about it.

I also publish on YouTube: @analify_pl in Polish and @analify in English, which is the newer of the two.

How I work in public

Everything I publish carries its source: the rubric is versioned, the market numbers will name their boards and their country, and any teardown of somebody else's work happens with their permission or not at all. Claims in the notes are tagged by where they come from, and the legend is on one page. When I get something wrong, the correction goes in the same place as the claim.

What this page does not say

It does not name my current clients or describe their projects. It does not carry a list of tools, because tools were never the hard part. The CBAP is here because it is true, not because it proves the work. The notes and the scorecard are for that.