I’ve worked as a recruiting manager in the technology business. During that period, I reviewed hundreds of resumes from people seeking a variety of employment. Although the occupations vary, the majority of the resumes have one thing in common: they stink.
Here’s the issue: recruiting isn’t the only thing I have to accomplish in a day. There are staff meetings, design meetings, progress reports, scheduling development, and a plethora of other activities that fall within the purview of a manager. When I set aside an hour to look through all the resumes, I’ve received an open position, and the typical one passes my desk in less than 30 seconds.
That is the issue with the typical resume: the intermediate section.
It does not distinguish itself from the crowd.
Here are few tips you can use
Show your Contribution
Remember to add your open source efforts and achievements. We often forget that what we do in open-source counts as professional progress and success; therefore, we don’t mention our contributions on our resumes. “Well, I didn’t do it on the job. Thus it shouldn’t be on my CV” is a typical thought process. That is true in some cases. Also, you try to highlight which process you are using for your day-to-day activities like lean agile, agile, waterfall or something else.
Could you keep it simple?
Don’t go overboard with the design. Unless you’re a graphic artist, keep your resume in a more conventional style. Anything else is at best startling and at worst outright distracting for the recruiting manager. The substance, not the layout, is the essential aspect of your resume. The structure and formatting, like any excellent design, should take a second seat to the content.
You should mention those tools if you worked on those tools.
Most of the time, I have seen candidates use Git on their resumes. Because one should have a fundamental understanding of software version control systems, and virtually all reputable firms utilize svn and Git. Including Git as a tool on your CV will be positive, and as a university student, you should include it.
If you’re good at it, mention it.
Otherwise, you will most likely be asked the following questions in interviews:
- What is the Git command for creating a commit message?
- What is the Git reset command and its usage?
- How are you going to combine the last N commits into a single commit?
- How do you undo a commit that has already been pushed and made public in Git?
Use proper order
Sort from most relevant to least relevant. When detailing your experience, structure it such that the bullet points most pertinent to the position are at the front of each section. Because this is where my eye is most likely to fall when I skim, I’m more likely to pay attention to what I see there.
Be as descriptive as possible. Don’t tell me you “managed a major client’s project.” Tell me precisely what you did while managing it, how significant that customer was, and why I should care that you did it. You made a difference in your positions, but bullet lines like “organized corporate events” don’t tell me anything about your influence on those activities or the firm.
Early and frequent updates are recommended
When I say that you should gather numbers, you should do it on your CV. I saw people only update their resumes when preparing to begin a job hunt, which is a mistake. Several years may have elapsed since your previous update by the time you start modifying the file.
That’s many years’ worth of memories to sift through. What are the odds that you’ll remember all you’ve done in that time, let alone the numbers linked with your achievements?
Ignore the recommendation to keep it to one page
While we’re on the subject of specificity, don’t skimp on information merely to limit your resume to one page. This adage is a relic from the days of analog resumes. We’ve gone digital, and we’re not going back. One advantage of becoming digital is that no one minds if your resume is more than one page.
Everyone will skim it on their computer or gadget. They’re unlikely to print out your CV until you get to a later point in the process, such as an interview. That being stated, exercise moderation in all aspects of your life. You should not transmit a novel just because you now have permission to surpass a single page. Keep in mind that the recruiting manager’s time is valuable.
Don’t squander it. Aim for a total of two pages, maybe even a third. That should give you enough room to explain what you want without overwhelming the reader.
The summary is crucial, if not the most significant part of your resume. It’s the first thing people notice on a resume, and when someone is reviewing numerous resumes for a job opportunity, the first item they see should stand out. Spend a lot of time on this, and make it stand out. It is, after all, your sales pitch. You are a product, therefore learn to market yourself. The summary will assist you in doing so.
The Technical Skills section should include a laundry list of programs, languages, databases, methods, or other tools that you use or have used to accomplish your work successfully. Accounting, finance, engineering, and a variety of different vocations may all benefit from this. Put it here if you’ve mentioned a specific tool/software/language. https://acompiler.com/git-head/ can help you with this one.
Hope with these tips you will have a successful interview.