Your candidate has a Profy.dev app on their resume?
Here is how we prepared them to work on your development team.
Most developers at the beginning of their career don't know how to work on a professional team. They may have built small applications like a Todo or Weather app. Maybe they even worked on a slightly bigger project. But for the most part, they worked alone.
You know that this is totally different from working on a professional developer team. It's not only about the code. To work on your team the developer needs to know
- how to work with Agile processes
- how to use a professional Git workflow
- how to work with tasks
- how to work with designs.
Hiring a developer without years of professional experience typically means you need to teach them all these skills on the job. Apart from all the things they already have to learn about your product and codebase...
What if your candidate was production-ready?
In an ideal world, your new developer knew how to work on your team already. They knew their way around Git. They would be comfortable working in an Agile environment with tickets and designs.
You and your team would save so much time on training and explaining the basics. You could focus on what's important to you: Your product, your system, and your code.
Your new developer would be productive quickly without blocking team resources for months.
Of course, that's the ideal world. But how should you even get close to such a candidate in the real world?
We prepared your candidate for a professional team so you don't have to.
Our developers go through a program designed to prepare them for a job. A job on a professional team in the real world.
Here is how it works.
1. They learn professional skills
Our developers first go through a series of lessons. The goal is for them to gain background knowledge about working on a professional team. This knowledge includes
- How development teams typically operate.
- The feature lifecycle from idea to release.
- Project management and working with tasks & user stories.
- Using a professional Git workflow with Pull Requests and code reviews.
- Writing automated tests.
2. They use professional tools
Our developers get access to tools used in real-world companies just like yours.
A professional UI/UX designer prepared the designs used to build the project. Our developers get access to Figma and use these designs to write their custom CSS.
To approach the implementation in a structured way, the application is split into small features. Our developers learn to break them into user stories.
3. They use a professional Git workflow
Using Git in a team can be complicated at the beginning. Especially since most new developers are only used to working on the main branch on their own.
Our developers use the GitHub Flow to implement the project.
- They commit their code to feature branches.
- They create Pull Requests.
- They ensure that the CI pipelines and automated tests pass.
- They get feedback in code reviews.
- They squash merge the PRs.