Monsters in your office and how to deal with them

As a child, you were sure that monsters are unsympathetic creatures with claws who were about to jump at you from under the sofa. Who would have thought that they could be bumped into not only in a dark room, but also in the metro at rush hour, in the queue to the therapist, and even in your own office (when you accidentally took someone else’s cup)?

All of us, from time to time, are just not in the mood. But some individuals constantly behave disgustingly and enjoy mocking others. Let’s look at it in terms of werewolves. Some people are hairy monsters only during a full moon. Others became wild and act like beasts on any day of the month.

Each transformation has a reason. Sometimes even a small thing can turn your colleague into something you wouldn’t want to deal with. It’s better to recognise dangerous signs in advance, while you can still fix things without Van Helsing. Let’s see what turns us into monsters, and how to help a colleague become a nice person again.

Wrong side of the bed

It’s so easy to make excuses with this phrase! But after all, only monsters get out on the wrong side of the bed five times a week.

How come? Definitely there is a real reason for bad behavior: a protracted conflict, an unresolved problem or chronic pain. The worst case is when abusing colleagues without any consequences makes a monstrous person satisfied.

Antidote. If your colleague is always not in the mood, talk about it (directly, via your team lead or your HR). A calm tone conversation and honesty can clarify what is this really about.

Monsters in the office

Fear of failure

To worry before some crucial moments is fine. But sometimes a person starts to be insecure no matter the occasion is. In most cases, it ends up with constantly shifting responsibilities to team mates and doubting each step the team makes. This monster person is always responsible for nothing and takes only simple tasks.

How come? Fear of failure appears when a person does not feel secure enough at work. Every incertain decision is a risk of losing their job or status, or the respect of their colleagues.

Antidote. This monster thinks that if something goes wrong he’s in a danger zone. Therefore, the monster person does not want to make anything. To overcome it, you’ll have to work on the feedback culture in the team and find the true cause of the uncertainty.

Monsters in your office


It could turn anyone into aggressive creature as soon as someone starts chewing a cookie nearby. From a systematically hungry person, even a “bon appetite!” can sound like a wish to suppress.

How come? We like to eat! What we don’t like is when a favourite food suddenly becomes forbidden. For example, when people are forced to change their food habits they tend to broadcast dissatisfaction on others who do not burden themselves with prohibitions.

Antidote. Replace the cookies in the office kitchen on fruits and nuts. Advise where a monster person can find some tasty and “allowed” food in town. Or from time to time have an extra sandwich to share with someone who has none.

Monsters in your office


Fatigue appears because of a chronic lack of sleep, too complicated or too simple tasks, or the routine at work. A tired monster person, like an influenza,  infects the office with constant irritability and apathy, which as a result greatly harms the project.

How come? Sometimes, somebody’s fighting fatigue, and simply cannot admit that he/she needs an extra day off, a hand to do the job right, or even have an honest tet-a-tet conversation about what you really want to do on the project.

Antidot. Offer help, give a hand (or two). Advise the fatigued monster to take an extra day off or to work from home for the next few days.

Recently we published an article about chronic fatigue and work: here is a 4-minute read about the causes of burnout and how to avoid it.

Monsters in your office

Petty grievances

Often, we do not see the real value and danger from them. At first somebody broke your mug (and did not admit it), you can hear their music through their headphones, you were the butt of a joke, and a few hours later someone stepped on your brand new white shoes in the metro. And that’s it. Goodbye patience.

How come? After all small disasters monster person can’t handle, he/she starts “defending” and snapping even at those who have always wished them a very good morning.

Antidote. Ask a monster person if everything is fine. Gently let him/her know how unpleasant it is when they start throwing thorns all around. Even if it’s a small bad joke or irritation, speak about it. Otherwise you risk to find yourself covered in thorns some time after.

Monsters in your office

To sum up, a monster person is distinguished from a regular person having a bad day primarily by how often such periods of “not in the mood” are repeated and how long they last. Some people, when constantly under stress, may not even notice that being unfriendly and rude have become their typical way of behaving. That’s where the colleague needs help. The calm and honest feedback are often the key to pacifying any monster person (even if it’s actually about you).

However, if someone in your team looks like a real monster, and, alas, this can’t be fixed with a kind word and warm embrace, we advise you to talk about the problem with your HR or team leads. And in addition, you can read this article about “toxic” behavior in the teams and how to deal with it on your own.

Case Study: work in the Project Unit and motherhood combined

Three years ago, Anastasiia Krekoten made a radical shift. An international economist, she attended Beetroot Academy courses for refugees from Donbas and received her first job offer on the second week after graduation. Nastya is a WordPress developer at Beetroot now.

She talks about the power of multitasking, her inspiring Project Unit experience and how to get back to work with an infant in your arms.

Anastasia Krekoten, WP Developer at Beetroot

The Project Unit is an internal Beetroot team that works primarily with WordPress, PHP, and JS frameworks.

By the way, there are several open vacancies in the Project Unit: WP developers are wanted. Maybe it’s you we are looking for?

All of a sudden, a WP developer

I never thought that I would be a WordPress developer. But here I am! This feeling, when you create something from scratch, is incredible. You eventually turn a set of characters into a properly working site. It’s a kind of magic!

I’ve started working with WP using ACF, Visual Composer and Slider Revolution plug-ins. Next, I learned how to use WPML, BuddyPress, Woocommerce, later on – Google Analytics, AMP and Optimizely. At the same time, I learned PHP, JavaScript, jQuery library. In the past few years I worked on different projects – from corporate sites to online stores, on projects developed from scratch and support for ongoing ones.

In my profession, every day is a new challenge: you must to be a fast learner here! And the easiest way to learn is to practice. Fortunately, at Beetroot I have both practice and support: there is always someone to help you out, advise or assist. On a colleague’s recommendation, I am reading Fullstack React. The Complete Book on ReactJS and Friends – a useful book for my new project on React.js.

Project Unit — no “big boss”, no pressure

Generally, in Beetroot’s Project Unit there is no concept of “subordinates and superiors.” Developers are responsible for the result and are free to manage their working hours at their will. This is very convenient: instead of having a “big boss” who’s in charge of everything you have a stable and friendly relationship in the team.

Of course, we do have a Team Lead. He may wonder if we need help, ask for updates on a project as a whole, but he will never ever put pressure on us or baselessly criticize us The only thing greater than that is direct communication with the client. That helps us avoid Chinese whispers a lot.

Beetroot Work

WP for USA, Kuwait and Sweden

We had a pretty good relationship with clients from different countries. And I never faced any stereotypical problems that are usually attributed to foreigners. But, I admit, some cultural specifics did exist.

For example, we had a real project-shifter from Kuwait. As you probably know, Arabic writing, unlike ours, is inverted – from right to left. While working on the website, I had to ensure that everything in both the Arabic and English language versions worked properly and that all translations were correctly uploaded. This task was a tough one, and at one point I caught myself trying to read a book backwards

In addition, the clients in Kuwait were tempted to put three dots at the end of each message. And what in the world would that mean? Americans, on the contrary, used another form of nonverbal expression and often wrote messages in capitals. Only with the Swedes did I not have any inconveniences – we found a common language from the very moment the conversation started.

It’s been hard to go and hard to come back

I have a little son now. Throughout the pregnancy I felt so comfortable at work and absolutely did not wanted any breaks. I worked till the last day. Literally! I did take maternity leave… and after three days welcomed my firstborn.

I really wanted to come back to work ASAP, but oh, how little I knew about working while taking care of this little gentlemen! Especially with no relatives anywhere around to help out. A colleague of mine managed to get back to work three months after giving birth – once a week she even worked from the office in order not to lose the skills and socialize. I was able to start working remotely only after my son was six months old. Fortunately, my client easily agreed to my “special” working conditions.

On my return, for the first two weeks I tried to refresh my memory and find some rhythm. It’s hard to get on track after such a long break. I felt stiff. Now I work from home at a 75% load: when my son is sleeping or playing, if possible, I can work for an hour or two. When he’s awake or needs attention – I’m there for him. I’ve spoken to my Team Lead and client and we decided to give it a try. So far, everything is going great.

I had the experience of simultaneous work on several different sites before. Perhaps that’s how I’ve learned to efficiently switch between tasks. I know that for some people, working from home or multitasking is not an option, but for me it works just fine. I can concentrate on a task and be productive even if it’s only for an hour. I can get into the flow.

We have an article about that phenomenon of “flow”. Click here to give it a quick look!

My experience proved that “impossible“ is just a word! You need a strong will to start something new without fear of change and complexities. Yes, at the very beginning of the journey, it may seem too hard. Try not to give up; ask for support if things are getting tough. Maybe you are on the very turning point?

Everyone who dares to leave their comfort zone has been where you are now. For you, the choice is to overcome the challenges and push yourself further to the exciting Unknown. Or go back to your roots. I chose the first. And I have never regretted it: now I have a great job that gives me a lot of positive vibes and also friends who are just as passionate about their profession as I am.

T-shaped people are the new IT superheroes?

The canonical superhero: flies, bends metal bars into pretzels, wears tights with a long red cloak. But the IT-world needs a completely different set of superpowers. And to have them, it’s not required to be born on Krypton.

Who are these T-shaped people?

Long story short, the T-shaped people are individuals who can possess deep skills in at least one area as well as acquire broad knowledge and diverse skills.

The T metaphor comes from two lines combined:

  • vertical – stands for the depth of the main specialization;
  • horizontal – illustrates the breadth of related knowledge, a capability of solving an array of problems (and do it fast).

Experienced UI/UX designers have deep knowledge in design — it is their “І” line. Additional general understanding of business processes, management, psychology, programming languages makes them a classic example of T-shaped specialists.

In most cases, Т-people are Middle+ or Senior level specialists who have drilled into management besides their main technical skill. Т’s are in a high demand in product development and startups when you need to have a broader range of shallower skills on top of your “І”.

“In my current role being a generalizing specialist is more valuable.” Tech Lead Adel Salakh says. “I have to keep track of the project as a whole. This wouldn’t be possible without having a broader view. I believe mine skill set can be categorized as T-shaped one, as I had experience with projects ranging from low-level system programming to front end development.”

Why is it cool to be T-shaped?

“If a team consists of T-shaped people, it works seamlessly,” Nastya Khyzhniak, HR-consultant at Beetroot explains. “An understanding of the development processes as a whole helps a development team to build work on a project more accurately. For the supporting roles, like HR, the basics of development would be useful too. For example, in recruiting the right people for the project or during performance reviews.”

This, however, does not mean that you urgently should change from “I” to “T”. Just keep in mind that many modern professions are gradually transforming into T-shaped ones (even if it’s not called like that). The emergence of DevOps is just one of many good examples.

T-shaped people are the new IT superheroes

Jason Yip, Agile Coach at Spotify highlighted at least 5 reasons why generalizing specialists are so super-powered:

  1. T-folks are capable of many things and experts, at least, in one.
  2. Т-shaped people can adapt to wide-ranging demand.
  3. When working in a team with T-people, you can use experts to solve bottlenecks, and non-specialists to free expert’s time from non-priority tasks.
  4. T-specialists allow you to do more with the same number of people in a team (or do the same with fewer people).
  5. T’s provide more effective communication within the team and with the client.

T-shaped teams are flexible, self-sufficient and productive. They provide a comprehensive view of the project and usually have a deeper understanding of its needs. Therefore, they are capable of making complex decisions and releasing a top-notch product. Previously, HR relied on the main specialization when searching for the right candidate. Now they’ll more likely pick with the “T” principle in mind:

“Beetroot helps to build effective distributed teams for different companies worldwide,” Anastasia comments. “More often, the request is a Full-Stack specialist, for example, someone who knows both the front-end and the back-end.”

Adel Salakh adds: “The older the product, the more mature the tech stack in use – the more specialized developers it requires (Java back-end stack is a good example here). Companies that choose newer and more experimental stack setup require more generalist developers.“

How to become a true T?

There is no “know this, do that” list to consider yourself as T-folks in IT. You must have the “І” – deep knowledge and specialization for a start. The rest is curiosity, creativity, caring about the work that you do and practice. Practice as much as you can.

QA Team Lead Nataliia Mylostna has worked for more than nine years in code quality assurance. This is her main specialization. But knowing business analytics, teamwork management, data analytics, and work processes expands her role in a project. “From the very beginning, I’m involved as a Senior QA, but I can become more of a Processmaker, and BA / QA Analyst if needed,” Nata says.

T-shaped people

Aleksey Bobyr, Senior Node-developer, thinks that to form the “I” of a Middle+ specialist you need to learn IDE, Git, Docker, programming languages, frameworks, ticket system functionality, continuous integration systems, and other tools that you have to work with on a current project.

For the “I” of a Senior specialist, according to Aleksey, you need to deepen your expertise in methodologies (such as functional programming), architectures (for example, micro-services), the fundamentals of object-oriented programming or testing — everything you use every day. And then, experience the trends and go beyond your typical skill set.

Adel Salakh also recommends learning functional programming: “It’s already trendy, and I expect it to grow even more.” In Adel’s opinion, there are a couple of technologies that might be game changers in the upcoming years:

  • On the web, one very promising technology is WebAssembly. It might overthrow the hegemony of JavaScript on the client side and might induce an even bigger migration of applications from native code to the browser.
  • In system level/back-end programming, Rust is very ambitious and innovative and is gaining a lot of traction. In the future, it can be a good choice for writing micro-services and web servers, as well as compete in these areas with GoLang or Node.

Company-side of T formation

Companies can nurture the growth of T’s by involving specialists from different fields to work on one task, allowing employees to use the 80/20 rule (the Pareto Principle) etc. Beetroot regularly holds lectures for teams and provides a bonus for education. Furthermore, Beetroot also maintains and updates a knowledge-sharing base for internal use.

Nata Mylostna’s team plays Advent of Code: this is a collection of puzzles to practice a variety of skill sets and skill levels that can be solved using any of the programming languages. They practice speed, problem-solving and challenge each other. Nata’s team tracks the results and participants get rewards for resolved tasks.

The key to becoming a real T is to move away from being a narrowly focused specialist and to widen your experience.

“Large western companies (and sometimes startups too) are often looking not for a Java specialist, but also for a good Senior-developer,” Aleksey Bobyr adds. “Real pro is capable of mastering any technology under a project request.”

So the plan is:

  • expand your expertise into areas you are less comfortable in;
  • possess deep skills in one area (or in a few areas at a time);
  • practice new tools, methodologies, architectures and programming languages;
  • keep an eye on the latest trends in your industry;
  • as a result, solve unsolved tasks (and maybe wear a long red cloak, as you are real IT-superhero).

Vacation or Work-ation: find your balance during holidays

Sunny beach, cocktail with a straw and … your urgent work tasks. This trio coexists peacefully only on stock photography. Right before the holidays hit, we want to share a piece of advice from our psychologists and colleagues: how to accomplish a smooth exit and reentry on work after a long vacation. No stress and grumbling.

Before you leave

Make a list

This will help you prioritize. There will definitely be three “somethings” in this list:

  • something to be done after the return;
  • something that to delegate;
  • something to fulfill before you go.

Start working on the last two points in advance. That’s your only chance to spend the day before the flight collecting swimsuits and inflatable flamingos, rather than panicking in front of the computer.

Anna Dobrovolskaya, Digital Marketing Manager at Beetroot, says: “Delegating my work was a big challenge for me. I thought no one would deal with it as good as I did. So going on a vacation was the same as being reckless.” However, there is always somebody who can help you out. Just maybe you need to delegate different tasks on different teammates?

Notify your team

“I’m gonna spend next week vacationing!” Saying that on a coffee break is not how you should announce your impending absence to your colleagues. Include your vacation in the team’s calendar at least a month ahead, and then set a reminder for team members a week before you leave. Most likely, your message will be completely forgotten and someone will be caught by surprise with your absence in the office. Therefore, remind them of it as often as possible.

Find vacation and work balance

Set your devices to “stunned”, or at least “out of office” mode

Another way to remind somebody you are on vacation is to create an automatic reply to messaging and voicemail. Mention the date when you will be available again. On addition to that, let your colleagues know who they can turn to while you’re offline or how they can reach you. Just in case of emergency.

Medical psychologist and Full-Stack HR consultant for Beetroot Volodymyr Vovk recommends to take a small neat notebook with you and write down some bright ideas about work improvement. “We believe”, he says, “that when we do not force our brain to work, and it can regulate mental activity, and the chance to come up with really good ideas or finding brilliant insights grows significantly.” So don’t push yourself to rest if your brain wants to work.

Put gadgets aside

To reboot your mind and body, you need to take a vacation without gadgets. Well, or at least stop scrolling the newsfeed and turn off the Internet: “I spent 10 days without a laptop, and even a smartphone!” Anna says. “Already on the third day, I even stopped thinking how things are going at work. I rewarded myself with some time off and enjoyed having a vacation with my family. Of course, after returning, some tasks were red-hot, but nothing I couldn’t solve really.”

“To make a vacation without gadgets work, everyone in the office needs to be prepared not having you online.” says Volodymyr Vovk. “Warning your colleagues also will help you realize the decision to be totally disconnected and get rid of feeling guilty for leaving your colleagues. Even for a short time.”

After the vacation

Have a buffer day

It’s clear why you want to lengthen the vacation for a day or two. But having an extra day at home before coming back to office will give you the space to get back to normal with minimal pressure.

Anna Dobrovolskaya decided that her first working day after vacation would be Friday: “It allows you to deal with all incoming messages, find out about updates on the project and make a plan for the next week that will begin without stress and panic.”

Come to the office a bit earlier

Try to go to bed early and come to the office an hour before you usually do. Think about it: no heavy traffic, some free time to clean the workplace, relax, drink your morning coffee and set a plan for your first working day. Sure, you still can be blue for no longer being at Sri Lanka. But some extra time will help you find a positive vibe and prepare yourself to work.

vacation and work balance

Do not overload yourself right away

The best option is to have no important meetings on the first day. Volodymyr Vovk advises to ask colleagues that helped you out during the vacation for updates. Please, do not try to manage everything that you missed in a last week or two. If the Apocalypse did happen while you were unavailable, calm down and determine actually urgent tasks. Often some business needs are not as important as they pretend to be.

Discover time management techniques

It is unlikely you will be 100% productive in the first 2-3 days after your vacation. Take it easy: you need a little more time to deal with the post-holiday blues and maintain your work life balance.

You can try the POMODORO technique or set the usual timer for 20-30 minutes: this is the amount of time you continuously work on solving one task. No chats, no other tasks or coffee breaks. Concentrate only for 20 minutes. Then take a 10-minute break and start again your 20 minutes of productivity.

A few sessions like this will help you focus and set the pace for your first day at work.

If even after all we’ve told you the only thing you can do at work is check whether it’s time to go home, do not map yourself. Let the body still have a little rest for one more day or so. But if this apathetically inactive mood drags on, read this article: “How to beat procrastination?“. We know how to deal with laziness, apathy and fatigue at work! 🙂

Do’s and Don’ts of entry-level CVs

When in the middle of radical career shift, people usually get frustrated about how to tell a prospective employer that they have little or no experience. The same thing happens when looking for a first-time job. We asked our recruiters about the most common mistakes of entry-level CVs to help you avoid them. Use this article to fix your CV or make it good-looking from scratch!

Our recruiters pointed to a set of common errors, including:

Click on the links above to go straight to the most interesting section of this article.


The common mistake is to write your life story instead of writing a CV. Do not confuse CV with an autobiographical essay (like the one you’ve done at school) – these two styles of self-presentation are for different purposes.

Do not overload your CV with information: the recruiter is looking for candidates with specific skill sets and goals. Highlight these qualities and prove you’re the right person for the job. The structure will help you do it even better.

Classic CV usually consists of seven sections (try to fit this information into one sheet of paper):

  • Name and Surname
    city of residence
  • 2-3 lines about your key skills, points of interest within the project and motivation to determine your readiness for this job.
  • Skillset
  • Experience
  • Education
  • Hobbies (if relevant)
  • Contact information

You can compile personal data for a CV using one of Canva’s templates or other web-resources: it will help keep the info organized, good-looking and easy-to-read.

File format

Yes, in the XXI century you still can use a regular text editor for writing your CV, but really why would you? Formatting sometimes crashes and turns your resume into chaos. If you still want to work in a text file save it as .pdf after you finish. Please, forget about PowerPoint presentations. There are better ways to show your design skills. If you do programming too (or someone can give you a hand with that), stand out from other candidates by creating a presentational web page.

Just don’t forget to add a “Download my CV” button somewhere – the recruiter will thank you for that.

The filename is another important detail. “Junior-designer Ivan Popov CV”, “Ira Kruchko Ruby CV” – writing your full name, the position you want to have or your core skill will help you to be identified among the dozens of files named “2.txt”, “cv.pdf”, or “resume.docx”.

The clichés

Imagine how many “communicable”, “stress-resistant” and “responsible” candidates the recruiter sees every day? These clichés are a total waste unless you’ll support the statements with specific data. We mean you can mention “I’m attentive and pedantic” but if double spaces, autocorrect fails, extra commas will pop up in your CV here and there, it’s going to be a fiasco.

Instead of describing yourself with clichés tell about your experience. If you want to point out your reliability and conscientious, don’t say “I am a responsible person”, let the facts tell more: maybe you were a class president, volunteer or some kind of event-manager?

The same thing goes when talking about your skills. Compare “I was taught Javascript on courses”, “I’ve been learning WordPress” and “…my graduation project is written in Javascript (link)”. Better tell the recruiter where you’ve already applied your knowledge.


Look through the required skills. If there is anything on that list you are not happy about, don’t pretend to be a 100% match for the job. Tell the truth, or do not mention skills you do not have at all. There is no point in exaggeration: you can’t even imagine how simple it is to catch the candidate on blabbing. Bad English is the classic case. “One candidate wrote that he has advanced English,” says HR-contractor at Beetroot Halyna Vorona. “But at the interview, he refused to speak it without preparation, which is suspicious, you know.” Another one rated his English at 4 out of 5 stars, but it turned out he was too shy and insecure to mention his excellent TOEFL!

HR specialist Natasha Dmytrenko believes that if there is a 50-60% relevance to the requirements, you can try to submit for the vacancy: “Send the CV even before you are totally ready for the job, otherwise you can lose time on waiting for the result. Do not be too critical to yourself – employers don’t expect professionalism from an entry-level candidate.”

entry-level CV

Creativity overdose

If you can think outside the box, make a good design or smashingly code, let the examples of your work speak for themselves. Natalia Dmitrenko advises: “It is better not to go from one extreme to another: candidates sometimes write that they are ready to work for food, or “your company is so lucky to have me!” – and it pushes me away.”

If you want to express yourself – add a cover letter to the resume. This is an informal text, a short story about your motivation for working in this company or project. Take up to 200-300 words to tell smth relevant and good-to-know about you. Keep a neutral tone of voice and not get too comfortable talking about yourself: recruiter is not your best fella (at least for now) and familiarity is not a good choice for making the first impression.


Candidates are not required to attach photos from ID’s (sometimes it’s better not to show them to anybody at all, agreed?). However, if there is an option to add a photo of you to the resume, be wise. Natalia received quite strange pictures with the CV: “One candidate was in a T-shirt on a photo, with his hands raised above his head and crowded train on the background. Another time I get a photo of a girl, she’s bent over the keyboard, so you see only the top of her head, with the signature: “This is how I look almost always because I’m a workaholic!”. Catchy idea but not a 100% good decision.”


If you have no commercial experience in a new specialty (didn’t have previous official employment in IT), it does not mean that you have nothing to tell. Inna Chernova, an HR consultant at Beetroot Academy, advises never to say: “I do not have a CV because I have not worked anywhere yet.”

Maybe you were attending conferences, studying at art school, taking part in FLEX or AIESEC, were volunteering somewhere? If just graduated from IT courses, show your graduation project – that’s already something!

Another mistake is to write all your jobs and activities in a row. Even if they do not relate to IT. Recall two or three recent or most revealing of them: where you worked for the longest, what position did you had, what duties performed, what results achieved.

Here’s a good example from HR Consultant (Full-Stack), Beetroot, Volodymyr Vovk:

Software Engineer at ***. August 2016 – present. Technologies research and developing new functionality.

Achievements: designed and developed completed microservice, implemented a set of build scripts, made infrastructure wrappers for 3AWS services.

Environment: Scala, Finagle, AWS, Guice, Git, Akka, Docker, Flatbuffers, SBT, CircleCIand IntelliJ IDEA.

Replace “Software Engineer” with “accountant”, “manager”, “decorator” – or what you’ve been doing before – and describe your experience and competencies using this scheme.

If your hobbies are somehow related to the vacancy, give a few words about them. Better to be brief about embroidery, singing karaoke, collecting postcards and other irrelevant to your new occupation activities.

entry-level CV

Dialogue with the recruiter

Even if you wrote an amazingly brilliant CV, it’s still unlikely that someone will send you a contract for signing right away. The whole employment process takes about a month: ~ 2 weeks for reviewing the resume, then the interview with the recruiter, fulfilling the test task, a few more technical or client interviews. The point is do not expect that the recruiter will answer you immediately.

The rule of good manners in HR is to answer all the CVs. Even if the candidate does not meet the requirements and must get a negative response. Only after two weeks, if your mail is still empty, tactfully recap: ask if they did get your CV and read it. It’s better to send the request in the same thread.

If you received a negative response, you might still benefit from it: ask the recruiter the reason for the refusal and what skills should you improve to get the job next time. It’s totally OK, as well as asking HR-manager to contact you when a new vacancy opens.


Juniors have a sneaky tendency to send the same CV to all the companies, thinking that this increases their chances of getting the job! Well, it’s not the wisest thing to do: a recruiter can determine if the person is motivated to work on this particular project, or just looking for any kind of work anywhere. Even if you have to pay the bills for the apartment, spamming a template-like CV to every IT company out there is not an option. Do not be too lazy to write a new CV for each vacancy that interests you (or re-write yours considering project characteristics). At least you can try to find a temporary work so you’d have resources for waiting for your dream job to come up.

To sum up

Don’t write a CV in a rush. Give yourself some time: sit in a quiet place and make a plan, structure the resume today, add some extra information tomorrow and give the text to someone the day after. When you’re working on smth for a long time you can miss obvious mistakes, it’s easier to find and correct them just asking another person to look through the text.

Remember, when a company opens an entry-level vacancy, they do not expect you to be an extraordinary professional. Most likely, they are looking for a flexible candidate with a good basis in technologies and good soft-skills to become such a pro inside the team or particular project. Look through the requirements: if you have at least 60% of the core skill set, apply! If not, look through the list once again: it is a right vector for self-development and future learning!

How to avoid miscommunication: 6 tips for remote teams

There is one thing that can ruin even a top-notch distributed team: communication. The way people talk to each other can either get them to the highest heights or cast them down into the abyss of failure.

We talked to a variety of specialists — managers, team-leads, developers — about the difficulties of remote communication and how to solve them. These are six of our main takeaways.

Get together in the very beginning

Working in distributed teams can be challenging sometimes because you can’t meet your peers on a daily basis and share the news over coffee. This is the reason why it’s so important to start out a project with getting together as a whole team. We mean like meeting in real life. Offline, to be more specific. A few days of collective work will help you understand your future colleagues way better. Natalia Milostna, QA lead at Beetroot, has a lot of experience working in distributed teams, and says that those collective brainstorming sessions can be the most productive time of your work.

Write understandable texts

You’re not one of those guys, right? Those, who write “hey” in chats and fall silent. “Hey, I need your help with one thing” is also bad. But the ultimate winner is:


need your help

with one thong



r u here


In order to make your communication understandable use the journalistic formula of “5Ws”, where “W” stands for Who, What, When, Where, Why. Answering these five questions will help you build clear communication.

But it doesn’t mean that you should speak like a robot all the time. For more informal chats — like, cheap flights to Sri-Lanka or Friday nights out — use a separate channel. Here, at Beetroot, we call it “random” and it’s full of utterly meaningless but fun texts.

Another good thing to have is a document, which describes responsibilities within a team. It might be challenging to create and maintain it, but at the end of the day, it can be a good tool to cut down unnecessary communication.

Talk to each other regularly and meaningfully

It sounds easy peasy lemon squeezy: just talk to each other and your distributed team will work efficiently. But this very principle can be turn into the most boring and inefficient activity on Earth. For instance, when you’re holding one of those meetings that should be an email.

If you want to avoid collective eye-rolls, prepare an agenda before a video call and send it to every member of the team. Trofim Prodayvoda, a Back-End developer with more than 10 years of experience on distributed teams, says that communication should always have a concrete reason. If there is no reason to have a meeting, just cancel it.

Spice up your messages with emojis 🙂

Australian specialists in body language and non-verbal communication, Allan and Barbara Pease, claim that we transmit only 7% of information through words. Another 38% is transmitted via a tone of voice and intonation, leaving 55% for posture, gestures and facial expressions. It means that reading an email people miss more than 90% of the initial meaning of a message.

You can fix this by making your messages more emotional. Add emojis, GIFs or more vivid words. But never ever write like this: “We’re screwed!!!!!!!!!!!” or “I don’t know……maybe ask me in a month, can you????????”.

When working on the same project people tend to develop their own slang. Which is good because it makes communication easier. But don’t use this slang when talking to someone outside of your group. They’lli barely understand it if you say “we’ve been rubberducking all day long”. As a sanity check-point, imagine saying these things to your grandma. Would she understand what “rubberducking” is?

Always have a plan B

Living in the era of technologies is a bliss but things like malfunctioning Skype, poor Wi-Fi or broken headphones still happen sometimes. Make sure that you have proper equipment: good mics, cameras and other devices. Also, you should always have a plan B in case something goes wrong. For example, get ready to jump to Hangouts if Skype doesn’t respond.

Apart from tech barriers, think of language barriers as well. Sometimes it can be hard to understand what people mean, even if you speak the same language. If you missed something from a conversation, don’t hesitate to ask again. It’s better to ask dumb questions that to write dumb code.

Make sure that everything is clear

Often teams end the conversation, asking “is everything clear?” It’s a typical phrase but it’s also useless. Picture this: you’re finishing an hour and a half call:

— “Is everything clear, guys?”

— “Totally!” — reply people who have just woken up from a meeting-caused coma.

Then they go back to their computers, start doing things wrong, ask clarifying questions and end up with doing much more work than they should. So, when having a meeting, you should better ask everyone to share their ideas on how things should be done.

So, is everything clear? 🙂