Mikhail Necheporenko

Zero to Hero Team leader
" Zero to Hero is a way to show young guys that they already go a long way"
Zero to Hero Team leader Mikhail Necheporenko is explaining you why Zero to Hero is useful for startups, which junior developers are working on creating prototypes, and how Zero to Hero affects the IT industry
What are you doing at Zero to Hero?
In Zero to Hero, I have several tasks. On the one hand, I help the customer formulate the prototype description. What hypothesis do we want to test? Who, how and when are we going to show the prototype? How will we record and analyze the result ? By saying "we", I mean the customer and Zero to Hero, because we are a joint team with a common goal.
A prototype is a product with a short "lifespan", the purpose of which is one: to confirm or refute the hypothesis. After that, it finds its way into a bin. A prototype can' be created as a full-fledged project or MVP. To create it effectively, it is extremely important to answer the above-listed questions (the list is not complete).
On the other hand, together with the Lucky Hunter team, we form a remote team of junior developers led by a senior team leader in a short time. These guys have never worked in a team, see each other for the first time, while many of them don't have any work experience. But they have a thirst for knowledge and experience. They are ideal for prototype creating task, where issues of architecture building and don't come first.
The guys learn to work as a team and produce a single team result. In the project, they gain communication skills, learn how to solve tasks, make decisions and protect their ideas.
We aren't just looking for workers, who need clear technical enquiries. We are looking for proactive guys, future senior developers. It is almost impossible to become a united team on a tight schedule. Therefore, my task is not only to find promising guys, but also to make a "combative" team out of them. I think one day I'll share how I do it.
What's Zero to Hero for you?
The project didn't appear from scratch. We've already had experience in creating teams from junior developers. And in the Lucky Hunter database, there were many promising young specialists who couldn't find a job due to lack of experience. But where to gain it, if experience is gained precisely on projects which almost always demand experience? Here is such a vicious circle. I understand companies that can't take a person without experience. This is a time-sapping, expensive and highly risky project.

We've decided to help young professionals and at the same time make real commercial projects. So we created Zero to Hero. At the beginning, we couldn't even imagine what reaction it would trigger and how relevant this issue appeared to be. The competition is 100-200 candidates for one place. This is a really big stream of those wishing to become a part of the project. It's hard to understand which candidate is the best. We had to decide who we needed. And we formulated it this way: "we are looking for future senior developers." In other words, those who in their soft skills and aspirations are already senior, it remains only to improve hard skills.
Zero to Hero is a way to show young guys that they already go a long way. To transfer them from the state "nobody needs me" to the feeling "we can do cool things qualitatively", supported by a successfully completed project.
If we consider Zero to Hero from the customer's side, then it's even more interesting. Our mission has changed and supplemented several times, and it is still developing. At first, we thought that our goal was to take simple projects (which 2-3 senior developers can do in a few days) and perform them with the help of junior teams. This is still more cost-effective than hiring in-house developers. But after we saw the first results of our teams, we quickly realized that we were able to carry out complex projects efficiently. Moreover, some customers didn't want to stop cooperation after the completion of the prototype.

We understood that we can immediately employ the whole team or individual developers. In other words, the customer receives not only a prototype for 4 weeks but also the opportunity to hire promising young guys who are already immersed in the specifics of the customer's business. It's a win-win situation. Even if the current customer isn't ready to expand his team, we can gladly share the successes of our future senior developers.
The entire IT market gains access to the contacts of young professionals for whom we can undertake. This is a great way to hire strong newcomer without wasting a lot of time on search.
To summarize and answer the question: Zero to Hero is a very strong social project for me. It touches many sides:
1
Helps to believe young and talented, but scared guys in themselves.
2
Helps formulate and effectively test a hypothesis to a customer.
3
Develops the entire IT-community.
I'm happy that I can participate in such a project.
What is the main reason you've decided to join the project?
There are many reasons, but here's the main one: Zero to Hero is a great way to contribute to your favourite IT industry. I've gained quite a lot of experience, which I want to share. I tried to do this before but I realized that experience is not transmitted by the push model when you try to tell the truth to an indifferent person. The most effective way is a pull model when people are interested in gaining knowledge not less, but even more than you.

An interested person has many tools for this. Through questions, analysis of situations and introspection, through experiments, through victories and defeats. And when it turns out to be implemented "in action", the effectiveness of gaining experience goes through the roof. Zero to Hero is an ideal project for sharing experiences. It is remembered for the whole life.
Test the hypothesis?