The relocation process is often stressful and fraught with uncertainty. If you’re considering relocation as an option, here are a few things you should pay attention to beforehand so you can settle into your new country with minimal stress.

The post What You Should Know About The Job Relocation Process first appeared on Relocate.me.

Whether you are a Software Engineer, an Android Developer, or a QA Tester, there are always plenty of exciting projects to join that will help you grow professionally.

The interview process — central to securing these opportunities — depends on the level and type of position, of course, and varies from company to company. However, there are a few factors all employers pay attention to when interviewing that we will cover below.

The post How To Successfully Pass An Interview At A Software Product Company? first appeared on Relocate.me.

With more than 30M companies and 20M open jobs listed on LinkedIn, it’s no wonder that 90% of recruiters use it for hiring purposes. Obviously, those who are recruiting for tech roles aren’t an exception.

So, having a powerful LinkedIn profile is more than important for finding a decent job, both with relocation and not. Polish yours up today with this quick guide.

Step 1. Headline and summary

Apart from a profile picture, these will be the first things every recruiter sees. 

Start with the headline. Use the following formula:

Position+Company | Your primary skills (keywords) | Zing (something that differs you from other candidates)

✓ Software Developer at Amazon | NodeJS, React, Ruby, Rails, AWS | Agile Evangelist, Public Speaker

✗ Junior Software Developer at Amazon

Note: If you’re a junior professional aiming to get a mid-level position, better omit the ‘Junior’ part, as well as the words like ‘aspiring’.

Polish the summary. It shouldn’t be too short (consider writing at least 40 words), but don’t overdo it with the length. Avoid buzzwords like ‘team player’, ‘familiar with’, ‘thought leader’, etc. Include relevant keywords. Since you’re looking for a job with relocation, don’t forget to add the words ‘relocate’ or ‘relocation’. For more tips and expert advice, check out this article. 

Opposite strategy. Recruiters strongly rely on keywords and boolean search when looking for prospects. For example, here is one of the boolean search strings for finding a Python developer: (programmer OR developer) AND python AND (mysql OR postgresql) AND (django OR flask) AND (chef OR puppet OR sentry). 

So, if you want to be reached by the most determined recruiters only, better omit the primary keywords from the headline and summary of your profile. If you’re a Java developer, don’t use the word ‘Java’ — mention Spring, Hibernate, and other relevant technologies instead.

Additional resources. If you have a GitHub/Behance/Dribble/whatever profile you’re proud of, add it as a custom website under your contact info.

Bonus tip: Never state that you need visa sponsorship in the headline and/or summary of your profile. This won’t increase your odds of finding and getting a tech job offering relocation.

Step 2. Filling other sections

Generally speaking, all parts of your profile should be filled and contain the right keywords. That is especially true for the Experience, Education, and Skills sections.

Experience. Simply stating the company and your position is not enough. Describe what you achieved in each position, not your tasks or duties. Do this in a bulleted form. Use active verbs (‘reduced’, ‘developed’, ‘achieved’, etc.) and prove your accomplishments with numbers when it’s possible.

For example:

• Designed, built, and launched to the Google Play Store XYZ, a React Native-based Android app for free textbook rental.
• Achieved over 5,000 downloads and 300+ positive reviews in less than six months.

Courses and certifications. If you’ve completed any relevant ones, take the time to mention them, especially if you’re only making the first steps towards an IT career. It’s one of the ways to show potential employers that you’re committed to continuously learning and growing your skillset. 

Step 3. Final touches (settings)

Let recruiters know that you’re up for a new challenge. Click on the ‘Career interests’ section of your profile, and choose the appropriate status. (‘Actively looking’ might be the best choice.)

Turn on the visibility of your profile. Go to ‘Me’ > ‘Settings&Privacy’ > ‘Edit your public profile’, and switch on ‘Show’ for all the components.

Profile URL. Personalize your profile URL — if available, your name+surname is the perfect option. 

✓ https://www.linkedin.com/in/john-smith

✗ https://www.linkedin.com/in/john-smith-468rff715f48

Bonus tip: Try switching your location to one of your potential destinations. That will make local recruiters pay attention to you. Moreover, you can combine tourism with a job search. If you’re visiting one of your possible destinations, don’t waste a chance to go on a couple of interviews.

And the last but not the least, if you’re in search of work abroad, make sure your profile is completed in English. 

Voila! Your profile is now ready for the job search.

The post How to Improve Your (Tech) LinkedIn Profile Before Relocation first appeared on Relocate.me.

Even if you’ve been dreaming about your new job, (with relocation or not), for months, and have a reliable agency or person to help you, it’s still a crucial affair. To choose the right location, company, and position, you need to possess as much information as you can. That’s why I always tell candidates: Don’t be shy to ask questions while talking to recruiters and/or hiring managers. To help you concentrate on the most important things, we’ve gathered 25 questions you need to ask your future employer before making that final move.

As here at Relocate.me we help tech specialists to find decent jobs overseas, some of these questions refer to job relocation. BTW, if you’re looking for tech jobs with relocation, browse them here.

Technical questions

1) What technologies (languages, frameworks, libraries) are used on the project?

2) Is the app monolithic or microservice? What patterns are implemented?

3) Does the team employ CI and CD practices? Are container technologies used in the project?

4) Is the code reviewed by other team members before deployment?

5) Who is responsible for maintaining the project’s documentation? How often is it updated?

9) How is the code tested? Which amount of code is now covered by tests? What bug trackers are used?

10) If the server failover happens in the middle of the night, who will be responsible for fixing the issue?

Apart from these, find out as much as you can about the operating systems, databases, APIs, build tools, IDEs, version control systems, etc. You need to know exactly what you’re going to work with. After all, your interest in a particular project directly depends on the tech stack, right?

The project, the team, and the company culture

11) What is the ratio of development and maintenance?

12) What methodology is used — Kanban, Scrum, Agile, Waterfall?

13) How many people does the team include?

14) To whom will I report? Will I be reported to?

15) Will I have any career advancement opportunities? Do you have a job rotation program?

16) Do you organize any hackathons or workshops? Do you pay for conferences and courses outside the company?

17) Will I have a mentor? Will I have to mentor somebody else?

18) How flexible is the schedule? Is it possible to work from home? How many (paid) days off are allowed?

19) Will I have to go on business trips? If so, how often, and what will be my destinations?

20) Do you hold any corporate events? If yes, how often do they take place?

21) What will my relocation package include?

It’s important for any person to work in a friendly environment with an appropriate schedule and growth opportunities. (For expats, it’s even more important.) Make sure the company you’re going to move to is exactly such an environment.

The hiring process

22) How many stages will the interview process include? How will it proceed?

23) What does a test task look like?  Will there be any deadlines for performing the test task?

The hiring process may vary from company to company, from project to project, and even from candidate to candidate. Nobody will tell you everything in details, but it’s important for you to know at least the basics to be timed perfectly.

Other important questions

24) What is the salary range for this job? How flexible is the salary, and how often will it be reviewed?**

25) Can I talk to some of the team members personally?

The recruiter’s answer and reaction to the 25th question will show you whether all they’ve told you about the company was the truth

**Don’t get ahead of yourself — better wait for the hiring manager to bring up the salary discussion.

Changing a job and relocation is not an easy process, and it would be a pity to spend time and effort on the wrong company and position. Save this checklist, and ask these questions during every call to identify your perfect employer.

If you have other interesting questions to ask, please write them in the comments below

The post Developer’s Checklist: 25 Questions To Ask Your Future Employer (Before Relocation) first appeared on Relocate.me.

Résumé trends change very fast, especially in tech. In spite of that, there are some elements that remain relevant to this day.

Since the launch of the Relocate.me job board, over 3,000 résumés have been received and forwarded to European technology companies. Below are the conclusions we came to based on our experience.

Résumé Size

Your résumé should be one page (unless it absolutely needs to be longer). Why? Recruiters and hiring managers usually spend only 10 seconds viewing any given résumé. Thus, it’s highly recommended to list all your professional skills right on the first lines of your CV to capture their attention.

Résumé File Format

Don’t let the wrong file format be your CV’s downfall. ‘Word is not the king, it was in 2003,’ says Bernardo Sulzbach. It should be a PDF by default unless you’re asked about another one, e.g., a DOC file or some other format.

No CV Titles, Use Your Name Instead

There is no silver bullet for an effective CV title. Just try to avoid any titles at all. Recruiters are skilled at learning what you’re all about by reading the content in your résumé. By including a specific title, you run the risk of throwing them off and reducing your chances of being offered an alternate role.

Don’t Look For Easy Ways

The ‘Export to PDF’ option on LinkedIn isn’t the same as crafting a good CV – in fact, these are two entirely different things. Even if your LinkedIn profile contains enough info about you, sending it as a PDF will hardly grab recruiters’ attention. Most of the companies you’ll apply to actively check LinkedIn to see reviews on a certain candidate, find common contacts, etc. It’s still a good idea to add a link to your LinkedIn profile to the cover letter, but don’t rely on it as your CV.

‘Sweets’

A good CV should have something to differentiate it from a boring wall of plain text. Try employing a good sense of humor, self deprecation, or some interesting numbers and facts: e.g., over 3M lines of code were covered with unit tests, 5 reasons why employers should hire YOU, etc. These simple things will make your CV stand out among the rest.

Where Is The Passion?

It’s no secret that every company wants passionate and enthusiastic employees who live for the job. Hence, it’s advisable to show this ‘passion’ in your CV:

• Add links to your GitHub/Bitbucket/StackOverflow profile(s) (after making sure their content is worth it, of course).
• Talk about your participation in various open source projects.
• Add certificates, training courses on Coursera, etc.
• Include a reference to your technical blog.
• Let them know if you ever took part in programming competitions.
• Have you ever organized any meetings/workshops and thematic conferences? It’s also worth noting.

Achievements

It’s always a good idea to talk about the tasks that you were performing while working on a project in the perfect tense (developed, implemented, optimized, etc.). In doing so, you’ll enable an employer to measure your worth in concrete terms. Plus, very few candidates put their achievements on the résumés, so it’ll help you stand out. I’d suggest that you use the following expressions:

• Accomplished X by implementing Y which led to Z…
• During my work on this game, I solved several interesting problems…
• The most challenging tasks were…

Describing Your Work Projects

There’s no need to describe all your projects. Pick two or three and provide a good overview. Very often, screening CVs from our Relocate.me tech job board, I come across project descriptions that go like this:

Since 2009: Huffingtonpost.com, Software Developer

Brevity is key, indeed. However, The Huffington Post is the largest news portal in the USA and one of the TOP100 most visited websites in the world. The company was acquired by AOL which is a huge corporation as well. These are the facts that I would definitely mention in the CV.

When describing a project, you should choose 2-3 sentences that would best tell about the tasks you completed. Give a few links to the website/App Store/Play Market (if any) along with other interesting facts like:

• The number of visits per month.
• Startup Of The Year Awards.
• Top 5 in downloads on the App Store during the last 3 months.
• The application is a market leader in X category.
• And so on and so forth.

Personal Projects

To write a good CV, you should talk briefly about the projects you may have done ‘for fun’ and all those interesting things you were doing whilst working on the project along with its social use (even banal enrichment of an owner can be presented in a favorable way that will enhance your résumé).

Summary

You have two choices: write a good summary or write no summary at all. As it typically goes in the beginning of your CV, make the opening lines count. Write a few sentences about your job activity and prove your professionalism. It’s not a simple task (especially when you’re limited by the number of characters). But, if you manage to write a catchy opener, you’ll get +5 to your karma.

Here’s an example of a poor résumé summary:

I am a 24-year-old senior developer with 2 years commercial experience in Android development and about 4 years in Java. A focused, goal-oriented, fast learning, responsible team player. Strong understanding of programming methodologies, able to develop and integrate Android apps using different modern frameworks and approaches.

Let’s take that same information and craft a much better summary:

I’m a passionate and agile-minded software engineer who is scrupulous about the details. Having started coding in Java during my 2nd course at University and learning ‘Thinking in Java’ by Bruce Eckel almost by heart, I’ve been totally committed to Android development for the past 2 years. I am a big fan of low-level things like memory management, multithreading, etc. and believe that TDD will change the world for the better.

‘80 level’ summary is when you’re capable of describing yourself with a single sentence, so-called ‘self-identification’. Here’s an example:

CTO, grown from LAMP developer with huge passion in UX/product management.

Listing Your Technological Proficiency

This is where most tech applicants don’t show restraint. They commonly list all the technologies they’ve ever worked with, even on a casual basis. Don’t do that. Instead, mention those ones that you feel confident with and demonstrate your superior knowledge. For example, Java (expert), C++ (basic), PHP (proficient), JavaScript (mother tongue). I can assure you, employers won’t judge you on these criteria alone. But, if you overload your CV by listing too much, it’s liable to work against you in the long run.

Don’t write that you’re proficient with Microsoft Office suite or an advanced user of Linux, CorelDRAW, Fortran. Agile, Scrum, and Project Management shouldn’t be listed among your technical skills either. Do you think that the more you use words like ‘Agile’ and ‘Scrum’ in your CV, the better it will be? Sorry, that’s not true. Recruiters perform a ‘quick scan’ of most résumés, and can easily identify the mindset of its author and see whether he/she is truly ‘Agile’.

One final note here: don’t forget to update your résumé every few months as your technology skills change and grow.

Your Work Experience Section

All your projects and professional experience from 3-4 years ago won’t be of interest to your potential employer. Even if you used to work with the required technologies, a lot of time has passed since then. Therefore, if you want to make your CV really good, get rid of outdated facts and talk about those projects that have a true value to your employer.

Trimming The Fat From Your CV

You can eliminate all the tables in your CV and get straight to the point. Don’t use headings that go as follows:

• Main tasks and job responsibilities
• Name of employer
• Dates of employment
• Project type and description
• Used technologies

Instead of writing a telephone number, give your actual number. Instead of including date of birth, use your age. The list goes on, but the general idea is that it’s not worth writing general phrases that pretty much everyone else uses. Don’t describe your hobby in details. A photo is not a must either. For technology companies, your ‘portrait’ on GitHub comes before your photograph, indeed.

Forget about Yahoo!

Don’t give recruiters the impression that you’re stuck in the past. If you are still using Yahoo or Hotmail, it’s time to create a Gmail account, or, alternatively, tie an email to your website.

The Finishing Touches

Remember that there’s no one CV and cover letter that will suit all your needs. Always assess the situation first and modify your CV and cover letter, taking into account the exact company/position you’re applying for and your own desire to work there.

The post For Techies: Raise The Bar For Your CV first appeared on Relocate.me.

You’ve probably all heard of Europass. Having launched the Relocate.me tech job board, our team gets a lot of developer resumes every day, and somehow many think the Europass CV is essential to get hired by European technology companies.

What is the Europass?

The Europass was established by the European Union to assist European citizens to make their skills and qualifications clearly and easily understood throughout Europe with a portfolio of five documents, one of which is a CV.

30 European countries are currently participating in the Europass Initiative.

Despite this, one often hears the Europass CV doesn’t give any benefits to applicants for tech roles. Moreover, its template is ranked even lower than a standard (short and plain) one. On the other hand, lots of software engineers (both in and outside the EU) believe that by using the Europass CV they’re one step closer to landing a job in different European countries.

For you, as a recruiter, the primary questions are what companies your tech candidate has worked for, when and how long, what he/she was doing for each company and which technologies/tools were applied. In this regard, the Europass CV is utterly worthless. Why?

First off, its template is rather generic and faceless. Consequently, many good developers have been overpassed just because their expertise wasn’t expressed in a proper (clear and comparable) way.

Companies like Spotify receive thousands of resumes regularly. And one doesn’t have to do the sums to see how much time on average is spent on screening each one of them. I guess it takes 7–10 seconds per resume and the screening is very brief. So if you want to snag a job at a hot tech company, your CV should ‘strike’ its recruiter immediately. A unique CV template may well give you a few seconds more while the Europass one can take a few seconds off. The key is the ‘content’ of your CV and whether you’re a good match for the team and its product.

Let me stress the following — the Europass CV is not obligatory to get hired by European tech companies. There’s no need to use it, thus. It may be helpful as a simple CV builder, however the internet is now teeming with such things and some of them can be a good alternative to the well-known Europass.

So, why is the Europass CV template NOT the best choice if you want to get tech jobs in Europe?

• The Europass logo in the header takes a decent amount of space on your resume.

• Every single word counts in your resume, so there is no strict need to headline it ‘Curriculum Vitae’. You can simply add ‘CV’ or ‘Resume’ to the title of your document (preferably PDF) and save a bit more space.
• The photo is not required for most of the tech roles. Recruiters can easily source the web and find your photograph if it is needed. By cutting it from your resume, again you can save some space as well as avoid any subjective judgments.
• I cannot fail to mention that there’s neither icon for GitHub, Stack Overflow and other almost must-haves for software engineers nor Dribble/Behance for designers.
• ‘Jobs applied for’ section is not required as well. I’d suggest adding ‘Which company I’m applying for and why’.
• The work experience section could be a little bit better too.

It doesn’t allow you to add enough information about your company and the project you’re working on. You can only shortly describe what type of problem your software/app is solving and a few details about the project (e.g. some numbers why you can call it a ‘high-traffic’ website). There is no space to mention your main technology stack.

• There’s no need to mention Business or Information Technology (IT) sector as it’s obvious for software developers.
• The ‘Personal skills’ section of your CV often can take at least half of A4 page. However, there is no real added value for describing you as a team-player or the most pedantic person in a team in terms of the quality of code.

• You don’t have to put your mother tongue, either. The most progressive tech companies are currently checking 2 languages — your English and how good you’re dealing with required programming languages.
• Communication, organization, managerial, and digital competence can be structured in 1–2 sentences. That’s more than enough. And this is also not mandatory to mention at all. You’ll never find ‘bad’ skills in any resume, and the required ones such as a team-player, open-minded, fast-learner will be carefully checked during the interviews.

The Europass CV is not something you necessarily need to use and it can hardly increase your chances of getting a great tech job in Europe. In our next article, we’ll share the best practices and tips from recruiters/hiring managers of European technology companies on how to raise the bar for your resume. 

The post The Europass CV doesn’t work for European tech companies anymore first appeared on Relocate.me.

Relocating to a foreign country is always a cost-intensive process, so, before you start looking for IT jobs abroad and start packing your boxes, it’s beneficial to pay close attention to what your future employer will and won’t offer regarding relocation support.

For international candidates, there is no standard for job relocation assistance, meaning the offers you receive might vary greatly from employer to employer. Some companies hiring employees from overseas can only cover basic expenses, while others can offer potential employees much more advanced relocation services. This is generally dependent on the size and age of the company in question.

Relocate.me is a job board aimed at verifying different relocation packages within the tech industry, which it then categorizes based on whether they are Basic Relocation Packages or Advanced Relocation Packages. 

The post Learning The Difference Between Basic & Advanced Relocation Packages first appeared on Relocate.me.