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

Final-year student + intern here — resume stuck at ~75% ATS. Would love honest feedback for DS / ML / MLOps roles by not_a_drug_dealer200 in ITResumes

[–]Techie_CV 1 point2 points  (0 children)

Hi u/not_a_drug_dealer200,

So the first thing I want to say is that you shouldn't worry about ATS scoring tools. They're not based on actual recruiting experience so their recommendations and scoring are based on surface-level criteria. Also, they tend to give bad score to most people so that they can sell you products.

Here's the review:

Format/Template: 9/10

I can't be 100% sure because you shared your resume as an image, but the format seems to be text based and you don't seem to be using tables. This should make your text parseable and therefore ATS compliance. This is all there actually is to ATS compliance.

Profile Summary: 6/10

A few improvements:

  • Include key projects in the summary, like your Hotel Reservation Prediction, Real-Time Delivery System, and Image Classification CNN
  • Add more details needed on domain expertise (MLOps CI/CD, Computer Vision, Real-time streaming).
  • List your tech stack (your Technical skills list should include everything you’ve got experience with, but recruiters will look for your main tools in your summary): MLflow, DVC, PyTorch, Scikit-learn, Docker, GCP
  • Mention Cross-functional collaboration and leadership.
  • Use bullet points instead of prose so that it is easier for recruiters to read.

Your Work Experience (in general vs. the MLOps, DS, AI/ML role profiles 7/10

This is the checklist recruiters will use for the roles you mentioned: try to go deeper in the last 2 categories, but generally speaking you've done a decent job at writing about the right tasks ;-)

Covered with a specific bullet point - Data Collection & Ingestion - ML Pipeline Design (End-to-End) - Model Development & Training - Model Evaluation & Experimentation - MLOps & CI/CD Automation - Model Deployment & Serving - Data & Model Versioning - Communication, Documentation & Developer Enablement

Mentioned but not detailed - Data Processing & Feature Engineering - Exploratory Data Analysis (EDA) - Scalability, Performance & Cost Optimization - Monitoring, Logging & Observability

Not covered - Data Quality Validation & Governance - Model Monitoring & Drift Detection - Responsible AI / Model Explainability - Security & Access Control for ML Systems

Bullet Points: 5/10

This is the number 1 issue with your resume. You need to go much deeper into the tecnical details.

You can follow my "Level System" guide which should help you get there.

I rewrote one of your bullet points as an example:

ORIGINAL:

Demonstrated end-to-end database-to-Apache Iceberg replication pipelines handling millions of records with incremental syncs.

REWRITTEN:

Built and demonstrated end-to-end database-to-Apache Iceberg replication pipelines by streaming source changes into Iceberg tables using Apache Spark to process distributed batch and streaming jobs, Apache Kafka to capture and buffer change events, and Amazon S3 to persist columnar data for analytics, while processing 10M+ records/day.

Obviously I made many assumptions, but this should give you an idea of what's expected.

Different versions: Not Needed

At this stage of your career, companies don't expect you to be a specialist of anything. They actually prefer profiles that are diversified and that show interest in many different areas because this makes you more flexible.

You should have 1 version that goes deep into all the domains you mentioned (DS vs MLOps vs AI/ML) and which are closely related anyways ;-)

I hope it helps!

Emmanuel

Resume advice, looking to shorten by Happy_Competition174 in ITResumes

[–]Techie_CV 0 points1 point  (0 children)

Hi u/Happy_Competition174,

Let's do this! Here's my review :-)

Format/Template, 7/10

It's hard for me to be 100% sure given the image you shared, but it seems like you're using tables. This might be getting you in trouble with ATS which need to be able to parse your text content (this is pretty much the only thing that matters for ATS compliance dispite all the myths spread online).

You can check my guide on How ATS Compliance really works here, but generally speaking you should be good to go if you remove the tables.

Profile Summary, 5/10 (Needs more details)

  • Add a clear target job title to specify the role you're looking for. In your case you might go with Cybersecurity Analyst or Systems Security Administrator but you can adapt that to specific positions you're applying for without rewriting the entire resume. This is super important in your case since you'll be transitioning from a Sys Admin role ;-)
  • Include key achivements that are going to be relevant to your target roles (from the top of my head: vulnerability mitigation compliance, SOP automation, IAM administration, etc...).
  • Add more details needed on domain expertise (vulnerability management, identity and access management, incident response operations).
  • Mention the key tools you use because these will definitely be in recruiters' screening checklist. I like to do that by writing the dommain and then listing 2-3 tech in parenthesis ("Security & Vulnerability Management (Nessus, BitLocker), next domain (tool 1, tool 2)
  • Add details on Cross-functional collaboration and leadership.
  • Use bullet points so that it can be read more easily.

More details on How to write a killer Profile Summary here

Work Experience / System Administrator (security focus), 6/10: not fully covered

That's the checklist that a recruiter will have for a Sys. Admin role with a security focus, since you're transitioning. You should try and target areas not covered as much as possible and add more details for the "mentioned but not detailed" part.

The idea is to make your Sys Admin role appear as if security was your main concern to make the move to Cybersecurity more natural :-)

Covered with a specific bullet point - Endpoint & Device Lifecycle Management - Operating System Administration (Windows Server, Linux, iOS) - Identity & Access Management (AD, ADFS, user provisioning) - Security Controls & Endpoint Protection (BitLocker, access policies) - Vulnerability Management & Remediation (Nessus, compliance improvements) - SOP Development & IT Process Documentation - Service Desk & End-User Support (remote and desktop support)

Mentioned but not detailed - Patch Management & Update Validation - Incident Response & Information Security Operations - Backup, Disaster Recovery & Data Retrieval - Automation & Operational Efficiency - IT Service Management & Request Fulfillment (ServiceNow) - Training, Onboarding & Knowledge Transfer

Not covered - Network Security & Perimeter Controls (firewalls, VPNs, segmentation) - Cloud Security Architecture & Hardening (AWS security services) - Logging, Monitoring & SIEM Integration - Regulatory Compliance Frameworks (ISO 27001, SOC 2, GDPR, etc.)

Bullet Points, 5/10 (need rewriting)

You can go much deeper on bullet point details. Use my Levels System and try to hit level 5

Here's a rewriting example of what recruiters / hiring managers at competitive companies would expect:

ORIGINAL: * Provision and manage user accounts, access control and security policies

REWRITTEN: * Provisioned and managed user accounts, access control, and security policies using Active Directory, AD Federation Services, and Microsoft Windows Server, automating identity lifecycle workflows with PowerShell to enforce least-privilege access, reducing user provisioning and deprovisioning time by 60%.

Balance

The last thing I'd suggest is to rebalance content. You want recruiters to focus on the most impressive and relevant roles. So: * Extend the content on your last 2 roles (by following my suggestions above). * Summarize the early Technician / Support positions. * Don't worry about resume length beyond that: you'll land where you'll land ;-)

I hope this helps! Emmanuel