| {"text": "TECH\nRESUME\nGUIDE\nSoftware\nengineers\nknow\nthat\nthere\nis\nno\none\nfit-size\nsolution\nfor\nanything.\nBe \nthat\ndeveloping\na\nwebsite,\nsolving\nan\nalgorithm,\nor\ndesigning\nan\narchitecture. \nWhile\nthis\nguide\npromises\nto\ndeliver\ngreat\ncontent\nto\nhelp\nyou\nace\na\njob\ninterview, \nit\ndoesn\u2019t\nguarantee\na\njob\nupfront\nor\na\nrecruiter\ncall\nevery\ntime.\nThere\nare\nplenty\nof\nfactors\nthat\ncontribute\nto\njob\nhunting.\nWhile\nfew\nare\nin\nhands, \nfew\naren\u2019t.\nIt\u2019s\nthat\ndead\nsimple.\nSo\nwhat\nare\nthe\nfactors\nthat\nyou\nneed\nto\ntake \ncare\nof?\nThere\nare\nplenty\nof\nfactors\nthat\ncontribute\nto\njob\nhunting.\nWhile\nfew\nare\nin\nhands,\nfew\naren\u2019t.\nIt\u2019s\nthat\ndead\nsimple.\nSkills\nYou\nmust\nhave\nrelevant\nskills\nto\napply\nfor\na\nspecific\njob.\nExperience\nSome\nindustry\nexperience\ncan\nmake\nyour\nresume\nstand\nout\nmore.\nCommunication\nYou\nshould\nat\nleast\ncommunicate\nwell\nin\nEnglish\n(as\nits\ninternational\nlanguage),\nif\nnot\na\nfluent\nspeaker.\nThen\nwhat\nare\nthe\nfactors\nyou\ncan\u2019t\ncontrol?\nPosition\nThe\nposition\nmight\nhave\nalready\nbeen\nfulfilled\u2014without\nyou\nknowing\nabout\nit.\nCompetition\nYou\nmight\nhave\na\nstrong\nresume\nwith\ngreat\nexpertise,\nbut\nsomeone\nmight\nhave\nmore\nthan\nyou\nto\nimpress\nthe\nrecruiter.\nEspecially\nafter\nCovid-19,\nyou\nwill\nhave\nto\ncompete\nworldwide\u2014if\napplying\nfor\nremote\nwork.\nLocation\nAlthough\nmost\nof\nthe\njobs\nare\nremote\nthese\ndays,\npeople\nwho\nare\nnear\nor\ndon\u2019t\nneed\nto\nrelocate\nare\npreferred\nby\nhiring\nstaff.\nSeniorityCertain\ncompanies\nonly\nlook\nfor\nspecific\nseniority\nroles.\nIf\nyou\nare\njust\nstarting\nor\nhave\nless\nthan\na\nfew\nyears\nof\nexperience,\nyou\u2019re\nlikely\nto\nbe\noverlooked.\nLuck\nLuck\nalways\nplays\na\nrole,\ntake\nit\nor\nnot.\nTo\nmake\nit\nless\nof\na\nfactor,\nyou\ncan\ngo\nfor\nreferrals.\n(In\nthe\nfollowing\nchapters,\nI\nwill\nshare\nthe\ntips\non\nhow\nto\nget\na\ngood\nreferral).\nNow\nyou\nknow\nwhat\nit\ntakes\nto\nbe\nready\nfor\na\njob/role.\nLet\u2019s\nmove\non\nto \nwriting\na\nresume\nthan\ncan\nsell\nyou\nfor\nthe\nposition\nyou\nhave\nbeen \napplying\nfor.\nA\ngreat\nresume:\nShowcases\nrare\nand\nvaluable\nskills\nthat\nare\nexactly\nwhat\nthe\njob \nneeds.\nIt\u2019s\nbuilt\non\nyears\nof\nexperience\nyou\ngathered\nthat\nmakes\nyou\nstand \nout\nfrom\nthe\ncrowd.\nIt\nshows\na\nsolid\nprogression\nthroughout\nyour\njourney.\nYou\ntake\nupon \nnew\nroles/challenges/responsibilities\nand\nare\nnot\nafraid\nof\nlearning \nnew\nthings.\nRemember\nthat\npreparation\nand\npersistence\nwill\nmake\na\ndifference. \nOne\nwithout\nthe\nother\nis\nan\ninvitation\nto\nrejection.\nTo\nget\nyour\ndream\njob, \nyou\nhave\nto\ndo\nthe\nhard\nwork.\nStaying\npositive,\nfocused,\nand\ncreative \nwill\nhelp\nyou\nclimb\nthe\nstaircase\nof\nvictory.\nHow\nto\nbe\na\nKickass\nNew\nSoftware\nEngineer\nguide \n(If\nyou\nget\na\npage\nnot\nfound,\nlog\ninto\nyour\nlinkedin\naccount\nfirst)\nKeep\nlooking\nfor\nsome\ninspirations\nor\nstories\nabout\nhow\npeople\nwent \nfrom\nground\nzero\nto\nsoftware\nheroes.\nIt\nwill\nnot\njust\nboost\nyour\nmorale \nbut\nalso\nguide\nyou\nlike\na\nmap.\nYou\nknow,\none\ncan\nlearn\na\nlot\nfrom\nother \nexperiences.\nNow\nwe\nunderstand\nwhat\nit\ntakes\nbefore\ncreating\na\nresume\nit\u2019s\ntime\nto\nwrite\nthat \nresume.How\ndo\nyou\nwrite\na\ngood\ndeveloper \nresume?\nThese\nare\nsome\nessential\npoints\nthat\nyou\nmust\ntake\ninto\nconsideration\nwhile \nwriting\nyour\nresume:\n1.\nYears\nof\nExperience:\nHow\nlong\nhave\nyou\nbeen\nworking?\nThe\nrecruiter\nwill\ncheck\nyour\neducation\nand\nyear\nof\npassing\nto\ncalculate\nhow\nlong \nit\nhas\nbeen\nfor\nyou?\nThey\nwill\ninternally\nmatch\nthese\nyears\nwith\nthe\nyears\nof \nexperience\nthey\nneed.\nThey\nwill\nalso\nevaluate\nyou\nwith\nother\ncandidates.\nThe \nmore\nexperience\nyou\nhave,\nthe\nmore\nare\nyour\nchances\nof\ngetting\ninto\nthe\n*Yes \npile*\nof\nresumes.\nIf\nyou\nmake\nthis\ninfo\nhard\nto\nfind,\nyou\nmight\nend\nup\nin\nthe\n*Reject\npile*.\nMake\nsure \nto\nprovide\ntransparent\ninformation.\n2.\nRelevant\nTechnologies:\nHow\nmuch\nrelevant\nexperience\ndo\nyou\nhave?\nE.g.\nIf\nyou\u2019re\napplying\nfor\na\nFrontend\nrole\nand\nknow\na\nlittle\nof\nbackend\nstuff, \nrecruiters\nwill\nprioritize\nyou\nover\nother\napplicants\nthat\nonly\nknow\nfrontend.\n3.\nWork\nExperience:\nHow\nmuch\nrelevant\nwork\nexperience\ndo\nyou\nhave?\nDo\nyou\ncome\nacross\nas\nsomeone\nwho\nhas\nconsistently\ndelivered\nthe\nimpact?\nDon\u2019t\nmisunderstand\nthe\nwork\nexperience\nwith\nthe\nyear\nof\nexperience.\nWhile\nthe \nyear\nof\nexperience\nis\nthe\ntime\nyou\nhave\nspent\nso\nfar,\nthe\nwork\nexperience\nis\nthe \nimpact\nyou\nhave\ndelivered\nin\nthe\nentire\nindustry.\nYou\nmight\nhave\nsolved\na\ncomplex\nproblem\nin\nyour\njob/internship\nor\neven\na \nfreelance\nproject.\nBe\nthat\nbuilding\na\nhighly\nsecure\nAPI,\ncatchy\nfrontend\nwebsite, \nor\nmarvelous\nUI/UX\narchitecture.\nIt's\nall\nmeasured\nin\nyour\nwork\nexperience.\nAnother\nawesome\nthing\nyou\ncan\ninclude\nin\nthis\nis\nyour\nopen-source\nwork.\nHave \nyou\ncontributed\nto\nany\nopen-source\nproject\nwhich\nis\nfamous\nand\nwidely\nused?4.\nGround\nRules:\nWe\nneed\nto\nfollow\na\nfew\nthings\nto\nwrite\na\nprofessional\nresume.\nMake\nsure\nyour \nresume\nfollows\nthese\ntraditional\npoints:\nGood\ngrammar\nand\nNo\ntypos\nYour\nresume\nrepresents\nyou.\nIt\nhas\nto\nbe\nthe\nbest.\nIf\nyou\nallow\ntypos\nor\npoor \ngrammar,\nit\nwill\nreflect\nyour\npersonality\ncarelessly\u2014someone\nwho\ndoesn\u2019t\npay \nattention\nto\ndetails\nor\ndoesn't\nhave\na\ngood\ncommand\nof\nthe\nlanguage.\nUse\nfree\nspell-checking\ntools\nand\ngrammar\nchecking\ntools\nsuch\nas\nGrammarly.\nEven\nbetter\nis\nto\nask\npeople\nto\nre-read\nyour\nresume.\nBasic\ncontact\ndetails\"\nInclude\nyour\nemail\naddress\nand\nrelevant\ncontact\ninformation,\nlike\nphone\nnumber, \ncity\n&\ncountry\nwhere\nyou\nlive,\nat\nthe\ntop.\nKeep\nit\nshort.\nYou\ndon\u2019t\nhave\nto\nadd\nyour \nfull\naddress\nor\nother\nunnecessary\ndetails.\nDates\nin\nreverse\nchronological\norder\"\nPoint\nyour\nwork\nand\neducation\nexperiences\nwith\nprecise\ndates.\nList\nthem\nfrom\nthe \nlatest\non\nthe\ntop\nto\nearlier\nones\nunderneath\nit.\nDon\u2019t\ninclude\nphotos\nor\nnon-required\npersonal\ninformation.\nMany\npeople\nmake \nthis\nmistake.\nIncluding\nphotos\nor\npersonal\ninformation,\nlike\ndate\nof\nbirth,\nrelationship\nstatus,\nand\nreligion,\ncreates\nbias.\nIt\u2019s\nabout\nyour\nskills\nand\nnot\nlooks.\nTwo\nPages\nor\nless\"\nIt\u2019s\nnot\na\nstrict\nrule,\nbut\nwise\nto\nfollow.\nIf\nyou\u2019re\na\nfresh\ngrad\nor\nsomeone\nwith\n1\n-\n2\nyears\nof\nexperience,\nit\u2019s\nnot\nexpected \nfrom\nyou\nto\nfill\ntwo\npages.\nA\none-page\nresume\nis\nenough\nhere.\nYou\ncan\ngo\nfor\na\ntwo-page\nresume\nif\nyou\nhave\nample\nwork\nexperience\nthat \ncounts.\nStill,\nthe\nmax\nlimit\nshould\nbe\ntwo\npages.\nRecruiters\ndon\u2019t\nhave\ntime\nto\ngo \nthrough\nyour\n3-5\npage\nresume\nin\na\npile\nof\n100+\nresumes.\n5.\nSimplicity\nand\nConsistencyResumes\nthat\nare\nsimple,\nconcise,\nand\neasy\nto\nread\nwill\nbe\nread\nmore.\nWriting \nwell\nis\nan\nunderrated\nskill\nin\na\nresume.\nClear,\nneat,\nand\nconsistent\nformatting: \nUse\nthe\nsame\nformatting,\nfont\nsize,\nand\nfont\nfamily\nthroughout\nthe \nresume.\nIt\nhelps\nfor\na\nsmooth\nread.\nBullet\npoints\n\u0085\nShort\nsentences\nwith\nbullet\npoints\nare\neasier\nto\nread\nover\nlong,\noverly\nverbose \nparagraphs.\nBullets\npoints\nare\neasy\nto\nscan\nfor\nrecruiters.\nThey\nare\nused\nto\nit.\nAvoid\nsub-bullet\npoints.\nIt\nclutters\nyour\nresume,\nmaking\nit\nharder\nto\nread.\nAvoid\ndashes\n(-)\nfor\nbullet\npoints\ntoo.\nIt\nlooks\nout\nof\nplace\nand\ndoesn\u2019t\nstand\nout \nwell\nat\nfirst\nglance\nover\nbullet\npoints.\nDate\nformats\nFormat\nlike\n08/07\n-\n20/12\nis\nhard\nto\nunderstand.\nThe\nreviewer\nhas\nto\nthink\nover \nthe\ndate,\n\u201cOh,\nit\u2019s\nfrom\nthe\n8th\nof\n2007\nto\nthe\n20th\nof\n2012\u201d.\nThe\nyear\nis\nnot \ndifferentiated\nfrom\nthe\ndate.\nInstead,\ndirectly\nuse\nthe\nstandard\nformat\n\u2014\nAugust\n2007\n-\nDecember\n2012.\nEasy \nto\nread\nin\nseconds.\nDon\u2019t\nforget\nto\nstick\nwith\nthe\nsame\nformat\nthroughout\nthe\nresume.\nResume\nformat\nDo\nnot,\nI\nrepeat,\ndo\nnot\nsend\nany\nformat\nother\nthan\nPDF.\nFormats\nlike\n.doc,\n.rtf\ndisplay\ncontent\ninconsistently\non\ndifferent\nmachines.\nWhat \nyou\nsee\nmight\ndiffer\nfrom\nwhat\nthe\nrecruiter\nsees.\nYou\ndon\u2019t\nknow\nreviewers/recruiters\u2019\nmachine\nspecifications,\ndo\nyou?\nOther \nInformation\nAvoid\nthat\ntrivial\ninfo\nthat\ndoesn\u2019t\nbring\nvalue\nto\nyour\nresume.\nIf\nyou\nhave\nsomething\nimportant\nthat\ncan\nhelp\nyou\nstand\nout,\ne.g.,\nyour\nschool\n& \nachievements,\nmaybe\nyou\npresented\nas\na\nleader\nof\nyour\nbatch\nin\nyour\ncollege,\nor \nthat\nuniversity\ncompetition\u2014both\ntechnical\nand\nnon-technical\n(sports),\nadd\nit\nat \nthe\nend\nof\nthe\nresume.After\nthe\ngeneralized\npoints\nof\nthe\nresume\ncomes\nits\nstructure.\nLet\u2019s\nunderstand \nhow\nto\nstructure\na\nresume:\nThere\nare\ntwo\ntypes\nof\nsoftware\ndevelopers:\none\nwho\nhad\ntheir\nfirst\njob\nand\none \nlooking\nto\nland\na\njob.\nYou\u2019ll\nwant\nto\nstructure\nyour\nresume\ndifferently\ndepending \non\nwho\nyou\nare.\nFor\nthose\nwho\nhad\na\njob,\nyour\nwork\nexperience,\nprofessional\nskills,\nand\nthe \ntechnologies\nyou\nworked\nin\nthat\ncompany\nmatter\non\nyour\nresume.\nWhile\nfor\nthe \nnew\ngrad,\nit\u2019s\ntheir\ninternship,\nopen-source\ncontribution,\nor\na\npersonal\nproject\nthat \nhelps\nthem\njump\nout\nof\nthe\ncrowd.\nWhen\nyou\u2019re\na\nstudent\nor\nnew\ngrad,\nyou\noften\nfeel\nyou\nhave\nlittle\nto\nno \nexperience\nto\nshow.\nEven\nthough\nthat\u2019s\nthe\ncase,\nyou\ncan\nalways\nmake\nthe\nmost \nof\nwhat\nyou\nhave.\nStart\nbuilding\npersonal\nprojects.\nGo\nfor\nsome\nfreelancing \nprojects.\nApply\nfor\ninternships.\nYou\ncan\ndo\nanything\nas\nyou\u2019re\njust\nstarting!\nHere\nare\nthe\nexperiences\nthat\ncatch\nthe\neyes\nof\npeople\nreviewing\nyour\nresume \nthe\nmost,\nin\npriority\norder:\n1.\nReal-world\nwork\nsoftware\ndevelopment\nexperience\n\u0083\nIf\nyou\nhave/had\nbeen\nworking\nas\na\npart-time\nor\nfull-time\ndeveloper,\nlist\nit\nand\nyour \nachievements.\nShow\nhow\nyou\ndelivered\nand\nprogressed\nin\nyour\ncareer.\n2.\nInternships\n\u0083\nYou\ncan\nattract\nattention\nwith\nthe\ninternships\non\nyour\nresume.\nBut\ndon\u2019t\nforget\nthat \nthere\nwill\nbe\nmany\npeople\nwith\ninternships\nwhile\napplying\nto\nlarge\ntech \ncompanies.\nSpecify\nyour\ncontribution\nand\nresults\nfrom\nthe\ninternships.\n3.\nOpen\nSource\nProjects\nIf\nyou\nhave\ncreated\na\nproject\nwith\nmany\ncontributors,\nshow\nit\noff.\nIf\nyou\ncontribute\nto\na\ncertain\nopen-source\nproject\nfrequently,\nshow\nit\noff.\nIf\nyou\nhave\ntaken\npart\n&\ncontributed\nas\nan\nopen-source\ncontributor\nin\nany \norganization,\nshow\nit\noff.\nIf\nyou\nare\nnot\nin\nany\nof\nthese\ncategories,\nit's\ntime\nto\ndo\nsomething.\nFind\na\nproject, \njoin\nan\norganization\nor\ncreate\nsomething\non\nyour\nown.\n4.\nSchool/College\nDetails\nEspecially\nif\nyou\nhave\nattended\na\nhighly\nprestigious\nschool/college \nand\nhave\nhigh\ngrades,\nthis\ncan\nbe\na\nremarkable\naddon.5.\nProjects\nHave\nyou\nbuilt\nany\nproject\nwhich\nhas\nsome\ngreat\nfunctionalities?\nDo\nyou\nhave\nsomething\nthat\ncan\nshow\nthe\nimpact\nor\nmetrics\nof\nyour\nProject?\nYou\ncan\nlist\nyour\ncreative,\ncomplex\nprojects\nin\nthe\nprojects\nsection\nof \nyour\nresume.\nLink\nthe\nsource\ncode\non\nGithub\nwith\na\ngood\nREADME \n.\n6.\nTutoring\nor\nLeadership:\nHave\nyou\nbeen\nsome\npart\nof\nNGOs\nwhere\nyou\ntaught\nsome\nprogramming?\nOr\nyou\nmight\nhave\ntaken\nupon\nleadership\nin\nyour\ncollege\nwhere\nyou\nled\nyour\nbatch.\nAnything\nthat\nyou \nhave\ncollaboratively\ndone\nto\ndo\na\nproject\nor\nteaching.\nIt\nshows\nyour\nteam's\nskills\n&\nproficiency\nin\nthe\nfield.\nDon\u2019t\nmiss\nadding\nthat.\nA\nnew\ngrad\nresume\nstructure:\n1.\nExperience\n2.\nProjects\n3.\nEducation\n&\nCertification\n4.\nLanguages\n&\nTechnologies\n5.\nInterests\nFit\nall\nthese\non\none\npage.\nAs\nyou\nhave\nmore\nworking\nexperience,\na\nsecond\npage\nwill\nmake\nsense.\nHow\ncan\nnew\ngrads\nand\ninterns\ngrab\nthe\nattention\nof\nrecruiters?\nSebastian\nPrieto\nTovar\nand\nClaire\nTaylor\nhave\nrecruited\nhundreds\nof\nstudents\nand\ninterns\nfor\nUber\nand \nother\ntech\ncompanies.\nHere\u2019s\nthe\nadvice\nthey\nhave\nfor\npeople\nstarting:\nWe\nalways\ntell\nstudents\nto\nread\nthe\njob\ndescription,\nthen\namend\ntheir\nresume\naccordingly.\nAnd\nreach \nout\ndirectly\nto\nthe\nrecruiter\nwhen\nyou\ncan.\nWe\nlook\nfor\nyour\nstudies,\nrelevant\ncourses,\nand\nwhat\nyou\u2019re\nbest\nat\nwith\nstudies\non\na\nresume.\nWe\nalso\ncare\nabout\nextracurricular\nactivities,\nhackathons,\nworking\nin\nteams\noutside\nschool,\napps,\nwebsites,\nand\nother\ncool\nthings\nyou\ncreated\noutside\nschool.\nDo\nspend\nplenty\nof\ntime\npreparing\nfor\nthe\ninterviews\nthemselves.\nRead\nabout\nthe\ncompany,\nwatch\nthe\nvideos,\nlearn\nabout\nthe\nculture,\nread\nstories\nabout\nemployees,\nand\nunderstand\nthe\njob\ndescription.\nWork\nExperience\nstructure:\n1.\nWork\nExperience\nat\nor\nnear\nthe\ntop\nof\nthe\npage\nYour\ncurrent\ntitle,\ncompany,\nand\npast\nfew\nyears\nof \nexperience2.\nHave\na\nLanguages\nand\nTechnologies\nsection\non\nthe\nfirst\npage.\nList\nthings\nyou\nare\nan\nexpert\nor,\nat \nthe\nvery\nleast,\nproficient\nat\nin\norder.\nMention\nthe\nlanguages\nand\nframeworks\nthat\nthe\njob\ndescription \nmentions.\nDon\u2019t\nbother\nlisting\nnon-relevant\ntechnologies\nlike\nJira\nor\nTrello.\n3.\nIf\nyou\nhave\nspent\na\nlong\ntime\nat\none\nworkplace.List\nkey\nprojects\nyou\ndeveloped\nand\nshipped.\nYou\nwould\nlike\nto\nmention\nroles\nor\nresponsibilities\nyou\ntake\nupon\npromotion,\nif\nany.\nIt\nshows\nprogression.\nWrite\nall\nthese\nin\na\nnew\nsub-work\nsection.\n4.\nEducation\ndetails\nIt\nbecomes\nless\nimportant\nas\nyou\nprogress\nin\nyour\ncareer.\nIf\nyou\nhave\nless\nthan\n1-3\nyears\nof \nexperience,\nit\u2019s\ngood\nto\ngo\nwith.\nWith\nmore\nexperience,\nyou\nwould\nlike\nto\nfocus\nmore\non\nwork \nexperience\nthan\npast\neducation\ndetails.\n5.\nCertifications\nList\nthe\nrelevant\ncertification\nrelated\nto\nthe\njob\nindustry\nbelow\nthe\nwork\nexperience.\nMake\nsure\nthese \ncertifications\nshow\nsome\nquality.\nTrivial\ncertification,\nlike\nLinkedIn\ncertification,\ndoesn\u2019t\nadd \nsignificance.\n6.\nProjects\nThe\nmore\nexperience\nyou\nhave,\nthe\nless\nrelevant\noutside-work\nprojects\ntend\nto\nbecome.\nList\nonly \nthose\nprojects\nthat\nare\noutstanding\nin\nthe\nextra\ncurriculum\nsection.\n7.\nInterests\nPoint\nout\na\nfew\nthings\nthat\ninterest\nyou\nto\nmake\nthe\nresume\nmore\n\u201chuman.\u201d\nKeep\nit\nshort.\nAs\na\nrule\nof \nthumb,\navoid\nlisting\nyour\nexpertise\nlevel.\nInstead,\nlist\nonly\nlanguages\nyou\nfeel\nproficient\nwith,\nand\nlist \nyour\nmost\nvital\nlanguages\nand\ntechnologies\nfirst.\nThere\nis\na\nspecial\nsection\nthat\nhas\ngained\ndifferent\nopinions\nfrom\ndifferent\npeople.\nGuess?\nYes,\nit's\nthe\nsummary\nsection!\nDo\nyou\nneed\nto\nhave\na\nsummary\nsection?\nMany\nresumes\nstart\nwith\na\nsummary\nor\nprofile\nsection\nat\nthe\ntop.\nHere\nis\na\nthing:\nrecruiters\nor\nhiring \npeople\nbarely\nread\nthis\nsection\nat\nfirst\nscan.\nThey\nonly\ndo\nso\nwhen\nthey\nhave\ndecided\nto\nproceed\nwith \nyour\napplication.\nFor\nless\nexperienced\ncandidates,\nit\u2019s\nnot\nwise\nto\nhave\nthis\nsection\nunless\nyou \ncustomize\nit\nfor\njob\nlisting,\nshowing\nhow\na\ngreat\nfit\nyou\nare!\nSo,\nwhere\nthe\nsummary\nsection\ncan\nbe \nhelpful?\nSenior/Standout\nprofile:\nDescribe\nyour\nmotivation,\nwhat\nyou\u2019re\nlooking\nfor,\nand\nyour\nyear\nof\nexperience.\nRemote\nposition:\nIf\nyou\u2019re\nlooking\nfor\na\nfully\nremote\nposition,\nthe\nsummary\nsection\ncomes\nin\nhandy.\nYou\ncan\nclarify\nthat\nin\nthe\nsection.\nRole\nchange:\nIf\nyou\nare\nsomeone\nfrom\na\nnon-technical\nbackground\nwho\nwants\nto\nswitch\nto\na\ntechnical \ncareer,\nhaving\na\nsummary\nspecifying\nyour\nmotto\nwill\nbe\nvery\nhelpful.\nSo\nif\nyou\ndecide\nto\ngo\nwith\nit,\nmake\nsure\nyour\nsummary\nsection\nisn\u2019t\ntoo\nshort\nor\ntoo\nlong.\nSo\nfar,\nwe\nhave\ntalked\nabout\nthe\nresume's\ngeneral\npart\nand\nits\nstructure.\nLet\u2019s\nfocus\non\nthe\ncrucial\npart \nof\na\nresume,\ni.e.,\nWork\nExperience.How\nto\nstand\nout\nfrom\nthe\nrest\nwith\nyour\nwork \nimpact?\nWhile\nlisting\nyour\nwork\nand\nprojects,\nfocus\non\nwhat\nyou\nachieved\ninstead\nof\nwhat\nyou\ndid. \nYou\nwant\nto\nconvey\nthat\nyou\u2019re\nself-sufficient\nand\nthat\nyour\nwork\nhas\nimpacted\nthe\nteam\n&\nthen\nthe \ncompany.\nYou\u2019re\nwell\naware\nof\nyour\nvaluable\ncontribution.\nBut\nhow\nto\nstand\nout?\nThere\nis\na\nsimple \nformula\nthat\nGoogle\nrecommends:\nAccomplished\n[X]\nas\nmeasured\nby\n[Y]\nby\ndoing\n[Z]\nEffective\nresumes\nshould\ncontain\ntwo\nthings:\nResponsibilities\nand\nAccomplishments. \nTo\nstand\nout\nfrom\nthe\ncrowd,\nyou\nmust\npoint\nout\nhow\nyou\nconsciously\nand\nproactively\nadded\nvalue \nthrough\nyour\nwork.\nEdit\nyour\nachievements\nwith\nthese\npoints:\n1.\nUser\nNumbers \nQuantify\nyour\nimpact\nwherever\nyou\ncan.\nInstead\nof\nsaying,\n\u201cBuilt\na\ntool\nwidely\nadopted\nby\nthe\ncompany,\u201d\nsay,\n\u201cLed\na\nteam\nof\n3\ndevelopers\nto \nbuild\na\ndependency\ninjection\nframework\nadopted\nby\n15\nteams\nand\nall\n50+\ndevelopers\nat\nthe \ncompany.\u201d\nNumbers\ncan\nbe\nanything:\nNumber\nof\npeople\non\nyour\nteam\"\nlines\nof\ncode\"\ncode\ncoverage\npercentage\nbefore\nand\nafter\"\nnumber\nof\nusers\"\nnumber\nof\ninstalls\"\nratings\n2.\nUse\nactive\nlanguage\nShow\nwhat\nyou\nhave\ndone\nand\nhow\nyou\nhave\nbeen\nproactive.\nUse\nactive\nverbs\nlike\n\u201cled,\u201d\n\u201cmanaged,\u201d \n\u201cimproved,\u201d\n\u201cdeveloped,\u201d\nand\n\u201crolled\nout.\u201d\n3.\nSpecific\nlanguages\n&\ntechnologie\n\u007f\nMentioning\ntechnologies\nin\nyour\nwork\nexperience\nis\npowerful.\nEnsure\nthese\ntechnologies\noverlap\nwith \nthe\nlanguages\nand\ntechnologies\nyou\nmentioned\nin\nthe\nstandalone\nsection.\n4.\nKeyword\nstuffing\nResume\nfiltering\nis\ndone\nby\ndiscarding\nresumes\nthat\ndon\u2019t\nhave\nspecific\nkeywords.\nA\nworkaround\nis\nto\nread\nthe\njob\ndescription\nand\npick\nall\nthe\nnecessary\nkeywords.\nAn\nexcellent\nway\nto\nkeep\nthese\nkeywords\nwithout\nlosing\nprofessionalism\nis\nto\nstructure\nthem\nin\nthe \n\u201clanguages\nand\ntechnicals\u201d\nsection,\nwhere\nyou\nlist\ntechnologies\nyou\u2019re\nfamiliar\nwith\nor\nrelevant\nto\na \njob.\nWhen\nit\ncomes\nto\ntechnical\nexperiences,\nsome\npeople\nfalsely\nstate\nthings.\nSome\nmight\neven\nshy \naway.\nDon\u2019t\nclaim\nuntrue\nthings,\nbut\ndo\naim\nto\npaint\na\ngreat\npicture\nof\nyourself.\nHere\nare\na\nfew\ntips\nfor\nyou:\n1.\nTalk\nabout\nyourself,\nnot\nyour\nteam.\nAvoid\nusing\n\u201cwe.\u201d\nThe\nresume\nis\nabout\nyou\nand\nnot\nyour\nteam.\nThe\nhiring\nteam\nwants\nyou!\nAlways\nuse\nthe\nfirst-person \napproach.\nIn\nmost\ncases,\nyou\ncan\ndrop\nthe\n\u201cI.\u201d\n2.\nBe\nconcise\nbut\nnot\nhumble\nand\ndon\u2019t\nhide\nyour\nachievements.\nWhen\nin\ndoubt,\ninflating\nthem\non\nthe\nborderline\nwill\nhurt\nless\nthan\nhiding\nthem.\nYou\nnever\nknow\nhow \nthese\nsmall,\nimpactful\nachievements\ncan\nhelp\nyou\nstand\nout\nfrom\nthe\ncompetitive\ncrowd.3.\nSide\nprojects\n&\nOpen\nSource\ncontribution\nMention\nthese\nin\nyour\nproject\nsection\nwith\nthe\nimpact-result\ncontribution\nmodel.\nProvide\nGitHub\nsource \ncode\nlinks\nwith\na\nproper\nexplanation\nof\nhow\nyour\nproject\nworks.\nCreate\nnice\nREADMEs\ncontaining \nproject\ndetails\nwith\nthe\ninstallation\nprocess.\n4.\nExtracurricular\nactivites.\nDo\ntalk\nabout\nthese\nactivities\nat\nthe\nend\nof\nthe\nsection.\nMaybe\nyou\u2019re\na\ntechnical\nwriter\nor\ncontent \ncreator\non\nsocial\nmedia\u2014\nmention\nit.\nProvide\ntwo\nlinks\nto\nyour\npopular\narticle.\nShowing\noff\nhigh-quality \nor\nstandout\nactivities\ncan\nmake\na\ngood\nresume\neven\nbetter.\n5.\nMention\nyour\nlearning.\nLearning\nnew\nand\nvaluable\nskills\nproactively\nis\na\npositive\ntrait\nthat\nhiring\nmanagers\nappreciate.\nDo \nmention\nif\nyou\npicked\na\ntechnology\nto\nspeed\nup\na\nproject,\ngain\nknowledge,\nor\nstretch\nyourself.\n6.\nDon\u2019t\nhighlight\nnegatives\nYou\ndon\u2019t\nneed\nto\nlist\nthings\nthat\ndon\u2019t\nshow\nyou\nin\na\ngood\nbook.\nAvoid\nmentioning\nfailed\nprojects,\nlow \nGPA,\nCGPA\nscores,\netc.\nRemove\nitems\nthat\ndon\u2019t\nconvey\nyou\u2019re\na\ngood\nfit\nfor\nthe\nrole.\nWe\nhave \nmostly\ncovered\nwhat\nshould\ngo\non\na\nresume.\nYet\npeople\nmake\nsome\ntrivial\nmistakes.\nWhat\nare\nthese? \nLet\u2019s\ncheck\nthat\nout!\nCommon\nMistakes\n1.\nCreating\nhard\nto\nscan\nresumes:\nMulti-column\nresumes\nare\nhard\nto\nscan\nfor\nmanagers.\nSimple\nformats\nare\nbetter.\nGo\nutmost\nfor\na \ntwo-column\nlayout.\n2.\nToo\nmuch\nbolding\nA\nresume\nshould\nhave\nminor\nand\nconsistent\nbolding\nfor\ncritical\nparts,\nsuch\nas\ndates,\ntitles,\nand \ncompanies.\nDon\u2019t\nbold\nrandom\nparts\nthat\ndon\u2019t\nmake\nsense\nat\nall.\n3.\nFlashy\nresumes\nA\ndeveloper's\nresume\nis\n95%\nabout\nthe\ncontent\nand\n5%\nabout\nthe\nstyle.\nIt\nworks\nif\nyou\u2019re \napplying\nfor\na\nUI/UX\nrole\nas\nit's\nmore\nabout\nstyle\nwith\ncreativity.\n4.\nInconsistent\nformatting\nPay\nattention\nto\nthe\nfine\ndetails.\nKeep\neverything\nconsistent.\n5.\nSloppy\nphrases\nAvoid\nunprofessional\nlanguage.\nDon\u2019t\nuse\netc.,\nso\non,\netc.\n6.\nUsing\ninternal\nacronyms\nand\njargon\nAvoid\nusing\ninternal\nproject\nnames\nthat\npeople\noutside\nthe\ncompany\ndon\u2019t\nunderstand.\nE.g.,\n\u201cI\ndid\nFD\nin\naplha2.0\nproject\u201d.\nA\nrecruiter\ncan\u2019t\nguess\nwhat\nyour\nFD\nis\nin \naplha2.0.\n7.\nNot\nreflecting\non\nthe\njob\nand\nnot\ntailoring\nthe\nresume\nfor\nthe\nposition\nSay\nif\nyou\nknow\nboth\nfrontend\nand\nbackend\nbut\napplying\nfor\na\nspecific\nfrontend\nrole.\nYou\nwill\nwant \nto\npresent\nyourself\nas\nsomeone\nwho\nknows\nthe\nfront\nend\nenough.\nBackend\nis\na\nsidekick\nhere. \nAlways\nkeep\nthe\njob\nposition\nin\nmind,\nthen\ntailor\nyour\nresume.\n8.\nUsing\ncliches\nover\nstatements\nbacked\nby\nevidence\nWhat\ndoes\nthe\nfollowing\nsentence\ntell\nyou\nabout\nyou?\n\u201cI\nam\na\nteam\nplayer\nand\na\nfast\nlearner\nwho \ncan\nhit\nthe\nground\nrunning.\u201d\nFrom\nthe\npoint\nof\nview\nof\nthe\nrecruiter,\nit\ndoesn't\nprovide\nanyinformation.\nIt\u2019s\nnot\nbacked\nby\nany\nfact\nor\nevidence\nthat\ncan\nstate\nit.\nLet\nyour\nactions\nspeak\nfor \nthemselves\n9.\nBeing\ntoo\nverbose\nAvoid\nblocks\nof\ntext\nor\nlong\nsentences.\nIt\ndoesn\u2019t\nhelp\nfor\nan\neasy\nread.Keep\nit\nshort\nand\nup\nto \nthe\npoint\n10.\nUnnecessary\ndetails\nDo\nnot\nadd\nphotos\nor\nirrelevant\ncontact\ninformation.\nIf\nnot\nneeded\nor\nnot\nin\nthe\njob's\ncontext,\ndo\nnot\nmention\nspoken\nlanguages.\nMost\ncompanies\nwill \nonly\ncare\nabout\nyour\nproficiency\nin\nEnglish.\n11.\nSelf-rating\nyour\nskill\nlevel\nDo\nnot\nrate\nyour\nproficiency\nin\nany\nlanguage\nor\ntechnology\nusing\npercentages\nor\nscores.\nIt\u2019s\nnot\nnecessary .\nNo\none\nknows\nanything\nabout\na\nprogramming \nlanguage/technology .\n12.\nNon-clickable\nor\nfull\nlinks\nCross\nverify\nif,\nby\nmistake,\nyou\nhave\nadded\nnon-clickable\nlinks.\nAdd\nproper\nlinks\nto\nGitHub, \nwebsites,\nand\nother\nmedia.\nRecruiters\nwill\nnot\ncopy-paste\nthe\nname/username\nto\nsee\nit.\nMake \nclickable\nlinks\nand\nhide\nthe\nfull\nURL\nbehind\na\nname\nthat\ndescribes\nwhat\nthe\nlink\nis\nfor.\n13.\nStaleLinking\nIt\u2019s\nbetter\nto\nleave\nit\nempty\nrather\nthan\nlinking\nto\nstale\nor\nnot-\ntouched-in-decade\nwebsites\nor\nGitHub\nprofile\nlinks.\nLink\nonly\nif\nthey\nare\nup\nto\ndate.\nSo\nmany\nguidelines,\nand\nyou\ncan\nstill\ncommit\na\nmistake\nor\ntwo,\nno\nmatter\nwhat.\nTo\nrecap,\nconsider\ndoing\nmost\nof\nthese\nto\nmake\nyour\nresume\nbetter:\nWrite\ntwo\ndifferent\nresumes,\nthen\ncreate\na\nthird\none\nfrom\nthe\nbest\nparts\nof\nthese\ntwo.\nTry\nto\nestimate\nthe\nimpacts\nof\nyour\nproject.\nA\nrough\nestimation\nis\nbetter\nthan\nno\nspecific.\nDo\ngrammar\ncheck,\nnot\njust\nspell-check.\nAsk\nfriends\nor\nfamily\nto \nproofread.\nSeek\nout\nfeedback\non\nvarious\ncommunity .\nDo\na\nkeyword\ncheck\nfor\nyour\nresume. \nManually\nor\nwith\nthe\nhelp\nof\nautomated\ntools.\nDifferent\nLevels,\nDifferent\nPaths\nDepending\non\nhow\nmuch\nexperience\nyou\ncarry,\nyou\nwill\nwant\nto\nfocus\non\ndifferent\nareas\nof\nresumes: \nResume\nfor\nStudents\nIf\nyou\u2019re\nstill\na\nstudent,\nknowing\nfundamentals\nis\nan\nessence.\nWhile\nlearning\nsoftware \ndevelopment,\nyou\nwould\nwant\nto\nfocus\non\nthese\nthings\nfor\na\nfuture\njob\nsearch:\nInternships\nOne\nof\nthe\nbest\nexperiences\nyou\ncan\nhave\nas\na\nstudent\nis\nworking\nas\nan\nIntern.\nApply\nin\nnatural\nproblem-solving\nindustries.\nCampus\nActivities\nYour\nuniversity/college\nmight\noffer\nplenty\nof\nopportunities\nto\nwork\nwith\na\nprofessor,\nlead\na\nlaboratory,\narrange\nevents,\netc.\nMake\nthe\nbest\nof\nthese\nTimes.\nYou\nwill\nget\nhands-on\nexperience\nmentoring/leading\nothers\nor\ntaking\nthe\ninitiative.University\nProjects\nYou\nwill\nundoubtedly\nhave\nclass\nprojects\nor,\nto\nthe\nleast,\nthe\nfinal\nyear\nProject.\nConsider\nputting\nextra\ntime\nand\neffort\ninto\nthese\nprojects.\nPublish\nthem\nso\nthat\nanyone \ncan\ndownload\nor\ntry\nthem.\nUsing\nGitHub\nwill\nbe\nsuper\nbeneficial.\nIf\npossible,\nbuy\nyour\ndomain. \nThis\nmight\ncost\nyou\nbucks,\nbut\nit\u2019ll\nbe\nworth\nit\nto\nshow\nthe\ninterviewer\nwhat\nyou\nhave.\nClearly,\nit \nwill\nshow\nyou\nas\nsomeone\nwho\nknows\ndeployment\nto\nthe\nleast. \nResume\nfor\nBootcamp\nGrads\nAs\na\nBootcamp\ngrad\nwho\nhas\nlikely\nlearned\nbasic\nsoftware\ndevelopment\nskills,\nyour\ntime\nspent \nstudying\nthese\nwill\nbe\nshorter\nthan\ncollege/university\nstudents.\nIt\nwould\nbe\nbest\nto\ncompete\nwith \nthese\ngraduate\npeople\nand\nother\nBootcamp\ngrads.\nBut\nno\nworries\nif\nyou\nhave\nthe\ncapstone \nproject\non\nyour\nresume.\nSo\nwhat\ndo\nyou\nneed\nto\nfocus\non?\nProjects\nIt\u2019s\nuniversal\nfor\neveryone\nlooking\nfor\na\njob.\nDevelop\nas\nmany\nprojects\nas\nyou\nwant,\nbut\nhave\nthat \none\ngreat\nproject!\nTo\nstand\nout,\nyou\nwill\nwant\nto\nshowcase\nbetter\nprojects.\nFollow\nthese \ntips:\n\u0301\nGood\nREADMEs\nAim\nto\nwrite\na\nREADME\nwith\na\ngood\nsummary:\nscreenshots,\ndetails\non\nhow\nto\nrun\n&\ntest.\nContribute\nto\nother\nopen-source\nprojects\nFind\nprojects\nwhere\nyou\ncan\ncontribute.\nTake\npart\nin\nthe\nopen-source\nprograms\nI\nmentioned \nearlier.\nIf\nyou\ncan\nmerge\na\npull\nrequest,\nyou\ncan\nclaim\nthat\nyou\nhave\ncontributed\nto\na\nproject\nused \nby\nmore\nthan\na\ncertain\nnumber\nof\ndevelopers.\nTurn\ninterview\nprojects/challenges\nor\nlearnings\ninto\npublic\nprojects\nYou\ncan\ndo\nmore\nthan\nsubmit\nprojects\nor\ndo\ncoding\nchallenges\nfor\na\njob\ninterview.\nWithout\ncaring \nabout\nthe\nresults,\ncontinue\nworking\non\nthese\nprojects/challenges\nand\nsubmit\neven\nbetter-polished \nsolutions\nonline\non\nGitHub.\nIf\nyou\ncannot\nreach\nthe\nnext\nround,\nask\nfor\nfeedback,\nand\nbuild\nthat \nfeedback\ninto\nthis\nproject.\nIf\nyou\ndo\neven\nbetter,\ndon\u2019t\nhesitate\nto\nsend\na\ncold\nemail\nwith\nthese \nlatest\nchanges.\nYou\nmight\nget\nanother\nchance\nto\ndo\nit\nbetter.\nNo\none\nknows\nunless\nyou\ntry.\nFreelance\nprojects\nTry\nfreelancing\nonce\nin\nlife\nwhile\nyou\u2019re\nin\nsearch\nof\na\njob.\nA\nfreelance\nproject\non\nthe\nresume\ncan \ntell\na\nlot.\nLanding\na\ngood\nclient\nat\nfirst\ncan\nbe\nchallenging.\nIf\nyour\ngoal\nis\nto\nget\nexperience,\nkeep \nthe\nfocus\non\nfinding\nprojects\nthat\ncan\nadd\nvalue\nto\nyour\nportfolio.\nPublish\nscreenshots\nand\ncode \nsnippets\nof\nthe\nwork\non\nthe\nportfolio\npage\nafterward.\nYou\ndon\u2019t\nneed\nto\ndisclose\nhow\nmuch\nyou \ngot\npaid.\nThe\ngoal\nis\nto\nshow\nyour\nknowledge.\nResume\nfor\nCareer\nChangers\nSummary\nHave\na\nsummary\nsection\nthat\nexplains\nyour\nmotivation/reason\nfor\na\ncareer\nchange.\nWhen\nyou \nhave\nchanged\ncareers\nfrom\nother\nprofessions\nto\nsoftware\ndevelopment,\nmost\nof\nthe\nadvice\nis\nthe \nsame\nas\nfor\na\nBootcamp\ngrad\nyou\nmight\nhave\nsome\ntraining\nbehind\nyou.\nHere\nis\nadvice\nfor\nyou:\nLanguages\n&\nProjectsList\ntowards\nthe\ntop\nof\nthe\nresume,\nshowing\nthat\nyou\nhave\nhands-on\nsoftware\ndevelopment \nexperience.\nFollow\nthe\nguidelines\nfor\nlisting\na\nproject,\ni.e.,\nsource\ncode\nlink,\ngood\nREADMEs, \ndemo\nlink,\netc.\nPast\nwork\nexperience\nKeep\nit\nconcise\nand\nhave\na\none-sentence\nsummary\nof\nthe\njob.\nFocus\non\nany\npoints\nor\nskills \ntransferable\nto\nsoftware\ndevelopment,\ne.g.,\nproactive\nlearner,\nteam\nleader,\netc.\nOne-page\nresume\nTry\nto\nfit\non\none\npage.\nDon\u2019t\nover-share\npast\nexperiences\nif\nthey\naren\u2019t\nbeneficial\nin\nthe\nsoftware \nfield.\nResume\nfor\nCareer\nBreaks\nYou\nmight\nhave\ngone\nfor\nmany\nmonths\u2014or\nyears\u2014without\na\njob\nor\nwork\nin\na\nsoftware\nfield.\nIt \nmight\nbe\nwhy\nyou\nwere\npursuing\nsomething,\nor\nyou\nwanted\nto\ntake\na\nbreak.\nEither\nway,\nthere\u2019s\na \ngap\nin\nyour\nresume.\nHow\ndo\nyou\npresent\nthis?\nCareer\nbreak\nyears \nYou\ndon\u2019t\nneed\nto\nexplain\nthe\nbreaks\nthat\nhave\nhappened\nmore\nthan\na\nfew\nyears\nago\n\u2014\n4\nor\n5 \nyears.\nRecruiters\nor\nhiring\nmanagers\nwill\nrarely\ncare\nabout\nit.\nFor\nrecent\ncareer\nbreaks,\nuse\nyour \ngood\njudgment\non\nwhether\nyou\nwant\nto\nadd\nit.\nTell\na\nstory\nof\nyour\ncareer\nbreak.\ne.g..,\nDue\nto \nCOVID-19,\nI\ndecided\nto\ntake\na\nbreak\nto\nspend\nmore\ntime\nwith\nmy\nfamily.\nHow\nto\naddress\na\ncareer\nbreak\non\nyour\nCV\nA\ncareer\nbreak\nis\ngenerally\nde\ufb01ned\nas\nany\ntime\nyou\u2019ve\nbeen\no\ufb00\nwork\nfor\nan\nextended\nperiod\n(of\ntypically\nmore\nthan\nthree\nmonths)\nthat\nhas\nbeen\nfor\nany\nreason\nother\nthan\nredundancy.\nIt\ncan\ncover\nillness,\ntravel,\na\nsabbatical\n,\nhaving\nchildren,\ncaring\nfor\nrelatives\nand\nmany\nother\nreasons.\nAs\na\ngeneral\nrule,\nyou\nshould\nusually\nexplain\ngaps\nin\nyour\nemployment\nhistory\nand\nbe\nhonest\nabout\nwhy\nyou\nwere\nout\nof\nwork\nas\nemployers\nmay\nuncover\nany\nexaggerations\nif\nthey\ncall\nprevious\nemployers\nfor\nreference.\nThe\nreal\ntrick\nis\nhow\nyou\nposition\nthe\ncareer\nbreak.\nBy\nputting\na\npositive\nspin\non\nthe\ntime\no\ufb00,\nmany\nemployers\nwill\nbe\nimpressed\nand\nmore\nthan\nwilling\nto\naccept\nit.\nMore\nthan\nanything,\nthey\nwant\nreassurances\nthat\nyou\nwon\u2019t\nbe\nleaving\nthe\nworkforce\nagain\nsoon\nand\nthat\nyou\u2019re\nmotivated\nto\nget\nback\ninto\nemployment.\nWhere\nto\naddress\nthe\ncareer\nbreak\non\nyour\nCVW hile\nit\u2019s\nalways\nimportant\nto\naddress\nyour\ncareer\nbreak,\nyou\ndon\u2019t\nneed\nto\ngo\ninto\ngreat\ndetail\nabout\nthe\ntime\no\ufb00.\nIn\nmost\ncases,\nit\ncan\nbe\nsummarised\nin\na\nshort\nsentence.\nBut\nwhere\nshould\nit\nbe\nmentioned?\nThis\nwill\ndepend\non\nhow\nrecent\nthe\ncareer\nbreak\nwas,\nand\npossibly\nyour\nmotives\nfor\ntaking\nit.\n\u25cf\nIf\nyou\nare\non\nyour\ncareer\nbreak\nright\nnow:\nSay\nyou\u2019ve\nbeen\nout\nof\nwork\ncaring\nfor\na\nrelative\nfor\nthe\nlast\nsix\nmonths,\nyou\u2019ll\nwant\nto\nexplain\nthis\nperiod\nout\nof\nwork\nin\nyour\nexperience\nsection\nas\nwell\nas\nin\nyour\npersonal\nstatement\n\u25cf\nIf\nyour\ncareer\nbreak\noccurred\nin\nthe\nlast\none\nto\n\ufb01ve\nyears\nbut\nyou\u2019re\nemployed\nnow:\nyou\nneedn\u2019t\nmention\nit\nin\nyour\npersonal\nstatement,\nonly\nin\nyour\nexperience\nsection\n\u25cf\nIf\nit\nwas\na\nlong\ntime\nago:\nDid\nyou\ntake\nsix\nmonths\nto\ngo\nbackpacking\naround\nIndia\nin\n1995?\nChances\nare,\nyou\nprobably\nneedn\u2019t\nmention\nthe\ncareer\nbreak\nat\nall\nHow\nto\ndescribe\nthe\ncareer\nbreak\nAs\nnoted\nabove,\nyou\nneedn\u2019t\ngo\ninto\ngreat\ndetail\ndescribing\nthe\ncareer\nbreak\n\u2013\nno\nmore\nthan\na\nline\nor\ntwo.\nThe\nkey\nthing\nhere\nis\nto\nemphasise\nthe\npositives\nand,\nif\nappropriate,\ndescribe\nany\nnew\nskills\nlearnt\nor\ncourses\ntaken.\nIt\u2019ll\nalso\nbe\nimportant\nto\nprovide\nsome\nreassurance\nthat\nyou\u2019re\nnot\nplanning\nanother\ncareer\nbreak\nany\ntime\nsoon.\nAgain,\nlet\u2019s\nlook\nat\nsome\nexamples:\n\u25cf\nYou\nwent\ntravelling:\n\u201cI\nful\ufb01lled\nmy\nlife-long\ndream\nof\ntravelling\nthrough\nSouth\nAmerica\nfor\nsix\nmonths\nwhere\nI\nimproved\nmy\nSpanish\nand\ngained\nan\nunderstanding\nof\ndi\ufb00erent\ncultures\u201d\n\u25cf\nYou\nwanted\na\nfresh\nstart:\n\u201cI\nchose\nto\ntake\ntime\no\ufb00\nwork\nto\npursue\nmy\ninterest\nin\npainting\nand\nhad\nthe\ntime\nto\ndecide\non\na\nnew\ncareer\npath\nthat\nreally\n\ufb01ts\nmy\npersonal\ngoals\u201d\u25cf\nYou\nwere\nill:\n\u201cI\ntook\ntime\no\ufb00\nwork\ndue\nto\na\nlengthy\nillness,\nbut\nthe\ntime\no\ufb00\nallowed\nme\nto\nfully\nregain\n\ufb01tness\nfor\nthe\nlong-term\nand\nI\nbecame\ninvolved\nin\nvolunteering\nat\na\nlocal\ncharity\nshop\nto\nget\nme\nback\ninto\nthe\nswing\nof\nwork\u201d\n\u25cf\nYou\nwere\ncaring\nfor\nsomeone\nelse:\n\u201cI\ntook\ntime\no\ufb00\nto\ncare\nfor\nmy\nbrother\nwho\nhas\nnow\nmade\na\nfull\nrecovery\u201d\nFormatting\ncan\nhelp\nAddressing\na\ncareer\nbreak\nis\nall\nabout\naccentuating\nthe\npositives.\nW hile\nyou\ndo\nhave\nto\nmention\nyou\u2019ve\nbeen\no\ufb00\nwork,\nyou\ncan\nformat\nyour\nCV\nin\nsuch\na\nway\nthat\nrecruiters\nfocus\non\nother\nparts\nof\nyour\nemployment\nand\npersonal\nhistory.\nOne\noption\nis\nto\ndescribe\njobs\nin\nterms\nof\nthe\nyears\nyou\nworked\nthere,\nrather\nthan\nexact\nmonths.\nFor\nexample:\n\u201cMarketing\nCompany:\n2009-2010\u201d,\nrather\nthan\n\u201cMarketing\nCompany:\nNovember\n2009-February\n2010\u201d:\n\u25cf\nPerhaps\nduring\nyour\nearly\ncareer,\nyou\nhad\na\nfew\nperiods\nout\nof\nwork\nfor\npersonal\nreasons,\nbut\nsince\nthen\nhave\nfollowed\na\nstandard\ncareer\npath.\nYou\nmay\njust\nwant\nto\ndescribe\nthose\nearly\nyears\nin\nthis\nway.\nIf\nyou\u2019ve\nhad\na\nmore\nstable\ncareer\never\nsince,\nit\u2019s\nprobably\nnot\nnecessary\nto\ndraw\ntoo\nmuch\nattention\nto\nthat\nearlier\nspotty\nperiod.\nAlternatively,\nyou\nmight\nwant\nto\ncreate\na\n\u2018skills\u2019\nor\n\u2018themed\u2019\nCV\n\u2013\nas\nopposed\nto\nthe\nmore\ncommon\nchronological\nformat:\n\u25cf\nMaybe\nfor\nthe\nlast\nten\nyears\nor\nso\nyou\nhad\nthe\nopportunity\nto\nlive\nin\nthe\nsouth\nof\nFrance\nand\ndidn\u2019t\nneed\nto\nwork\nmuch\nbut\nare\nnow\nkeen\nto\nreturn\nto\nthe\nUK\nand\nrestart\nyour\ncareer.\nCreating\na\nskills-based\nCV\ncould\nbe\nreally\nhelpful\nhere.\nTake\nthe\ntime\nto\nthink\nhow\nthe\nskills\nyou\u2019ve\nlearnt\nwhile\nout\nof\nwork\ncould\nbe\nreapplied.\nFor\ninstance,\nyou\u2019d\nlikely\nbe\n\ufb02uent\nin\nFrench\nby\nnow\nand\ncapable\nof\nworking\nin\na\nmultilingual\nenvironment.\nOr\nyou\nmight\nbe\nfamiliar\nwith\nFrench\ntax\nlaw\nor\nthe\ncountry\u2019s\nproperty\nmarket,\nknowledge\nthat\nwouldbe\nvery\nhelpful\nfor\nall\nsorts\nof\nbusinesses.\nBy\nmaking\nyour\nskills\nstand\nout,\nemployers\nwill\nunderstand\nthe\nvalue\nyou\ncould\nbring\nthem\nand\nlook\npast\nthe\ntime\nout\nof\nformal\nemployment.\nExample\nSummary\nSection\nfor\nCareer\nBreak:\nI\nam\na\ncon\ufb01dent\nand\ncapable\no\ufb03ce\nmanager\nwith\nover\nten\nyears\u2019\nexperience\nin\na\nrange\nof\nbusinesses.\nI\nhave\na\nsolid\nunderstanding\nof\nall\ncore\no\ufb03ce\nmanagement\nresponsibilities,\nI\nam\nfriendly\nand\napproachable,\nand\nI\nlearn\nnew\nskills\nfast.\nI\nam\nnow\nreturning\nto\nthe\nworkforce\nafter\na\nperiod\nof\nabsence\nwhile\nproviding\ncare\nfor\na\nrelative,\nbut\nam\nnow\nready\nand\nmotivated\nto\nrestart\nmy\ncareer.\nFor\nthe\npast\ntwo\nmonths\nI\nhave\ntaken\non\nvolunteering\nwork\nas\na\npart\ntime\no\ufb03ce\nmanager\nat\na\nlocal\ncharity\nto\nrefresh\nmy\nskills.\nResume\nfor\nSenior\nor\nabove \nEngineers\nThe\nmore\nexperienced\nyou\nare,\nthe\nmore\nlikely\nyou\nstand\nout\nbased\non\nyour\nexperience\nand\npast \ntitles.\nFor\nsomeone\nhaving\nexperience\nof\nover\n7-8\nyears,\nyour\nchallenge\nwill\nbe\nto\nkeep\nyour \nresume\nrelevant\nto\nthe\nposition\nyou\u2019re\napplying\nfor:\nCareer\nbreak\nyears\nthe\nexperience\nyou\ncarry,\nthe\nhiring\nteam\nwill\nlook\nforward\nto\nthis\nsummary\nsection\nto\nknow\nabout \nyour\nmotivation\nbehind\napplying\nto\ntheir\nfirm.\nSoft\nAchievements\nMention\nsoft\nachievements\n\u2014\nmentoring\njunior\ndevelopers,\nleading\na\nteam,\nand\nother\nactivities \nwhere\nyou\nhelped\nothers.\nImpact\n&\nInfluence\nOn\ntop\nof\ncompany\nwork,\nyou\ncan\nmention\nwhat\nkind\nof\nimpression\nyou\nmade\nwith\nyour\nwork. \nMention\nwhat\nteams\nor\norganizations\nyou\ninfluenced\nfor\nspecific\noutcomes.\nEducation\nAs\nyou\ncontinue\ngaining\nmore\nexperience,\neducation\nwill\nhave\nless\nvalue.\nYou\ncan\nmove\nthe \neducation\nsection\nto\nthe\nsecond\npage.\nOnly\nkeep\nstandout\ndetails\nin\none\nline\nor\ntwo.\nResume\nfor\nTech\nLeads\nYou\nmight\nhave\ngone\nfor\nmany\nmonths\u2014or\nyears\u2014without\na\njob\nor\nwork\nin\na\nsoftware\nfield.\nIt \nmight\nbe\nwhy\nyou\nwere\npursuing\nsomething,\nor\nyou\nwanted\nto\ntake\na\nbreak.\nEither\nway,\nthere\u2019s\na \ngap\nin\nyour\nresume.\nHow\ndo\nyou\npresent\nthis?Follow\nthese\nguidelines\nwhen\napplying\nfor\nthe\ntech\nlead\nposition:\nShowcase\nhow\nyou\nhelped\nteams. \nHiring\nmanagers\nhire\ntech\nleads\nwhen\nthey\nfeel\ntheir\nteam\nis\nbehind\non\ndelivery,\nstruggling\nwith \nhigh\nturnover,\nor\ndelivering\npoor\nquality.\nAs\na\ncandidate,\nyou\nwill\nwant\nto\nshowcase\nthese\npoints \nwhere\nyou\nhelped\nyour\nteam\nto\nexcel,\nincreased\nspeed,\nimproved\ncode\nquality,\nor\nrepaired \nstakeholder\nrelationships.\nGive\nexamples\nof\nhow\nyou\nmade\nyour\nteam\nsuccessful.Y ou\nwill\nbe \nexpected\nto\nhave\na\ntrack\nrecord.\nMake\nit\neasier\nto\nfind.\nSpecifics\nand\nContext \nSpecify\nthe\nsize\n&\nmakeup\nof\nthe\nteam\u20143\nfrontend,\n2\nbackend\n&\n1\nQA\nengineer\u2019s\nteam. \nMention\nyour\nmajor\ntechnical\nchoices\ntaken\nwithin\nthe\nteam. \nOutcomes\nand\nActivities \nPlease\ntalk\nabout\nthe\ndaily\nscrums\nand\nhow\nyou\nmanaged\nto\nmake\nthem\nhappen\nwithin\nthe \ndeadlines.\nInclude\nproof\npoints\nfor\ndelivery;\ne.g.,\nmanaged\na\nteam\nof\nx\ndevelopers\nthat\ndelivered \nProject\nX\non\ntime\nand\nwithin\nbudget.\nResume\nfor\nEngineering\nManagers\nMost\npercentages\nof\nthe\nguidelines\nshared\nfor\ntech\nlead\npositions\napply\nto\nthe\nrole\nof\nengineering \nmanagers.\nBut\nyou\nwould\nlike\nto\nprovide\nmore\ndetails:\nTell\na\nstory\nabout\nhow\nyou\nachieved\nresults,\nimproved\nyour\nteam\u2019s\nperformance,\n&\nhow\nmade \nyour\norganization\nbetter.g\nBe\nfamiliar\nwith\nthe\nvalues\nof\nthe\ncompany\nyou\u2019re\napplying\nfor.\nDo\nyour\nresearch\non\nthe \norganization\u2019 s\nculture.g\nTalk\nabout\nthe\ntype\nof\nchallenges\nyou\nare\nfit\nto\nsolve.\nPoint\nout\nwhat\nkind\nof\nproblems\nmade\nyou \nachieve\nyour\nbest\nresults=\nGet\nfeedback\nfrom\nyour\npeers\nor\nfriends.\nLinkedIn\nAlong\nwith\nyour\nresume,\nyou\nwill\nwant\nto\nget\nready\nother\nthings:\nLinkedIn,\nGitHub\nProfile,\nor \ncover\nletter.\nLet\u2019s\ntalk\nabout\nhow\nto\ncreate\na\nbetter\nLinkedIn\nprofile:\nResumes\nand\nLinkedIn\nprofiles\nare\nlike\nthe\nyin\nand\nyang.\nYou\ndirectly\napply\nwith\na\nresume,\nand \nopportunities\ncan\ncome\nand\nfind\nyou\nwith\nyour\nLinkedIn\nprofile.\nIt\u2019s\nsmart\nto\ninvest\nequally\nin \nboth.\nHeadline\nSet\na\nheadline\nthat\nrepresents\nwhat\nyou\nwant\nto\nbe\nfound\nfor.\nIt\nshould\nsummarize\nthe\nmessage \nyou\nwould\nwant\nto\nconvey.\nIf\nyou\nset\nnothing\non\nyour\nprofile,\nyour\ncurrent\nposition\nwill\nappear.\nConsider\nadding\nthe\n\u201c|\u201d\nseparator\ncharacter\nto\nadd\nmore\ninformation\nto\nyour\nheadline.\nFor \nexample,\n\u201cFrontend\ndeveloper\nwith\n2\nyears\nof\nexperience\n|\nJavaScript,\nExpress,\nMongoDB, \nNext.js\u201d.\nA\ntailored\nheadline\nwill\nrank\nyour\nprofile\nhigher\nwith\nkeyword\nsearches\nthat\ngrab\nthe \nrecruiters\u2019\nattention.Current\nPosition\nDescribe\nyour\ncurrent\nrole\nproperly.\nFor\nexample,\nif\nyou're\nleading\na\nteam\nof\nfrontend\ndevelopers, \nyou\nshould\nwrite\n\u201cFrontend\nLead\u201d\nor\n\u201cFrontend\nTeam\nLead\u201d.\nAnything\nthat\nbest\ndescribes\nyour \nrole.\nIf\nyou\ndon\u2019t\nhave\na\ncurrent\njob,\nLinkedIn\nwill\nrank\nyour\nprofile\nlower.\nMake\nsure\nnot\nto\nleave \nyour\nheadline\nempty,\neven\nif\nyou\ndon\u2019t\nhave\na\nposition.\nYou\ncan\nhighlight\nthe\nskills\nyou\nknow\nin \nthat\ncase.\nSummary\nMention\nkeywords,\ntechnologies,\nor\nlanguages\nyou\u2019re\nfamiliar\nwith.\nGo\nfor\na\nlonger\nsummary\nthat \nbest\ndescribes\nyour\nvalues\nor\nmotivation\nin\nthe\nfield.\nYou\ndon\u2019t\nhave\nto\nfit\neverything\non\na\npage \non\nLinkedIn.\nIn\nfact,\nwith\nmore\ncontent,\nyou\ncould\nrank\nhigher\nin\nsearch\nresults.\nSo\nit\u2019s\nfine\nto\nbe \nverbose\nhere.\nProfessional\nphoto\nA\nprofessional\nphoto\nis\none\nwhere\nyour\nface\ncan\nbe\nseen\nproperly\nwithout\nno\none\nelse\nin\nthe \npicture.\nWork\nExperience\nOmit\nwork\nexperience\nthat\ndoesn\u2019t\nsupport\nyour\nprofessional\ncareer.\nYour\nprofile\nshould\ntell\na \ngood\nstory\nof\nyour\nprofessional\nside.\nRemove\npositions\nthat\ndon\u2019t\nstrengthen\nthis\nimage.\nOpen\nfor\nwork\nDo\nnot\nadd\n\u201cLooking\nfor\nopportunities\u201d,\n\u201copen\nfor\na\nnew\nrole\u201d\nor\nsomething\nsimilar\non\nyour \nheadline.\nIt\ndoesn\u2019t\nadd\nmuch\nvalue.\nInstead,\nit\nwill\ntake\nthe\nspace\nthat\nyou\nmight\nhave\nused\nto \npresent\nyourself\nor\nhighlight\nyour\nskills.\nYou\ncan\nactivate\nthe\noption\ngiven\nby\nLinkedIn\nto\nlet \nrecruiters\nsee\nwhether\nyou\u2019re\nopen\nfor\nwork\nor\nnot.\nNetworking\nConnect\nwith\nmore\npeople.\nReact\nout\nto\nthe\ngreat\nminds!\nThe\nclose\nyou\nare\nconnection-wise\nwith \nthe\nrecruiter,\nthe\nhigher\nyour\nprofile\nwill\nrank.\nLocation\nLocation\nis\noften\na\nfilter\nthat\nrecruiters\nuse.\nIf\nyou\u2019re\nmoving\nto\na\ndifferent\nlocation,\nyou\ncan \nupdate\nit.\nIn\ncase\nyou\u2019re\nlooking\nfor\nremote\npositions,\nyou\ncan\nspecify\nthat."} |