I managed Dmytro for over two months. He was assigned to our team after his team was disbanded and its members were spread across other areas, due to a reorganisation of the engineering area. Dmytro came with experience on JVM-based languages, most recently Clojure. Our team was using mainly Ruby. He impressed me in our first internal interview with how pragmatic he is regarding languages, tools and paradigms. He really considers himself a generalist and focuses on learning skills that are transversal to software engineering, skills that he can bring with him to any language: best practices on testing, clean code, KISS principle, etc. He considers languages as just another tool, and picks the one better suited for the task and the team. It took him around a month to go from never have installed or used any tool from the Ruby stack, to have his local environment up and running and several Ruby PRs deployed to production. I should point out that having the local environment for the Event stack at Hopin, was quite a feat in itself. If anything, my only complain would be that he worried too much during that month because he was not delivering code. But during that time, he was already delivering value: he updated all readme docs about the local environment setup, took care of creating a diagram of the content moderation stack requested by upper management, and made valuable recommendations and suggestions during our retros. In terms of culture and behaviour: he's a quiet person who nevertheless participates in the team socials, has fun, and contributes to create an environment where everyone enjoys working with him. All the feedback I got about him from the rest of the team was extremely positive. I've never detected even the slightest sign of ego. He speaks his mind, listens to others, and really evaluates decisions based on arguments and facts. He knows when a solution is good enough and doesn't have any tendency towards overengineering. I can’t recommend Dmytro strongly enough. He will be a valuable addition to any team.

I managed Dmytro for over two months. He was assigned to our team after his team was disbanded and its members were spread across other areas, due to a reorganisation of the engineering area. Dmytro came with experience on JVM-based languages, most recently Clojure. Our team was using mainly Ruby. He impressed me in our first internal interview with how pragmatic he is regarding languages, tools and paradigms. He really considers himself a generalist and focuses on learning skills that are transversal to software engineering, skills that he can bring with him to any language: best practices on testing, clean code, KISS principle, etc. He considers languages as just another tool, and picks the one better suited for the task and the team. It took him around a month to go from never have installed or used any tool from the Ruby stack, to have his local environment up and running and several Ruby PRs deployed to production. I should point out that having the local environment for the Event stack at Hopin, was quite a feat in itself. If anything, my only complain would be that he worried too much during that month because he was not delivering code. But during that time, he was already delivering value: he updated all readme docs about the local environment setup, took care of creating a diagram of the content moderation stack requested by upper management, and made valuable recommendations and suggestions during our retros. In terms of culture and behaviour: he's a quiet person who nevertheless participates in the team socials, has fun, and contributes to create an environment where everyone enjoys working with him. All the feedback I got about him from the rest of the team was extremely positive. I've never detected even the slightest sign of ego. He speaks his mind, listens to others, and really evaluates decisions based on arguments and facts. He knows when a solution is good enough and doesn't have any tendency towards overengineering. I can’t recommend Dmytro strongly enough. He will be a valuable addition to any team.

I managed Dmytro for over two months. He was assigned to our team after his team was disbanded and its members were spread across other areas, due to a reorganisation of the engineering area. Dmytro came with experience on JVM-based languages, most recently Clojure. Our team was using mainly Ruby. He impressed me in our first internal interview with how pragmatic he is regarding languages, tools and paradigms. He really considers himself a generalist and focuses on learning skills that are transversal to software engineering, skills that he can bring with him to any language: best practices on testing, clean code, KISS principle, etc. He considers languages as just another tool, and picks the one better suited for the task and the team. It took him around a month to go from never have installed or used any tool from the Ruby stack, to have his local environment up and running and several Ruby PRs deployed to production. I should point out that having the local environment for the Event stack at Hopin, was quite a feat in itself. If anything, my only complain would be that he worried too much during that month because he was not delivering code. But during that time, he was already delivering value: he updated all readme docs about the local environment setup, took care of creating a diagram of the content moderation stack requested by upper management, and made valuable recommendations and suggestions during our retros. In terms of culture and behaviour: he's a quiet person who nevertheless participates in the team socials, has fun, and contributes to create an environment where everyone enjoys working with him. All the feedback I got about him from the rest of the team was extremely positive. I've never detected even the slightest sign of ego. He speaks his mind, listens to others, and really evaluates decisions based on arguments and facts. He knows when a solution is good enough and doesn't have any tendency towards overengineering. I can’t recommend Dmytro strongly enough. He will be a valuable addition to any team.