Comment Re:The bottle was leaking for years (Score 1) 128
You make good arguments, of course, and I understand the general lazy approach to the resume. If you're going to do the lazy resume, just make sure it's fantastic. I read every single resume, I do a full review, and I give every applicant a fair chance. I've changed Office software, from Libre, Only, Office 365, just because a resume shows up mis-formatted. Furthermore, I've made text colour changes, high-light changes, checked links in multiple browsers, and even reached back out to get a new copy of the resume.
That is not common, the attention I give an applicant is rare, hell, maybe a one-off, but, I'll give you that respect because I really want to find a good quality candidate. When it comes to Java vs JavaScript, when I say they're a Java developer, I mean Java, not Java + JS, just Java. If I see JS, TS, etc... that's fine, I don't need to see Typescript under the Angular framework, I just need to see TypeScript, and actually just JavaScript because the switch is easy. JavaScript / TypeScript is terrible, but, it's the web, so you have to work in something generic enough it's supported everywhere, even if it sucks (and it does).
Being clear C# and GO are just nice to have, they help, but no one losses the chance because they don't have those skills. Really what we're looking for is a TypeScript / JavaScript developer, with real skill apparent from the resume. I said this somewhere else but the problem I run into a lot is seeing something like: Expert in AHTML, BHTML, CHTML, DHTML and XHTML. Then CSS, ACSS, BCSS, SCSS, and LESS. Continue that on for everything, and then in the interview, which is made from your resume, every applicant gets a customer interview, explain A vs B vs C, vs D vs X HTML. That always got followed, 100% of the time, with silence. I had one guy get mad and tell me I stacked interview against him, but he put DHTML and XHTML in his resume. He also had CSS, SCSS, SASS and LESS, but then couldn't answer a single question about them.
Now that over a long resume, broken into different areas, sure, but in 1 job, over 1 year, you used every technology including COBOL? I had one resume that said the guy increased productivity 1 000% every two days, in a product. I throught that was an error, asked for his resume again, and same statement, 1 000% every two days? I had others that were all over the map, and it's they don't make sense, you could be very educated in A, B, C, D, E, F, X HTML, sure, but you should be able to easily explain why in a resume: "Worked draft proposal for HTML specifications ranging from A - X", or "Developed frondend of software X, made sure compliant with HTML A - X, due to regulatory compliance order XXXX-1111".
If I got a plain text formatted resume, I'd smile! If you're not going to use PDF, just use TXT because using DOCX, actually throws in more problems for you. There is nothing wrong with a long resume, full of experience, and terms, but it should make sense, and it can be generic, but that doesn't mean it should be thrown together in a blender, full of broke URLs and broken English.
That is not common, the attention I give an applicant is rare, hell, maybe a one-off, but, I'll give you that respect because I really want to find a good quality candidate. When it comes to Java vs JavaScript, when I say they're a Java developer, I mean Java, not Java + JS, just Java. If I see JS, TS, etc... that's fine, I don't need to see Typescript under the Angular framework, I just need to see TypeScript, and actually just JavaScript because the switch is easy. JavaScript / TypeScript is terrible, but, it's the web, so you have to work in something generic enough it's supported everywhere, even if it sucks (and it does).
Being clear C# and GO are just nice to have, they help, but no one losses the chance because they don't have those skills. Really what we're looking for is a TypeScript / JavaScript developer, with real skill apparent from the resume. I said this somewhere else but the problem I run into a lot is seeing something like: Expert in AHTML, BHTML, CHTML, DHTML and XHTML. Then CSS, ACSS, BCSS, SCSS, and LESS. Continue that on for everything, and then in the interview, which is made from your resume, every applicant gets a customer interview, explain A vs B vs C, vs D vs X HTML. That always got followed, 100% of the time, with silence. I had one guy get mad and tell me I stacked interview against him, but he put DHTML and XHTML in his resume. He also had CSS, SCSS, SASS and LESS, but then couldn't answer a single question about them.
Now that over a long resume, broken into different areas, sure, but in 1 job, over 1 year, you used every technology including COBOL? I had one resume that said the guy increased productivity 1 000% every two days, in a product. I throught that was an error, asked for his resume again, and same statement, 1 000% every two days? I had others that were all over the map, and it's they don't make sense, you could be very educated in A, B, C, D, E, F, X HTML, sure, but you should be able to easily explain why in a resume: "Worked draft proposal for HTML specifications ranging from A - X", or "Developed frondend of software X, made sure compliant with HTML A - X, due to regulatory compliance order XXXX-1111".
If I got a plain text formatted resume, I'd smile! If you're not going to use PDF, just use TXT because using DOCX, actually throws in more problems for you. There is nothing wrong with a long resume, full of experience, and terms, but it should make sense, and it can be generic, but that doesn't mean it should be thrown together in a blender, full of broke URLs and broken English.