{"id":26050297,"url":"https://github.com/devscanr/resume-checklist","last_synced_at":"2025-12-06T21:02:05.440Z","repository":{"id":281007509,"uuid":"943890768","full_name":"devscanr/resume-checklist","owner":"devscanr","description":"Resume checklist. Checklists for professional profiles: LinkedIn, GitHub.","archived":false,"fork":false,"pushed_at":"2025-03-06T13:54:22.000Z","size":8,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-03-06T14:22:01.103Z","etag":null,"topics":["checklist","cv","github","linkedin","resume"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/devscanr.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-03-06T12:41:16.000Z","updated_at":"2025-03-06T13:54:25.000Z","dependencies_parsed_at":"2025-03-06T14:22:02.310Z","dependency_job_id":"fb92e26d-5e46-49ea-a493-569ccf15bbae","html_url":"https://github.com/devscanr/resume-checklist","commit_stats":null,"previous_names":["devscanr/resume-checklist"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/devscanr%2Fresume-checklist","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/devscanr%2Fresume-checklist/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/devscanr%2Fresume-checklist/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/devscanr%2Fresume-checklist/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/devscanr","download_url":"https://codeload.github.com/devscanr/resume-checklist/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":242492110,"owners_count":20137575,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["checklist","cv","github","linkedin","resume"],"created_at":"2025-03-08T02:27:50.820Z","updated_at":"2025-12-06T21:02:05.434Z","avatar_url":"https://github.com/devscanr.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cp align=\"center\"\u003e\n  \u003cb\u003eEnglish\u003c/b\u003e\u0026nbsp;\u0026nbsp;\u0026nbsp;\u0026nbsp;\u003ca href=\"ru.md\"\u003eРусский\u003c/a\u003e\n\u003c/p\u003e\n\n# Resume/profile checklists for IT specialists\n\nBelow, you'll find a guidance on how to structure your resume(s) and optimize your profiles on career/professional networks such as LinkedIn and GitHub.\nImmediate note: terms **Resume** and **CV** are interchangeable, but culturally specific. Use the one that is used and expected in your target area.\nBy following these simple steps, your resume(s) and profiles will make a stronger impression on recruiters and hiring managers. \n\nAs engineers speaking to fellow engineers, our goal isn't just to show you the steps you can do. We'd like to explain which and why certain actions matter when crafting your resume and preparing for a job search.\n\nTo put this insights into practice, fork this repository, enable issues and create a TODO task with a predefined list of actions:\n\n\u003cimg src=\"assets/todo.gif\" width=\"640px\"/\u003e\n\nThe provided information should be taken as a starting point. There're definitely many more culturally-specific, domain-specific, etc-specific points that were omitted for clarity. If you're interested in further recommendations or a professional resume review – feel free to [ask the authors](mailto:info@devscanr.com). Most pro-tips are contextual and wouldn't fit a general document.  \n\n## List of Content\n\n1. [General checklist](#1-general-checklist-)\n2. [Resume checklist](#2-resume-checklist-)\n3. [Resume under a microscope](#3-resume-under-a-microscope-)\n4. [LinkedIn profile checklist](#4-linkedin-profile-checklist-)\n5. [GitHub profile checklist](#5-github-profile-checklist-)\n6. [Tools](#6-tools-)\n7. [Vocabulary](#7-vocabulary-)\n\n---\n\n## 1. General checklist ✔\n\nGeneral recommendations for resumes and professional network profiles.\n\nIt's critical to understand the role of ATS in the job search.\nIf you never heard about \"ATS\", read this [short note](#7-vocabulary-)\n\n### 1️⃣ Contact Information\n\nEnsure all contacts (links, usernames, etc) are listed accurately. Verify that links are\nfunctional and up-to-date. Recheck that your location is present and clear.\n\n### 2️⃣ Avatar / Photo\n\nA large topic on its own. [A photo in resume](https://resume.io/blog/picture-on-resume-or-not)\nmight be legally required, prohibited, or none. Some companies might add more rules... it has to be researched.\n\nTalking about GitHub profiles – a photo works better than a creative avatar. It definitely looks more trustworthy\nto see a real face with a real name.\n\nCriteria for a good photo:\n\n- Face-focused portrait. The percentage of \"creativity\" should be aligned to your role.\n- Neutral background and attire.\n- Adequate quality: clear, well-exposed image.\n\nHow to take a quality photo at home:\n\n- [Video Tutorial](https://www.youtube.com/watch?v=n_rPTWXn__U)\n- [Article](https://headshots-inc.com/blog/how-to-take-professional-headshots-at-home/)\n- AI photo Enhancer: [ReMini.ai](https://remini.ai) (one photo enhancement for free)\n- Paid AI Enhancers: [HeadShotPro](https://www.headshotpro.com/) \u0026 [HeadPix.ai](https://headpix.ai/)\n\nFor best results, consider a professional photo shoot.\n\n### 3️⃣ Full Name\n\nSynchronize how your name appears across LinkedIn, GitHub, and your resume. Recruiters shouldn't\nhave to guess if different accounts belong to the same person, especially if you've changed your\nsurname. For applicants with foreign (non-english) names: transliteration between profiles should remain consistent.\n\n### 4️⃣ Title / Specialty / Desired Position\n\nThe title (e.g., Product Engineer) on your resume and profiles must align\nwith the **position you're applying for**.\nThis field is crucial for talent searches and filtering within [ATS systems](#7-vocabulary-).\n\nA common mistake is spending mere minutes on crafting a title, assuming it's self-evident. However,\nthis field deserves careful consideration. Your title should reflect your desired rather than\ncurrent role/specialization. Use popular, widely recognized job titles. Phrases like \"Backend Ninja\" may\nmake sense to humans but will negatively impact search rankings because text-based searches\nprioritize exact matches. As a result, your resume could go unnoticed.\n\nWhen working on title, we recommend using a [SEO](#7-vocabulary-) approach. Search engine guidelines\nfor a title typically recommend staying within 50–80 characters. The beginning of the line carries the most weight. \nKeep in mind that you don't know where your title might get truncated or shortened in an ATS, so ensure it looks good \nat varying lengths. We suggest choosing one of these formats:\n\n```\n1) [Desired Position Title] | [Narrowing Hard Skill(s)]\n\nEXAMPLES:\nSenior Frontend Developer | React.js, Redux, Node.js, Tailwind CSS\nSenior Frontend Developer | CSS Animation \u0026 Accessibility\n```\n\n```\n2) [Desired Position Title] | [Value Proposition]\n\nEXAMPLES:\nSenior Frontend Developer | Mentoring Teams While Driving Innovation\nSenior Frontend Developer | Delivering Pixel-Perfect, Responsive Solutions\n```\n\n## 2. Resume checklist ✔\n\n### 1️⃣ Contact information. Full name. Photo.\n\nFollow the guides from the [General checklist](#1-general-checklist-) section.\nProfessional networks like LinkedIn and GitHub are acceptable (and desired).\nLinks to your social network profiles are not allowed (and, in some cases, strictly forbidden).\n\n### 2️⃣ Readability\n\nThe resume should be easily readable by a human and parsable by a robot.\nUse only PDF format (unless the job requirements specify otherwise).\nHTML and other formats will be a problem for ATS. Use a standard font of an adequate size (more below). The resume should look clean and readable.\n\n### 3️⃣ Structure\n\nThe resume has a standard structure from which it is better not to deviate:\n\n- Headline, the desired position\n- Photo (not always, see above)\n- Full name\n- Current location: country/city\n- Contacts. Links to profiles in professional networks (GitHub, GitLab, StackOverflow) – desirable\n- Brief description / summary\n- Technical stack, up to 7 main technologies\n- Work experience\n- Work permits – situational\n- Readiness for relocation – situational\n- Knowledge of languages ​​– situational\n- Education\n\nIt is not recommended to exceed 1-2 pages for juniors and 2-3 pages for senior specialists. If it\ndoes not fit, try reducing the font size, for example, to 10-12 points. If it still does not fit, you need to cut\nout the excess.\n\n_Corrections for students._\nInstead of `Work experience → Education`, change the structure to `Education → Projects`.\nFor non-students, a list of projects is also acceptable, in certain cases.\n\n### 4️⃣ Portfolio / GitHub link\n\nIn our view, each engineering resumes should contain a link to your portfolio and/or your GitHub (GitLab) professional account.\nNDA is not an argument, there're multiple ways to get around it (legally). If you have nothing to show: no screenshots, no contributions, \nno public projects, no stars, nothing... – it's super bad and must be fixed.\n\n### 5️⃣ Other\n\nIt is worth checking the resume with a PDF validator. The text should be proofread several times,\nit should not contain spelling errors. Knowledge of the language may be secondary... but errors\nindicate problems with attention to detail, a valuable skill. Ask a colleague or friend to check\nyour resume — this is always useful. Use spell check services.\n\n*Found a typo in this article? Let us know\nvia [issues](https://github.com/devscanr/resume-checklist/issues)*.\n\n## Common Mistakes\n\nBroadly speaking, as each point might have an exception:\n\n⚠️ Your age, marital status, etc. are indicated\u003cbr/\u003e\n⚠️ Emojis or other images are used\u003cbr/\u003e\n⚠️ Non-PDF format like WORD or HTML format is used\u003cbr/\u003e\n⚠️ External links named \"Find out more\"\u003cbr/\u003e\n⚠️ Copy protection is enabled in PDF (may interfere with ATS)\u003cbr/\u003e\n⚠️ No headings, unfamiliar layour or section names\u003cbr/\u003e\n⚠️ Politics, religion, unrelated hobbies\u003cbr/\u003e\n⚠️ Too much or too little information\n\nList your hobbies and interests in LinkedIn, GitHub. There should be no room for this in a resume.\nDo not list your soft skills separately – it doesn't look good and trustworthy. Embed them in the **Summary** and/or in the **Work Experience** sections.\n\n## 3. Resume under a microscope 🔬\n\n### 1️⃣ Summary / About me\n\nA short, concise description of your experience, key skills, and achievements.\nIt presents you as a specialist. Explains why extactly you should be hired.\nMaximum 3-4 sentences. For everything else, there are sections \"Responsibilities\" and \"Achievements\"\nat each place of work. You can write in the 3rd person (adds neutrality)\nor in the 1st person (adds individuality). This point may be regulated by law or company rules, double-check.\nOn LinkedIn, it is better to write in the 1st person.\n\nWhat can/should be indicated:\n\n- Your general expertise, transferable skills\n- Your strengths\n- Skills in demand for the desired position\n- Your preferences regarding the industry, company, team, project (of course, not all at once)\n\n[Examples for reference](https://resume.supply/examples/software-engineer-objectives-summaries).\nThe text from the summary is used for cover letters (with modifications).\n\n### 2️⃣ Work experience\n\nIndicate the names of companies, dates of work and positions. Up to the last three that are relevant\nto your desired job. Descriptions should be adequate to the position you are applying for and the level of expertise.\nStick to the format `developed \u003e details \u003e effect`. Focus on results and achievements, not the\nprocess. The numbers should match your scope of responsibilities. Junior developers writing about \"increased business income by...\" raise a lot of questions. \n\nIn the description of tasks and achievements, use active voice and past tense (increased, created,\nimplemented). The years and months of work should be indicated. Specify the skills that were used in this\nposition. For the last place, you can even indicate a contact person for communication (maximizing trust).\n\n### 3️⃣ Education\n\nList the primary educational institutions and courses that are directly\nrelevant to the desired position. Keep only those entries that align with your target role\n(students may include relevant projects). Limit to three points.\nFormat should visually resemble the _Work Experience_ section.\nYou can mention ongoing education with a corresponding note.\n\n### 4️⃣ Skills\n\nInclude only skills that directly match the desired position. Interesting hobbies unrelated to the\nfield can detract from the resume rather than enhance it. Remember, the resume is a formal document\nshowcasing your professional capabilities. Focus on listing your core technical stack. Extensive\nlists of every framework and library appear unprofessional and do not benefit even a junior-level\ncandidate.\n\n### 5️⃣ Font\n\nSelect a standard font (Arial, Georgia, etc), to ensure your resume is displayed properly in all ATS. \nRecheck that the font size falls within an acceptable range of 10-16px. Use a single font, unless you know what you're doing.\n\n## 6️⃣ How many resumes to create\n\nShort answer: one master resume plus per-role variations.\n\n## 4. LinkedIn profile checklist ✔\n \n### 1️⃣ Contact information. Full name. Photo\n\nFollow the recommendations from the [General checklist](#1-general-checklist-) section.\n\n### 2️⃣ Title, desired position\n\nFollow the recommendations from the [General checklist](#1-general-checklist-) section.\n\nLinkedIn has a special block\nfor listing \"Job Titles\" options, which can be opened by the blue \"Open To\" button in the page\nheader.\n\nWe would like to emphasize once again that for recruiters, when they are looking for talent,\nyour job title is the most important information.\nIt is recommended to list all common synonyms for the roles by which you would like to be found.\nFor example: Security Researcher and Malware Analyst can solve identical tasks, but the search will\nindicate only one of them.\n\n### 3️⃣ About yourself (main text), Skills\n\nFollow the recommendations from the [Resume under a microscope](#3-resume-under-a-microscope-) section.\n\nA LinkedIn description can be longer and more personalized than a resume. The latter is a dry\ndescription\nof you as an employee, as a specialist. Your social profiles, however, can (and should)\nadd a note of personality and character.\n\nWhen choosing profile skills and skills related to experience at a specific company, make sure that\nthe most important skills are listed first. LinkedIn collapses information and can give a false\nimpression of your competencies if they are not sorted correctly.\nIn addition, the first skills will naturally collect more reactions (endorsements) than the last.\n\n### 4️⃣ Work experience, Education\n\nFollow the recommendations from the section [Resume under a microscope](#3-resume-under-a-microscope-).\n\n### 5️⃣ Custom URL\n\nActivate a custom URL with your name: `linkedin.com/in/yourname`. Looks more professional.\n\n### 6️⃣ Recommendations\n\nIn today's competitive talent market, profiles without reviews look increasingly pale.\nThere is nothing difficult in exchanging reviews\nwith former colleagues. Accordingly, their absence means that you 1) do not get along with\ncolleagues,\nor 2) do not show initiative, or 3) think that \"this will do\".\nWould you personally hire a person with such characteristics?\n\n### 7️⃣ \"Open to work\" flag\n\nTurn on the \"Open to work\" status. This is a flag that will add your profile to the lists for\nrecruiters.\nSome recruiters have mixed feelings about the green \"Open to Work\" sign.\nThe opinion, which we personally do not share, is that this sign is added \"out of desperation\".\n\n### 8️⃣ Other achievements\n\nCertificates, awards, courses, publications increase trust and indicate \"above average\" expertise.\nAll other things being equal, an employer will always prefer a person\nwith such evidence of competence to another candidate. In addition, all these achievements speak\nof you as a \"Continuous Learning\" expert, and this skill is consistently included in the TOP-5 most\nin-demand cross-job skills.\n\n## 5. GitHub profile checklist ✔\n\n### 1️⃣ Contact information. Full name. Avatar\n\nFollow the recommendations in the [General checklist](#1-general-checklist-) section.\n\n### 2️⃣ Brief description (bio)\n\nFollow the recommendations in the [Resume under a microscope](#3-resume-under-a-microscope-) section. \n\nThis field can hold an even shorter summary of your resume or outline your professional goals. \nSince the profile isn’t as formal as a resume/CV, there aren’t strict guidelines here. Still, \nwe advise including your title for added clarity.\n\n### 3️⃣ Repositories\n\nSelect and pin 3 key repositories at the top of the page. If everything is weak, it is better not to\npin anything.\nAdd a description to each valuable repository (what kind of project, why it was created, tags).\nDo not be among those who did everything that was necessary, but could not or did not want to\npresent their work.\n\n### 4️⃣ Stars\n\nSet stars to your favorite/interesting technologies, if you haven't already. For active accounts,\nthe lack of stars suggests that you 1) aren't interested in anything, or 2) don't appreciate other\npeople's work,\nor 3) are super busy and bogged down in business. If you have a lot of stars, organize them into\nlists (optional).\n\n### 5️⃣ Followees\n\nFollow leaders in your areas of interest. The lack of followees is perceived in the same way as\nthe lack of stars.\nHaving a lot of followers is not necessary (and it is harder to change). We recommend exchanging\nmutual following with friends to get rid of zeros.\n\n### 6️⃣ Organizations\n\nFollow organizations in your areas of interest. GitHub organizations are clubs or companies.\nTracking organizations, repositories shows your interests. According to our research and experience \nin hiring, the more the recruiter and employer know about you, the better.\n\n### 7️⃣ README\n\nIf you are motivated and have an above average GitHub profile, we recommend adding\n[a README profile](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme).\nFollows LinkedIn's profile design rules, see the [corresponding checklist](#4-linkedin-profile-checklist-).\n\nMore on this topic:\nhttps://github.com/abhisheknaiidu/awesome-github-profile-readme\n\n## 6. Tools 🛠\n\n- [Resume builder with ATS optimization](https://www.jobscan.co/resume-builder)\n\n## 7. Vocabulary 📕\n\n**ATS** (Applicant Tracking System) is a software used by recruiters when working with candidates.\nYour data gets stored in this system when you submit applications or when recruiters discover your\npublic profiles. In situations where the volume of resumes outweighs available jobs (which happens frequently),\nrecruiters implement stringent filters to streamline their workflow. As a result, only a fraction of applicants are reviewed by actual recruiters.\nIf your resume can't be parsed or fails to meet filter criteria, it’s automatically archived.\n[Read more about ATS here](https://www.linkedin.com/pulse/guide-formatting-your-resume-atshr-ai-systems-alexander-hinojosa/).\n\n**SEO** (Search Engine Optimization) is about helping search engines understand sites' content,\nand as result helping users find releval information.\n\n## Next steps\n\nNow that you understand why and how to update your resume and social accounts, we've prepared an actionable TODO list for you. \n[Fork this repository](https://github.com/devscanr/resume-checklist/fork), create a TODO issue from the provided template, and start optimizing your profiles right away!\n\n## License\n\n**CC0 1.0 Universal: public domain.** You can distribute, remix, adapt, and build upon the material in any medium or format, with no conditions. Attributions are always appreciated but not required.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdevscanr%2Fresume-checklist","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdevscanr%2Fresume-checklist","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdevscanr%2Fresume-checklist/lists"}