[AlexDanger]

>Make multiple resumes, each with a focus on one thing. Use the resume that's best for the job. I recently saw somebody who must have had 20 different resumes to match the jobs they were applying for. It worked.

I'd like to second this methodology. It is a very effective approach. I've worked across multiple specialties within technology and I always tailor my CV to the job I am applying for. I highlight the most relevant experience and skills required and remove (or summarize) experience that is not relevant to the position.

Matching your CV to the job can be as simple as updating it to use the same keywords that you see on the job advert. It sounds trivial but many recruiters will filter job applications with a keyword search. If they dont see the exact keywords they are expecting, your CV will be thrown away.

Good luck!

[mettamage]

Question: how do you deal with gaps in your resume?

Let's suppose you were a machine learning engineer for 2 years, a web developer for another 2 and a product owner for 3 years.

I presume that some experiences would almost make it seem that you're not dedicated to the role you're applying for if you leave them in. So you have to leave them out.

How do you deal with that?

[redshirtrob]

Be honest. I make a habit of having gaps in my resume. I like to take some time off between jobs. It's a luxury, but if you can swing it, it will do a lot to recharge you and get you ready for your next role.

If the gap is fairly large (say over six months), be prepared to discuss what you were up to during that time. Hopefully it's something interesting, but it doesn't have to be something related to your career path.

To your actual question: I see no issue with bouncing between roles. If anything it shows flexibility and a diverse interest. You'll fit right in at small to medium places where folks frequently wear many hats. Plat it as a strength.

[ldjb]

That's an interesting question and something that hadn't really occurred to me.

Personally, over the past few years I've been a developer, a product owner and now a product manager.

But if I were to apply for a new developer role, would I leave out my current product manager role from my CV? Absolutely not!

It's generally considered a bad idea to have gaps in your CV. And actually having worked various roles can actually be to your advantage. There are transferable skills you would have gained as a product owner that you can apply to a developer role. In fact, very few developers will have the skills required to be a product owner, so employers should look favourably upon your skillset.

Case in point: my experience as a developer has put me at quite an advantage in the product management field. Due to my technical knowledge/experience, I can understand how systems work better than most other product managers, and I'm better placed to know what the development team needs of me.

So I would say, don't leave gaps in your CV, include all the really good experience you have, even if it is varied, and use that to your advantage to show how these experiences will help you in the role you're applying for.

[klondike_klive]

How about if I was a stay-at-home dad for a year? I haven't included that in my resume - I figured if I were asked I have no problem speaking about it, I'm actually super proud of it, it just doesn't strike me as something I should put in my list of experience.

[killtimeatwork]

Employers worry about gaps in CV because of two possible scenarios:

- you were actively looking, but were unable to find a job during that whole time - for them it's social proof that you suck

- you're actually picky and "high maintenance"

[DuckBoy]

"you were actively looking, but were unable to find a job during that whole time - for them it's social proof that you suck"

Gee... I would hope I don't suck. Most places I apply to ghost me when they find out I'm deaf! They don't want to "deal with accommodations".

[ldjb]

I think that's a perfectly reasonable reason for you to have a gap in your career, and prospective employers should be understanding of that.

It is something you should be prepared to explain at an interview, but I don't think it would cause any problem.

You're right that it doesn't really count as experience. Employers won't necessarily mind a one year gap on your CV, but if you do find it difficult to get to the interview stage, it could help to add a short note to your CV explaining the gap. But I'd hope that wouldn't be necessary.

[blackrock]

How’s the compensation (pay and/or stock options) for your product manager role now, as compared to your development roles of past?

[fecak]

What you are referring to aren't what we'd traditionally call gaps. Resume gaps are usually periods of unemployment. What you're referring to seems to be some career inconsistency.

I write resumes all the time for people who have bounced between different types of roles. In those cases, having a couple resumes makes sense. For the description you have in your comment, if this person is applying for ML roles, we provide more detail and emphasize that role. If they were applying for a product owner job, you emphasize that aspect and those skills.

As I mentioned in another comment, you can also use a summary to define yourself. If you're applying for product owner jobs, you define yourself as a product owner with skills in web dev and ML. If you're applying for a web dev job, you define yourself as a web dev with skills in ML and product.

[T-zex]

Why would you make such an absurd presumption? Life is life and there are lots of circumstances pushing you to make tough choices. Always being able to stick to your dream job or career path is not an option for most people.

[mettamage]

It's my experience when applying for a job that people are very judgmental. I've learned to take that judgmental frame, if I wouldn't then I would never be invited for an interview.

The only places that don't have these judgmental frames are a subset of startups.

Just my experience, YMMV.

[AlexDanger]

fecak's reply is the best answer. In particular this quote:

>As I mentioned in another comment, you can also use a summary to define yourself. If you're applying for product owner jobs, you define yourself as a product owner with skills in web dev and ML. If you're applying for a web dev job, you define yourself as a web dev with skills in ML and product.

This is great advice. Make sure you still include all the roles in your CV to illustrate a consistent period of employment. Just highlight the aspects of each role that are most relevant to the position you are applying for. If a previous role is barely relevant, just summarize the experience in a couple of sentences.

The point is to make most of your CV relevant to the role. Dont make the employer hunt through your CV for relevant experience. Most people will make a snap judgement within a minute or two of scanning your CV. Make it easy for them.

I also think a summary is very important. Sum up your best points with some dot points at the top of your CV.

[de_nied]

This seems extremely helpful. 20 resumes, as GP mentioned, should be an excellent source. I've always seen multiple cover letters, and maybe 2-3 resumes, but never 20. While 20 is fairly high, I think it's also the right amount in being able to have a resume for almost every position that is "just right."