Although he doesn't have an engineering background, he can take better decisions than an experienced engineer.
He did this not just with engineering, but with the whole company.
John understands what engineers want and he accommodates engineers' needs very well.
His engineering philosophies and meticulous coding have inspired many engineers.
All these made him the go-to-guy for the engineers across the company.
His attitude towards the engineers and others is very special.
John influenced him more than any other engineer at our company.
Yuriy is just an example of what our company engineer should be.
He's an engineer's engineer, and is someone you just want to go into battle with as a leader.
We have continuously come at him with many changes and new directives regarding the engine.
He also goes out of the way to help people and groom new engineers.
John always motivated the engineers and got the best out of them.
We in the engineering department used to look for his inputs.
John is a brilliant engineer on his own, at the same time he is well respected by the engineers around him.
He's one of the few front-end engineers that really has a good solid engineering background.
John is an excellent engineer and a great asset to any engineering company.
He interviews the candidates himself along with his engineers.
Software engineering is not only his job, but also his hobby.
He saw and felt a need in the underclassmen engineers to experience engineering first hand.
John always makes sure that his engineers get the visibility they deserve within the company.
John always had time for younger engineers even the ones that were not in his group.
There is no doubt regarding his capability for both engineering and organizational.
He taught him so many things about engineering, about cooperation, and about life.
The needs assessment he conducted was thorough, not over-engineered and fast.
John listened to not only engineers, but the end users and stakeholders.
He always found top engineers from the best companies and universities.
His understanding of the various engineering disciplines is remarkable.
He is looked upon as one of the best engineers in the entire company.
He not only improved himself, but also elevated his fellow engineers.
John would be an asset to any company and engineering organization.
He pushes the engineers to make sure things gets delivered on time.
John's years of experience as an engineer is quite intimidating.
Hence he became one of our best engineers in a very short time.
At the same time, he respected his leadership of the engineers.
Our company & John were classmates during our engineering studies.
John has been one of our most meticulous our company engineer from the beginning.
As much as he excelled at our company he was even better on the engineering side.
John's creativity is the engine behind everything he accomplished.
In his estimation, that is unique when it comes to an engineer.
Our company, True engineer, last but not least very creative.
His understanding of engineering issues allows him to know when to allow engineers' time to do their jobs and when they may need some help.
He can then either directly help the engineer or at least point them in the correct direction.
He helped other engineers in the same way when it came to his area of expertise.
He genuinely wanted to see us become better as both people and engineers.
John reported to him for several years and was one of our best engineers.
As an engineer, he is very meticulous about meeting his responsibilities.
Most importantly, he helps the people around him become better engineers.
He's so matter-of-fact that you don't know he's engineering the meeting.
They see him as a motivator and bringing the best out of the engineers.
That makes him an engine for change, not just another cog in the wheel.
He engineers the recordings and ensures that everything goes smoothly.
Ilkka has been an inspiration and mentor throughout his time at the engine
John has been an engineering partner for him for quite a while.
He is not an engineer, but he knows plenty about engineering, and he also takes the time to understand the needs of the specific role.
It's no surprise to him that he has an engineering and mathematics background because he approaches sourcing like an engineer.
John's responsibilities grew quickly from front-end engineer to full stack engineer.