Adam Groszer
Principal Software Engineer at pyte
Hungary
Summary
👤
Senior🎓
Top SchoolAdam Groszer is a Principal Software Engineer with 17 years of hands-on experience designing and shipping Python-based backend systems, currently continuing Shoobx work within Fidelity Labs from Hungary. He specializes in Zope 3/ZTK, buildout automation, and full-stack backend work—bringing deep expertise in databases (ZODB, PostgreSQL, MongoDB) and deployable infrastructure. Adam has a track record of improving cross-platform tooling (notably Windows fixes and documentation for buildout) and enhancing code-quality tooling, contributing ESLint integration and test coverage improvements to open-source projects like diff_cover. Comfortable across startups and enterprise environments, he has built production systems end-to-end—from REST APIs and background workers to repeatable Ubuntu/KVM deployments and DevOps automation. Clients and teams benefit from his blend of pragmatic engineering, long-term maintenance focus, and a penchant for making legacy Python stacks robust and testable.
17 years of coding experience
23 years of employment as a software developer
BSC, Engineering, BSC, Engineering at Dennis Gabor College
English, German, Hungarian
Stackoverflow
85reputation
4kreached
3answers
2questions
Github Skills (17)
git10
javascript10
python10
testing10
windows10
eslint10
windows-xp10
build-automation10
build-tools10
sqlalchemy6
emacs6
virtualenv6
ide6
flask-sqlalchemy6
zip6
Programming languages (10)
Github contributions (5)
buildout/buildout
Mar 2009 - Feb 2017
Buildout is a deployment automation tool written in and extended with Python
Role in this project:
Backend Developer & Automation Engineer
Backend Developer & Automation EngineerContributions:23 commits, 3 PRs, 1 push in 8 years
Contributions summary:Adam primarily focused on improving the `buildout` project's compatibility with Windows systems. Their contributions include fixing script generation for Windows, addressing shebang issues related to Python interpreters on Windows, and incorporating a Windows-specific build status image. They also made adjustments to core buildout functionality to ensure proper behavior on different operating systems, specifically addressing problems in the testing and easy_install components. Additionally, the user updated the documentation with the addition of Windows-specific instructions and considerations.
continuous-deploymentcontinuous-testingpythondevopsdeployment
Bachmann1234/diff_cover
Jan 2016 - Nov 2017
Automatically find diff lines that need test coverage.
Role in this project:Full-stack Developer
Full-stack DeveloperContributions:7 commits, 2 PRs, 9 comments in 1 year 10 months
Contributions summary:Adam primarily contributed to the implementation and testing of ESLint integration within the `diff_cover` project, including adding an ESLint driver and updating the tool to recognize ESLint violations. They refactored and added tests for the ESLint functionality. The user also added the ability to exclude files at the diff-cover level. These changes enhanced the project's code quality analysis capabilities.
linestestingneedcoveragetest-coverage
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.