4 ms·
I’m probably as old as you are and my resume is two pages. I’ve worked ten jobs and I don’t have anything going back further than 10 years. No one cares that
by scarface_74 2y ago
I’m probably as old as you are and my resume is two pages. I’ve worked ten jobs and I don’t have anything going back further than 10 years. No one cares that I wrote C and Fortran on main frames, VB6 and C++/MFC/DCOM
or that I worked on ruggedized Windows CE devices. This was all pre-2012.
No one is going to read an 8 page CV. But honestly, I never depend on my resume to get a job. It’s a requirement. But I don’t blindly submit my resume to an ATS. By the time I’m sending my resume, I’m already 99% sure I’m going to get an interview because I’ve already talked to someone.
When I was looking for a job before, I had one of the managers describe one of the products that I would be over. The problem was, that if they had taken an even cursory look at my resume, they would have seen that I had worked at one of their acquisitions that the product was based on and I designed the architecture of the product.
I had worked at the company until 2020 and I was referred by my former manager to be a staff architect over all of the companies acquisitions.
- kasey_junk 2y ago“By the time I’m sending my resume, I’m already 99% sure I’m going to get an interview because I’ve already talked to someone.” This 100%. My resume is always custom tailored to the hr process it’s going through because I position them to only be supplied once that’s one of the final check boxes.
- scarface_74 2y agoI wouldn’t even go that far. I use to have one resume that got sent out to everyone. As of last year, I have two. But if I’m going through the network, I already know the decision makers are going to pull my resume through the HR process. One that is focused on strategic app dev + cloud consulting where I emphasize that you can fly me out to customer’s sites along with sales and I can do requirement analysis and help close deals and then lead the projects. The other is for my “Plan B” jobs and more focused on hands on keyboard “senior” enterprise developer jobs.
- rramadass 2y agoThe point was to make explicit one's specific work achievements. In your case, it seems you do it via contacts/word-of-mouth which works for you. Reading a long CV is generally not that much of a chore since a lot will be boilerplate (eg. company name, duration etc.) which can all be skipped as you pick out technical/other details relevant to the job. I also disagree that older experience beyond 10 years (some even use just 5 years) can be skipped. The reason i like to see everything is that it gives me many clues as to the nature of the person i am to interview viz. whether they have a breadth of thought to understand different concepts, the experience to have done it in reality, whether they are adaptable/self-driven etc. Without this information in hand i literally have to spend the first half of the interview asking them what they actually did before i can move on to the interview proper.
- scarface_74 2y agoBut no one to a first approximation is going to do it. Statistics show that on average, people only look at your resume for 6 seconds. And I’m not asking questions about what you did 30 years ago. If I ask you the standard question as an interviewer “tell me about yourself”. I expect you to succinctly walk me through the parts of your career that are relevant to the job. I am then going to ask behavioral questions to assess whether you have the traits I need, the “tell me about a time when…” questions to see if you can work at the needed level of scope and ambiguity. I then ask them what they were most proud of to work on a dig into their technology choices and tradeoffs
- rramadass 2y agoI am not buying the oft-quoted statistics in HR/Recruiting which like most popular adages is mostly made up from a few anecdotes and widely disseminated which people then accept because "everybody says so". The key is to hook in the reader from the summary/qualifications on the first page. The "tell me about yourself" question is one of the worst to ask and i never do this. It is so open ended that people start rambling. Instead get them to focus (this also calms their nerves) by asking about notable jobs picked from their resume "what did you do as ... at ..." and dig more as needed. Do this for a couple more jobs if available and you will get to see how confident the candidate is, how he communicates, the depth of his knowledge and his modes of thinking. From here, you generalize to what the job actually needs and give the candidate some idea of the job and its environment and ask how he hopes to fit in and contribute. This makes things clear to both interviewer and interviewee. I also do not place much weight on personality/psychology tests/questions. People generally cannot be truthful in their answers to questions like "how do you deal with conflict with your co-worker?" etc. Here i trust to "gut feeling" based on non-verbal impressions, verbal communication and pointed questions (challenge the candidate by taking a contrarian stance and see how he responds). Finally, i make sure that the interviewee at the very outset understands that though i am the interviewer it does not mean that i am more knowledgeable than him in his areas of expertise. This works great by boosting his confidence which then leads to a more natural interaction. Recruiting/HR is a complex art where you have to consider various factors to build a picture of a person (suited to a role) from factual data and psychology. IMO a good way is to start with an understanding of Self-Determination Theory of Edward Deci and Richard Ryan - https://en.wikipedia.org/wiki/Self-determination_theory https://en.wikipedia.org/wiki/Self-determination_theory For a nice overview, see the book Why we do What we do: Understanding Self-Motivation by Edward Deci.