What does recruitment at Docplanner Tech really look like? Report from the new Developer’s point of view
Hi! I just began my work as a junior PHP developer at DocPlanner Tech and wanted to share my thoughts on the recruitment process that is just behind me. Are you curious? Let’s get started! :)
First of all, it wasn’t “typical” recruitment, during which you need to talk to a recruiter not very subject-oriented, then you get to solve a task not adapted to your level, and finally, you don’t get any feedback. I think you’ve been there and done that.
This time it was completely different, though not necessarily easy (did anyone say it supposed to be?). The recruitment process lasted about three weeks in total, and it certainly was a challenge. But fear not, after all, everything had a happy ending :)
So, let’s start from the beginning…
The first stage is the analysis of the sent documents. In my case, i.e., a developer with slightly over a year of commercial experience, I was ready to be dropped out of the process at this first stage. So, I wrote directly to the recruiter, sent my CV and thus began my recruitment in a somewhat unusual and direct way — instead of filling out the official form, I simply contacted the company :)
Less is not worse
After the company analyzed my CV and GitHub projects, I received the first specific feedback. I was invited to the second stage of recruitment. This stage is usually a conversation with a People Experience team representative and a developer. In my case, it was different. Despite some shortcomings in the art of development, only because of my little experience, I got a chance to prove myself in a task I got to solve. I had to write an application, and I got two weeks for it.
At first, it seemed like a long time, but as the days went by, even though I was writing the code at every free moment (after work and on the weekends), it turned out that it was not so much time. Especially if some things don’t go well, or the code can play tricks in the least expected places and moments. Thanks to my determination and motivation, I was able to return the task a few days ahead of schedule and complete all of its additional points.
Feedback, and of what quality!
Already after two days, the developer handling my recruitment sent me extensive and very detailed feedback on the task I completed. (You can learn more about why in DocPlanner feedback is so crucial from this article: https://medium.com/docplanner-tech/give-feedback-now-directly-856bebff7aac
What captivated and, at the same time, very positively surprised me in the received feedback was its insight and quality. Usually, when participating in recruitment, I didn’t get feedback at all, or it was a few dry sentences without any justification. This time it was completely different.
I learned what I was able to accomplish, what I could do differently (which does not mean that I did it wrong), and constructively — what went worse. The information was in such a clear, substantive, and accessible way that even if I would not go any further, the feedback itself was valuable to me as winning the lottery (seriously!) :)
Encouraged by this substantive bomb in the form of feedback, I started to correct my task and introduce the suggestions I received. I did it entirely regardless of the subsequent stages of recruitment that were still ahead of me.
Trial day — this trial is not so scary
The third stage also turned out to be a surprise, and again a positive one, although, at the same time, it meant that I had to get out of my comfort zone a bit. I was invited to the company for a trial day. You can read about this form of recruitment here: https://medium.com/docplanner-tech/why-i-dont-believe-in-a-classic-recruitment-approach-9f3cb08adf8a
Initially, in addition to the joy that I got to the next stage of recruitment, I felt uncertainty about what such a day would look like.
After setting up a date convenient for both sides, I got a message with the agenda for that day. Although it was only a general schedule, I immediately felt much more confident knowing what was ahead of me. For example, I was to eat lunch together with the team that I was to spend this day with.
The trial day began with a conversation with the recruiter and the developers who were to look after me. We set the plan for the day, got to know each other better, and discussed formal issues related to employment.
During the day, in addition to solving tasks, I had the opportunity to participate in several interesting meetings. Some of them were brainstorming sessions, during which I discussed with other developers the task I was working on at that moment. I also had the opportunity to talk to the Engineering Director. I ate lunch, during which I met several people from the company. The day passed quickly, it was very dynamic and, what is essential, it was not just about sitting at the desk. In the end, relationships with other colleagues are no less important than writing new lines of code.
I quickly got the impression that the purpose of a trial day as a form of recruitment is not only to solve the received task. It is more important to get to know each other and to verify one’s expectations towards the future employer, and on the part of the company to assess me as a potential co-worker.
By the end of the day, I got initial feedback — mainly technical, and I could give my impressions of the entire day. For information on whether or not I am going further, I had to wait some more.
Good feedback — never enough
Soon I received a message, and in it was— yes! — Feedback once again :)
This time it was a summary of how I was perceived during the trial day. Again, all that went well and that could go better was pointed out insightfully and comprehensively. Once again, I received a substantive and sound dose of useful knowledge about myself, and at the same time, I learned that I got to the next, final, recruitment stage.
References — an important piece of a puzzle
The only missing part needed to complete the picture of how I was perceived during the trial day was the information gathered from my former colleagues. Therefore, the last stage of recruitment was for me to provide contacts to several people with whom I had the opportunity to work in previous companies. And finally, after a few days, the final feedback! :) Yes, feedback again and, as befits DocPlanner, once more as full as possible. During a very friendly video conversation, I found out that I would soon join DocPlanner Tech.
Summary
I have to admit that this was my most demanding recruitment, both in terms of time and merits. What both delighted me the most and surprised positively was the feedback. I received it after each of the four stages of the recruitment process. No less important was the constantly friendly and relaxed atmosphere that, for me, made each subsequent stage more of an exciting adventure than a stressful duty.
These three weeks of recruitment were a fascinating adventure, during which I got to know the company I applied to and verified my expectations toward it. On the other hand, the company got to know me and my expectations as much as possible. So, it wasn’t typical, meaning tedious and stressful, recruitment. Can it be done? Of course!
If you want to learn more about what to look for, if you’re looking for a job right now, read the article by Adam, one of our developers:
https://medium.com/docplanner-tech/few-things-to-remember-when-you-apply-for-a-job-44ac6c4efd8d
