Now I have a pitch style CV and have dumped the chronological for well over a decade.
However writing a guide like this you need up front to show that you have actually done a lot of recruiting.
21–30 of 132 posts
Now I have a pitch style CV and have dumped the chronological for well over a decade.
However writing a guide like this you need up front to show that you have actually done a lot of recruiting.
One thing that always blows me away (literally) is candidates that will eat like a tunafish sandwich with onions five minutes before they come in for an interview.
"GPA does matter" No, it does not, unless you're a recent graduate. Absolutely nobody pays attention to your GPA, if you're more than a few years in your career.
As a new grad I didn't have my GPA on my resume and it never actually came up except for the occasional transcript request. I had a fine GPA, but not high enough for it to be a nice datapoint. I had plenty of interest with lots of companies, including many FAANGMGOEWVIOPJW companies. This was years ago though.
"GPA does matter" No, it does not, unless you're a recent graduate. Absolutely nobody pays attention to your GPA, if you're more than a few years in your career.
I never put my GPA on any resume. I had a garbage GPA because the only classes I went to were CS classes so I got horrible grades in all my required electives. I was worried someone would ask and no one did.
"GPA does matter" No, it does not, unless you're a recent graduate. Absolutely nobody pays attention to your GPA, if you're more than a few years in your career.
I never put my GPA on any resume. I had a garbage GPA because the only classes I went to were CS classes so I got horrible grades in all my required electives. I was worried someone would ask and no one did.
I disagree about having an Objective Statement. I replaced mine with a Summary long ago. Also, talking about your interests should happen during an interview or even a phone screen. You don't list "Film Noir" when applying to a flowers shop.
Earlier quoted context omitted.
As a new grad I didn't have my GPA on my resume and it never actually came up except for the occasional transcript request. I had a fine GPA, but not high enough for it to be a nice datapoint. I had plenty of interest with lots of companies, including many FAANGMGOEWVIOPJW companies. This was years ago though.
Maybe things have changed, but when I went to career fairs as a uni student in the 00s they all asked for my GPA. Less than 3.5 was pretty much an instant no.
I had about a 3.5, so nothing to write home about. Got offers from a few big tech companies.
I really think they didn't care, unless my barely 3.5 GPA just made the cutoff when they looked at my transcripts.
I disagree with this resume advice actually. He for example removes that he was in the military sniper team and won best shot, but keeps high school education? I would totally say the opposite, keep the cool the side thing that's a conversation starter, but remove irrelevant educational experience. Including the number of stars on the github projects they worked on seems so.... narcissistic? Promotional? Idk but its…
I disagree with this resume advice actually. He for example removes that he was in the military sniper team and won best shot, but keeps high school education? I would totally say the opposite, keep the cool the side thing that's a conversation starter, but remove irrelevant educational experience. Including the number of stars on the github projects they worked on seems so.... narcissistic? Promotional? Idk but its…
Depending on whether you took advantage of the opportunity and who you are interviewing with, it can be a strong differentiator and set you onto a quicker path to promotion.
The stars part is flawed because it's set against the 19 commits which don't really quantify anything. Both these miss after some good build up around the adoption of the Docusaurus. It'd be better to have a description of the impact of the 19 commits.
Earlier quoted context omitted.
The last time I interviewed, I did it full-time for about a month. Was kind of fun actually: you're solving isolated little coding problems, talking with companies about their engineering and business challenges, meeting smart and friendly people, and at the end of it all you get a big pay raise. The downside is mostly that it's a ton of scheduling calls and on-sites (back when those were in person). At the end of th…
Well yes. To get a software engineering job, step 1 is to quit your software engineering job to study full time to get a job doing something very similar. Doing your job as a software engineer is an impediment to interviewing as one.