I'm a Python developer with a background in backend engineering, financial systems, and automation. I've worked in energy market intelligence, fintech, and IT services — mostly building the kind of software that handles real data and real edge cases.
My primary tool is Python. I occasionally work with AI/ML and React when the project calls for it, but backend systems and APIs are where I spend most of my time.
I'm comfortable owning a project end-to-end: from architecture decisions through implementation to deployment. I care about code quality, clear architecture, and making technical decisions that the next engineer can understand.
I work best with companies that have a clear problem, respect engineering, and want someone who communicates well with both technical and non-technical stakeholders.
I operate as a registered sole proprietorship (CEIDG) in Poland for freelance and B2B contracts — programming and related IT services (PKD 62.10.B and associated codes). Registered address: ul. Obrońców Westerplatte 144A, 80-317 Gdańsk. NIP: 8442338935 · REGON: 522772081
Public company record (Monitor Firm / PB.pl)2025 — Present
Python Developer @ Energy Aspects
Energy market intelligence & research analytics
Research analytics — pipelines and internal tools turning market and commodity data into products for institutional subscribers.
2024 — Present
Senior Python Developer @ JIT Team
IT services & software development · Warsaw / remote
Client projects in a software-house model — backend APIs, integrations, data processing, and shipping maintainable services for teams in Poland and abroad.
2024 — 2025
Python Developer @ Equiti
Online brokerage & fintech (forex, CFD, multi-asset)
Backend and platform work for a regulated online broker — trading workflows, integrations, and internal tooling in a high-availability environment.
Core languages
Backend
Data
Infrastructure
Frontend
AI / ML
Testing
I start with the problem, not the stack. A good solution is one that fits the actual constraints — team size, operational maturity, timeline, budget — not the one that uses the most interesting technology.
I communicate clearly and early. If something is going to take longer than expected, you hear about it before it becomes a problem. If the requirements have a hidden complexity, I flag it in the planning phase.
I write code that other engineers can read. Good naming, clear structure, tests on the important paths. The kind of code that doesn't need a 30-minute explanation before you can contribute to it.