I assume you’re not talking about a really high end position. Even there, your network, accomplishments, and reputation will carry you much further than your resume.<p>My suggestion as a hiring manager is not to treat your resume like a fine jewel to be polished once and put on display for all to see. Instead, find out what the job requirements are and <i>tailor</i> your resume heavily to show that you are the person they’re looking for.<p>Know your audience. If your resume will have to get through a keyword screen, first improve your networking to get a recommendation from the inside. These always carry greater weight than a resume off the street. Then tailor your resume to pass the keyword filter. If they want Android, gradle, Java, and Maven, then make sure those keywords and variants (<i>e.g.</i>, gradlew and mvn) are present.<p>Quantify! People can claim vague familiarity with lots of technologies, being results-oriented, and having “contributed to growth.” Big deal. Almost anyone can say that. Tell me the size of the code base, your commit rate, the size of the team, counts of passing tests by type, which deals you closed, proposals you wrote, and so on. Be specific because it looks less like weasel-worded BS and differentiates you from the crowd.