SM Tech | Software Development

Independent software engineering studio

Have a look what I can offer to you, here you can find some information about my services, my experience, and the way I work. If you want to know more, feel free to contact.

Contact View projects

MY RULE / 01 Be Professional

Create and maintain business software with a focus on reliability, clarity, and long-term value

MY RULE / 02 Be Practical

Build practical tools and applications that solve real problems and improve everyday workflows

MY RULE / 03 Be Open-minded

Explore new technologies with a practical mindset, using them where they add real value

About me

Hello!

I am Mateusz Siepracki, software developer with 999 years of experience. I worked for industries where precision and reliability are a must: finance, aviation, sport - adapting to each one's constraints has always been one of my biggest professional strengths.

Throughout my career I've worked on both systems that started from scratch, contributing to their architecture and design from the ground up, and maintenance of complex existing codebases. That range gives me a practical understanding of the full software lifecycle.

A highlight of my career has been a sport industry project I joined from the very first line of code. I was shaping the architecture, drove it through to a successful production deployment, and continued owning its maintenance as it scaled. When the product grew large enough to spin off as an independent company, I've planned and executed full migration to a dedicated AWS account - coordinating the technical and organisational complexity that comes with it.

My biggest strength is backend development, with deep expertise in Java and Spring Boot. I effectively cover the full delivery stack: PostgreSQL and MySQL databases, Docker containerisation, RabbitMQ messaging, CI/CD pipelines with GitLab and GitHub Actions, infrastructure-as-code with Terraform, and AWS cloud services. I also like to experiment with new technologies, like LLM-supported development, having in mind that system requirements and current industry standards are always fulfilled.

I am a team-first developer: technical delivery and clear communication are equally important.

How I work

From the first conversation to a working product

I keep development clear and practical from the first conversation to the released product. I start by understanding the problem, users, and business context, then turn that into sensible architecture and technology choices. I develop carefully, verify behavior, take care of the release, and keep improving the software as requirements change.

01 / Discovery

Determine the path

Before I write code, I want to understand what the product needs to achieve, who will use it, and where the main risks are. Good analysis keeps the scope focused and helps avoid expensive work that might not be necessary.

02 / Architecture

Craft long-lasting solution

I think through service boundaries, data ownership, APIs, integrations, and failure handling early to avoid painful rewrites. For distributed systems, I focus on clear responsibilities, maintainability, observability, and predictable behavior.

03 / Technology

Use tools that earn their place

I prefer technologies that are stable, well supported, and appropriate for the problem. New tools can be useful, but the stack should make delivery easier, not add complexity just because something is fashionable.

04 / Implementation

Code development

Code itself is considered by many people as the most important step, but for me it's a part of a bigger picture. I think that good implementation is something that does the job, following best practices at the same time. Clean code, focused responsibilities, proper unit and integration tests, and service contracts - I focus on all of them through the whole process. Building new features is always fun, but debugging and improving an existing codebase is also important for the product to succeed.
Here are example technologies I have the most experience with, but I'm always eager to expand my skills to match customers' expectations.

Java Spring PostgreSQL Docker AWS Terraform RabbitMQ CI/CD

05 / Quality

Behavior check is a must

Testing, code review, logging, and failure analysis all matter and improve code quality. They help confirm that the direction is correct and prevent the same issues from coming back through regressions. Software must behave correctly and be easy to support when real users start using it.

06 / Delivery

Predictable releases

I care about the whole path from local development to production. Docker, cloud infrastructure, CI/CD pipelines, configuration, and release checks must work together to make deployments repeatable and reduce any risk.

07 / Maintenance

Release is not the end

Even after a successful release and positive client feedback, I stay vigilant. Maintenance is something that I guarantee with my services. Fixing issues, improving performance and adapting to the requirements change - all of that still happens after release and I am prepared to support that work.

Projects

Some examples of my solutions

Here is brief overview of my projects - have in mind it's just a sample and new challenges, depending on customers' needs are always welcome. I cannot share everything due to NDAs, but I hope that can be a good sample what I am able to create.