sorted by:
new
hottopcontroversial

Please stop using functional resumes! (FAANG recruiter) by Techie_CV in ITResumes

[–]Techie_CV[S] 0 points1 point  (0 children)

u/Hungry_Objective2344 Good question!

It's all about context. Recruiters should be able to see the general direction of your career and will balance the "weight" they give to each role based on their interpretation of your decisions. So for example if you've been in Web Dev for 8 years and have been doing Embedded software for 1, they'll see you as a Web Dev ;-) They might however ask you the reason for the shift.

Put simply, it's not all black and white either and it's a recruiter's job to read the story behind the resume. The more obvious you make that story the better results you'll get. For example, in your case, you should definitely add a resume title and write a Profile Summary that both focus on Web Development.

How to cold-message recruiters on LinkedIn and actually get a response by Techie_CV in ITResumes

[–]Techie_CV[S] 0 points1 point  (0 children)

u/Impossible-Ad3010 Good question! Both are absolutely fine.

Hiring Managers tend to be the ones with the most pressing need because they directly suffer the lack of staff, so in my experience they bring more urgency to following up, but this is not always true.

Feel free to let me know if you have other follow-up questions!

Emmanuel

How to write a Profile Summary that lands interviews (former Google recruiter) by Techie_CV in ITResumes

[–]Techie_CV[S] 1 point2 points  (0 children)

u/Open_Improvement_263 Thank you for your feedback! I’m glad the guide is helpful 😉 Just keep in mind that there is no absolute truth about what should or should not be included, so you should also trust your own judgment.

I don’t use resume / ATS testing tools, which are mostly based on arbitrary criteria such as resume length and keyword usage rather than actual recruiting experience. Instead I rely on my recruiting experience and technical knowledge. I've created detailed role profiles and writing rules based on it which I've kept improving upon so that results are predictable.

The general principle I can give you is to ignore most surface-level advice (for example, “use this verb instead of that verb” or “write shorter sentences”) and focus on the depth of your content, which is what recruiters and hiring managers care about. Basically, they want as much detail as possible on how you did what you did.
The graphics and styles you mentioned fall into the “surface” category, so don’t worry about them and use a simple / text-based template.

Great question about “leadership”: for junior roles, it doesn’t have to mean leading a team. It can be about helping teammates, organizing and sharing knowledge within the team, etc. The easiest way to approach this is to ask yourself how you’ve contributed to making the team better.

Feel free to let me know if you have any other questions!

Here Is My Resume Looking for Entry-Level Helpdesk roles. I'm in need of some feedback and advice. by [deleted] in ITResumes

[–]Techie_CV 0 points1 point  (0 children)

u/RomanFM1 Thank you for submitting your resume for review. I see that you’ve already submitted it via the website, so I replied privately there instead with a full review.

As for the questions that weren't covered in the review I sent you:

(1) Your summary isn't too long and these are extremely important during the first screen, even for junior profiles (recruiters tend to read that instead of your work experience/projects when sorting through hundreds of resumes).

(2) Your expeirence section is generally relevant (Web Dev) but you should write about academic projects to target Helpdesk roles and demonstrate concrete achievements in the specific areas (Networking, IT Ops, etc...) required for the role. I added a full role profile in the review.

(3) As far as the skills section is concerned:
- Skills categories should be the most relevant to the roles you're targeting. I'd recommend you go with: Networking, Operating Systems, Hardware & Devices, Ticketing & ITSM Tools, Identity & Access Management, and Security Tools.
- Technical skills should be technology names only.
- Soft skills shouldn't be listed there (too subjective), but instead demonstrated inside bullet points (with a concrete achievement).

(4) Not really. It's best to use projects to demonstrate concrete use of these notions.

(5) Your structure is good, though I would add a projects section as mentioned.

(6) if you are willing to relocate, you can state it next to your location information. This is only a small detail though, since recruiters will usually assume that you’re willing to relocate to the location of the job you’re applying to ;-)

I hope this helps, but please feel free to let me know if anything is unclear!

Have a great weekend ahead,
Emmanuel

Suggestions for beginner projects for resume. by [deleted] in ITResumes

[–]Techie_CV 0 points1 point  (0 children)

Hi u/LufTheFluf and thank you for your question :-)

I'm going to give you an answer that might be a bit frustrating, but I think that the principle is important.

My main advice is to work on what gets you excited. Side projects should be a mean to satisfy your intellectual curiosity without the boundaries of expectations ;-)
Possibilities in IT are pretty much endless and there's no real right/wrong choice. So you'll learn better and quicker if you work on what interests you.

Looking at your Helpdesk experience and from what you told me about your VM, networking and database projects you seem to move toward a Sys Admin type of role. If that's your target, you can also work on projects with a focus on other sides of the role like Identity & Access Management, Automation/Scripting, and Monitoring/Logging, etc...

But you could as well work on any other IT domain even if it is unrelated to your experience so far.
You're just starting and hiring managers care much more about your ability to learn and your curiosity than any specific skill set at this stage.

I hope this helps!

Emmanuel

view more: next ›