My experience

As a Business Analyst

Retail

Insurance

Global

  • Writing comprehensive, technically advanced and well-structured functional and technical documentation - 50% of time.
    Mostly in Confluence or MS Word. I'm a big fan of Confluence and a very advanced user of it. I document everything I can. Once in 2022 I counted... I wrote over 400 official documents.
  • Conducting functional workshops, trainings, demos and presentations - 20% of time.
    To all level of audience - customers, internal operations, direct management and C-level.
  • Create company-wide standards, prepare templates, research new tools - 10% of time.
    I supported other BAs from a central team responsible for standardization of our solutions and work.
  • Travel to stakeholders, conduct meetings, organize customer dinners and outings - 10% of time.
    Building relationships with our stakeholders is a very important part of being a BA, in my opinion it's pure fun.
  • Elicit requirements, prepare user stories, prepare customer journeys - 5% of time.
    I supported whenever I could but in most cases the requirements came from my customers.

As a Software Developer

  • In .NET - extending retail point of sales systems, create loyalty systems and write internal tools.
    I started as an intern and quickly moved through the retail world. At some point I left the developer role and moved to being a BA. But personally I still code in .NET
  • In Java - creating microservices, integrating with Kafka, using Spring (boot, batch, data, rest, webmvc), Hibernate (PostgreSQL, MongoDB), Mockito and JUnit for unit tests, recently Angular for front-end.
    I moved again from a BA role to a developer in my recent employer. At heart I will always be a developer, but I do not forget about my vast BA experience. At the moment I conduct two roles at the same time (BA + DEV)
  • Design and implement databases - mostly Microsoft SQL, mySQL but also recently PostgreSQL, MongoDB and Google Firebase.
    I enjoy structuring data and optimizing databases. I always start creating systems with database-first approach.
  • In Kotlin/Android - writing utility apps with cloud connectivity (Google Firebase), non-commercial.
    I wanted to try to write something more tangible than large enterprise systems, therefore I gave it a go with Android. I published so far two Android apps in Google Play and I'm open to creating more of them
  • In indie Game Development - designing and implementing games in Unity 2D. This includes doing design, coding, sound editing, animations and publishing.
    An evolution of Android apps was to create Android games so that's the direction I went it. So far I published one arcade game in Google Play and I am working on another, much bigger one.

Retail

Insurance

Personal

Powered by Webflow