Recruiting for technical roles can often involve navigating through various terms and definitions, which can be overwhelming. To help simplify the process, we have provided some high-level guidelines for different types of technical roles that you can find on our job board:

1. Full stack engineer - Look for keywords and programming languages that are required. Candidates should have these skills heavily listed on their CV and experiences in order to be a good match.

2. Test analyst (or Quality Assurance Engineer, or Software Development Engineer in Test (SDET))

   1. Role: The purpose of this role is to find bugs and automate much of the testing that needs to be done.
   2. Some of the classic languages and tools that a candidate should be familiar with include:
      1. Selenium for web application automation.
      2. Java, Python, and C# as primary programming languages.
      3. Cypress for front-end web testing.

3. DevOps engineer (or Site Reliability Engineer)

   1. Role: DevOps engineers help set up the pipelines so that other engineers can build the customer-facing parts.
   2. A candidate should typically have experience with CI/CD (Continuous Integration/Continuous Deployment) listed on their CV.
   3. They should also have experience working with one of the major cloud platforms, such as GCP, AWS, or Azure.

4. Delivery lead

   1. Role: A Delivery Lead is similar to a Product Manager but with a more technical focus. They work closely with the engineering team to ensure that projects are completed on time and within budget. The role is more implementation-focused, involving working closely with Engineers to get things done, rather than coming up with lots of new ideas, as a Product Manager typically would.

What makes a technical CV stand out

In the tech industry, reviewing CVs requires a slightly different approach, so it's important for IT recruiters to understand how to evaluate them in order to select the right candidates.

• Given the high demand for IT professionals, many of them may not actively seek job opportunities and may not put significant effort into perfecting their CVs. A CV that is not perfect or detailed may not necessarily mean that the candidate is unqualified. If the CV includes information about their experience, technology stack, and contact details, it is generally a good start.
• When reviewing a developer's CV, it is best to begin with their technology stack and assess how well their hard skills align with the position. Take note of their previous projects and the technologies they worked with.
• Pay attention to the experience of a specialist. It's important that there are no gaps in the candidate's professional biography.
• Also look for the "contact details" column - it helps if a candidate not only shares email but also the candidate's phone number in order to contact a specialist in Telegram. Studies show that now this method of communication with specialists is the most suitable for all parties.