Quite a long resume.
#I am a developer of 7 years in Toronto. And I need help
snow thicket
Skills, activities, and interests isn’t a good headline.
Condense it to one page.
Limit each job to 3-5 bullets.
I’ll leave that up to you.
turbid tapir
Yeah, pretty long. People tend to spend like 30 seconds on a resume so as much as you can put the best stuff on it, that helps.
More important things towards the top, but mainly if there's something not interesting just cut it
You've been working for a while, but all the points right now seem to me to still be "I built a thing they told me to build". Have you done any stuff with like, running a project for multiple people, or interfacing with stakeholders? Recognizing problems in the team and fixing them?
I'd include those as some of the things you keep as you're trimming down. That's part of what people are expecting you to have learned as you get experience
wise harbor
Pretty much echoing what everyone else has said. A lotta text but I can't easily find where you've provided impact or value for the company. To xiong's point that would make me think whether your lateral moves are due to refusing to take on additional responsibilities beyond designing and implementing code for software. Just my 2 cents though - definitely not anywhere near as experienced as you are.
turbid tapir
To provide an example, https://dropbox.github.io/dbx-career-framework/ic3_software_engineer.html talks about what an IC3 at Dropbox looks like. Your resume right now reads more like an IC1, but folks don't want to hire someone who has been working for a while but with the same level of experience as a new engineer. It seems like you actually are operating at the higher level, but you need to indicate that in the resume, especially if you haven't been getting the titles for it
Not that you need to look exactly like that, unless you're applying to Dropbox. But it gives an idea what sort of things people are expecting from a more senior engineer
Yep, exactly. Because part of what a company is hiring you for is your growth after you're hired
There are a lot of variations on the levelling concept, but that's a good one IMO. I have more resources but I don't think they would be helpful
wise harbor
A potential explanation is just that you've had so many stints - maybe a risk that after interviewing you'll demand such a high salary that interviewing you at all would be a waste of time
turbid tapir
I can't speak to the specific jobs you've applied for because I'm not privy to what's happening internally at them.
A concern I have heard, and one that sometimes caused us to pass on candidates at the job where I was involved in a lot of hiring, is that someone who is shall we say "senior junior" has demonstrated that they aren't going to grow beyond where they're at; a "junior junior" instead has more unknown, so they might grow into a nice senior engineer who stays at your company.
When we had someone like that, the thing that we tried to determine was whether they had had opportunities or not. So for instance, someone with five years of experience does poorly on system design, we see: did they get the opportunity to do any design work at their previous job(s)? If no, then fine, we're ok downlevelling them and giving them an opportunity to do that here, and if they do they can get a quick promotion
This was after final interviews, not the resume review stage, but gives an idea of some of the types of conversations that happened
turbid tapir
We can only make guesses
weak coral
IMO, yes. The number of situations where your resume is more attractive than the other applicants' is few. That's your issue right now. Unintuitively, getting more experience is making your resume worse.
As in, it's now larger and less approachable and your experience isn't really meaningfully better to make up for it.
weak coral
TBH I didn't even read the points because there are so many of them
I think you need a great amount of refinement
Having a one or two page resume doesn't matter
But it seems like you don't know why someone would want to hire you
weak coral
Ultimately it's unfocused.
A resume isn’t a holistic view of your employment and education history, it’s a one page highlight reel of your achievements
This is not a highlight reel.
It's meandering and difficult to parse, so people will choose not to parse it.
No one will delete it. Good luck.
heady heath
Some additional feedback to the above - there's a lot of flowery language like "sleek and logical", "user-savvy", "pivotal", "causing the business to skyrocket", "ensuring meaningful experience". Please be more succinct but also more specific.
As a reader this drives me insane because it tells me nothing. How did you measure whether it was meaningful? Busines skyrocketed - ok, great, but by how much did this impact it?
Another example - Doubling the speed of dev and deployment? Isn't that a bad thing? Reword this. You mean doubling productivity, right? Anything measurable there?
As a former hiring manager, I'd keep this resume on my desk (because it's clear you're productive) but I'd still put at the end of the pile (because I have no idea what anything amounted to).