Tomasz Maczukin

Właściciel at GitLab Inc.

Olsztyn, Warmian-Masurian Voivodeship, Poland
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts

Summary

🤩
Rockstar
🎓
Top School
Tomasz Maczukin is an experienced backend engineer and IT specialist with 11 years in software development, currently contributing to GitLab as a Senior Backend Engineer while running his own IT consultancy. He focuses on Go, Docker, and Kubernetes, and has improved CI/CD robustness by adding keep-alive APIs and refactoring job lifecycle handling in the high-profile gitlabhq project. His DevOps work on the Omnibus configuration shows attention to system stability, logging, and dependency management across complex service stacks. Based in Olsztyn, Poland, he blends hands-on engineering with operational discipline and brings practical improvements that reduce downtime and simplify maintenance. Outside of work he’s an avid hiker, sailor and sport shooter, hinting at a calm, risk-aware approach to problem solving.
code11 years of coding experience
bookUniwersytet Warmińsko-Mazurski w Olsztynie
languagesEnglish
stackoverflow-logo

Stackoverflow

Stats
51reputation
10kreached
1answer
0questions
github-logo-circle

Github Skills (18)

ruby-rails10
docker10
apidoc10
configuration-management10
rails10
dockers10
cicd10
ruby10
chef-client10
gitlab10
api10
chef-solo10
devops10
rspec9
continuous-integration6

Programming languages (10)

TypeScriptC++ShellCGoOpenSCADMustacheHTML

Github contributions (5)

github-logo-circle
gitlabhq/gitlabhq

Nov 2015 - Sep 2019

GitLab CE Mirror | Please open new issues in our issue tracker on GitLab.com
Role in this project:
userBack-end Developer
Contributions:448 commits, 14 pushes, 8 tags in 3 years 10 months
Contributions summary:Tomasz's contributions primarily involve implementing and modifying API endpoints related to CI/CD jobs. They introduced a new keep-alive API entrypoint for CI jobs, enhancing their functionality and improving their lifecycle management. Furthermore, they refactored existing code to utilize the job update endpoint for the keep-alive functionality. This involved changes to both the API layer and associated testing, demonstrating a focus on CI/CD system improvements within the GitLab project.
gitlab-apinew-issuestrackerrailsgitea
gitlabhq/omnibus-gitlab

Feb 2016 - Mar 2017

GitLab Omnibus Mirror | Please open new issues in our issue tracker on GitLab.com
Role in this project:
userDevOps Engineer
Contributions:48 commits, 24 pushes, 35 branches in 1 year
Contributions summary:Tomasz focused on maintaining and improving the GitLab Omnibus configuration. Their contributions primarily involved updating logging configurations for various services, specifically `gitlab-workhorse`, `gitlab-pages`, `mailroom`, and `remote-syslog`. They also made adjustments to the Ruby version and dependency configurations and updated the Docker registry version. The user's work directly impacted the system's stability, logging practices, and overall maintainability.
new-issuestrackergitlabgitlab-omnibusissue-tracker
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.
Request Free Trial