Adam Puza Email & Phone Number

Experienced backend engineer (15+ years), architect, and team lead focused on delivering business needs. Strong team player, focused on team evolution based on examples and practice instead of theory. TDD/BDD enthusiast and teacher - lucky to work with the best on a vast scale system.- CTHINGS.COWith deep knowledge of asynchronous programming, multithreading, and network transports, I am responsible for delivering the core of Orchestra.- Appjobs/UnveelI participated in creating a revolutionary, unique, on a global scale, real-time system processing data from gig workers: Aggregating Uber, Glovo, Bold and several other apps in one consistent place.- Blue Focus/360dialogI've created architecture and code for the performance marketing system that works for millions of devices. I supported a system that operates on millions of mobile phones (for customers like T-Mobile, HRS, ImmoScout, Rossmann and many more) in real-time.- eSKY.pl S.A.I led the backend team and was responsible for market lead software for the reservation of flight tickets. I participated in expansion to other markets, including South America, and resolved all technical problems connected to working across continents (multiple data centres, latency, synchronization, security).SpecializationMy specialization is Test-driven development/Behavior-driven development and Coding Standards. I'm teaching the teams/companies about. Over the years, I mentored outside teams. I implemented TDD/BDD flows in companies, including mentoring and rearranging the work in teams in small and enterprise-sized companies.In each company, I introduce proper testing flow. The stability of code is my passion. My goal is to create a system where engineers can work in an efficient, productive way and produce a stable code. For example, in 360dialog, I implemented a framework (I can be proud because it was entirely my know-how and responsibility) that covers the proper way of creating and testing (unit/integration) software. And I teach the team to work with it. With this way of work, I introduced our team to writing code so stable that we do not have failures and no on-duty, even with software working all the time with millions of connections on more than 600 containers. The code deployments were immediate (CI/CD), and we were never afraid to deploy code even on millions of connections. And we never had any failures. I spent 1,5 years introducing the way and teaching the team how to work, but in the next few years, the code was always stable, and our system never failed on a vast scale.

• 

  Politechnika Śląska

  Inżynier (Inż.)