Ömer Aydin is a Berlin-based Product Manager with 11 years of experience translating user needs into delivered software within Agile teams, currently shaping product direction at Anaconda. He blends hands-on backend engineering experience—contributing to open-source projects like the Automatisch Zapier alternative and RubyGems.org—with strong product skills in requirement prioritization, sprint planning, KPI definition, and BI-driven analysis using Power BI, Tableau and SQL. His background as a team lead, business analyst, and trainer gives him a rare mix of technical fluency, stakeholder facilitation, and documentation discipline. Ömer also prototypes interfaces with tools such as Justinmind and Axure, ensuring practical handoffs between design and development. Colleagues rely on him to bridge users and engineers while bringing measurable, data-informed decisions to product roadmaps.
11 years of coding experience
10 years of employment as a software developer
Master of Science (M.Sc.), Educational Administration, Master of Science (M.Sc.), Educational Administration at Ankara Hacı Bayram Veli University
Bachelor of Science (BS), Computer Education and Instructional Technology, Bachelor of Science (BS), Computer Education and Instructional Technology at Orta Doğu Teknik Üniversitesi / Middle East Technical University
The open source Zapier alternative. Build workflow automation without spending time and money.
Role in this project:
Back-end Developer
Contributions:11 releases, 432 reviews, 776 commits in 1 year 3 months
Contributions summary:Ömer primarily contributed to the back-end functionality of the open-source Zapier alternative, "Automatisch." They implemented database connections, including one for PostgreSQL and made improvements to various internal models. The user also worked on integrating different applications and features.
Contributions:55 commits, 40 PRs, 95 comments in 1 year 1 month
Contributions summary:Ömer primarily contributed to the RubyGems.org repository by modifying the backend code, focusing on API improvements. Their commits included adding user IDs to JSON responses for various API endpoints. They updated the owners API to accept user IDs, and fixed issues related to documentation URLs and gem statistics retrieval from Redis. Additionally, the user worked on implementing changes to display and filter gem information, such as excluding yanked gems from user profiles.
ruby-on-railshostingrubygemsrailsruby
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.