Ashley Rossman

Hump day resume tip! Here are two examples of resumes I’ve reviewed this week. Similar tenures, skillsets, and ability – but two separate ways of showcasing their experience. Resume 1: Used .NET, SQL, and Angular. Resume 2: Developed greenfield projects and maintained over 50 legacy services across a large corporate ecosystem, using C#/.NET Core/.NET Framework, RESTful API, and microservices. I have been seeing more of Resume 1 of late. Unfortunately for Resume 1, they haven’t been getting many calls and they’ve been frustrated by their job search. As you can deduce by this post, managers are hoping to see more of Resume 2. Developers have been in high demand for so long, they haven’t needed to put as much care into their resumes as before. With the string of layoffs we’ve seen over the past two years, things are not what we’re accustomed to. For those who are out of work or seeking new work, you don’t need to write a novel in your bullet points. However, a little expansion on what you do with technology you touch daily will be a huge value add to your job search. I’m trying to help those I come across in the moment. If there is anyone in my feed who needs a quick resume review, I am happy to help where I can. This market stinks, but we take some steps to make it stink less.

42

9 Comments

I'm genuinely curious to hear from tech leaders – what's the biggest headache you're dealing with staffing right now? Is it finding those elusive developer skills, keeping projects on track, or navigating the changing landscape? Let me know in the comments! #itstaffing #staffingchallenges"

4

Got some tips for my recruiter friends out there. 1. Learn the acronyms for the job your recruiting. I just had a recruiter ask me to update my resume because he didn't see Oracle EBS on there. My resume has over 15 years or Oracle E-Business Suite experience all over the last few positions, and yes, EBS is on my resume as well, as in "Oracle E-Business Suite (EBS)" 2. My android phone does an initial screening of calls it doesn't recognize, whether I want it to or not. It doesn't ring my phone until you answer some basic questions like "Who are you? and What do you want?" I will pick up if you just tell Google why you're calling. Why do you feel the need to email me and tell me that you tried to call me and to please call you back?

5

Ever thought your hiring process could be too long? Some great points that you may not have considered were highlighted in the Haskellforall blog from an engineering manager's experience to give you some food for thought. Their take is that you should only need one technical interview and one non-technical interview (each no more than an hour long). 💡 More effective interviews “When everyone is responsible, no one is responsible.” 💡 Better senior applicants 💡 Priors and bias Full article below (3 min read) https://lnkd.in/gnkbQta9

5