What do you guys use to build your CVs? Do you automate it in any way or just use something like Google Docs? I’d be interested to know.

Personally I’ve been using rendercv for a while and I can’t imagine going back to doing it manually. However, I think I might need some more flexibility. Been struggling to get any interviews so I’ve been doing what I can to experiment with my CV. If any of you have a good typst template they’ve actually used to land a role I would love to steal borrow it.

  • JeeBaiChow@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    4 days ago

    Hey chatgpt, write me a resume for a <insert job description> that will likely fly with a 6B publicly traded company. Include details about <insert field expertise here> and wors it like Tony stark wrote it.

    • blargh513@sh.itjust.works
      link
      fedilink
      arrow-up
      4
      ·
      4 days ago

      Well, companies are using ai to delete our resumes so I’m all for blasting them with fully automated ai submissions.

      Just keep submitting and iterating, eventually one will get through.

      In the end, we are battling HR on our turf. If we can’t beat these clowns, we deserve to be jobless.

  • ambitiousslab@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    4 days ago

    I write my CV in Markdown (just headers and bullet points), and then use pandoc to generate a pdf. Very easy and straightforward!

    This has landed me interviews although not hired (I think that’s down to me, not the format of my CV 😅)

    pandoc \
    --variable title-meta:"ambitiousslab - CV" \
    --variable author-meta:"ambitiousslab <ambitiousslab@example.org>" \
    --variable lang:"en-GB" \
    --variable geometry:margin=1cm \
    --variable colorlinks:true \
    --variable pagestyle=empty \
    cv.md \
    -o ambitiousslab-cv.pdf
    
      • traches@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 days ago

        Eh, I try to keep this username separate from my real name. It’s not too hard though, you just need ‘@media print {‘. Set display none on stuff like the navbar and footer, and you also need to think about page breaks and such, there are guides.

        Browser dev tools can simulate print styles, and you can preview with the regular print preview. To get consistency across browsers you probably want to set a definite width, so the sizing stays the same.

  • HaraldvonBlauzahn@feddit.org
    link
    fedilink
    arrow-up
    1
    ·
    3 days ago

    Using pdflatex and a tree of resumes stored with git, one tailored to each application. And a lot of proofreading by other people. Get feedback on what you prepare!

  • ExLisperA
    link
    fedilink
    arrow-up
    3
    ·
    4 days ago

    LaTeX and gitlab but today it’s mostly for fun. To get any replies you have to use one of online generators. It doesn’t matter if it’s readable to humans anymore. AI has to be able to parse it.

  • litchralee@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    4 days ago

    I use LibreOffice has my word processor, and no substantial amounts of automation to speak of. And each time I intend to submit a resume, I save off a new copy and tailor it specifically for the recipient employer. After all, what’s relevant and worth highlighting (not literally!) to one employer won’t be the same as for another.

    Yes, I’m aware that a lot of recruiters/reviewers use LLMs as a first-pass filter, but that’s precisely why my submission should be crafted by hand each time: if it’s an LLM, then I want its checkbox exercises to be easily met, and if it’s a human, I want to put my best foot forward.

    In days of yore, where paper resumes were circulated by hand to prospective employers at career fairs, having a bespoke resume for each would have been difficult to pull off. But with PDF submissions, there’s no reason not to gear your submission to exactly the skills that a company is looking for.

    To be clear, tailoring a resume does not mean adding fake or hallucinated qualifications that you do not possess. Rather, it means that you copyedit the resume so that your relevant skills are readily apparent. If you already listed an example project from a prior employer or internship, but a different project would better align to the prospective employer, consider swapping out the example for max appeal. Bullet-points are particularly easy to rearrange: if you have web-dev skills and that’s desirable by the employer, those should be moved up the list of bullet-points. And so on.

    Although resumes are now mostly PDFs, the custom remains – both as an informal fairness criteria between applicants, but also because it would be more to read – that one’s resume should fit on a single sheet of US Letter or A4 paper, barring unique exceptions like professors that have long lists of published papers or systems architects that hold patent numbers. And so the optimization problem is how to most effectively use the space on that sheet of digital paper.

    • _hovi_@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      4 days ago

      Thanks for the in-depth answer. I could definitely be better about it tbh but I agree highlighting points relevant to each role. Makes a lot of sense.

      However, I think automating it actually makes this easier. With rendercv, I have everything in a yaml file, and can comment/uncomment relevant parts where needed, etc., and I can have it re-rendered to PDF on each change.

      that one’s resume should fit on a single sheet of US Letter or A4 paper

      Yeah I might have to go back to this. I recently expanded to 2 pages to be able to show more personal projects / open source work, but it hasn’t seemed to entice any employers much anyway.

      • litchralee@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 days ago

        Having previously been on the reviewing side of job applications, if you have GitHub/Codeberg repos with your work, please, please, please include those links somewhere on the resume, ideally spelled out and also clickable in the PDF. It’s a neat trick to showcase more work than what fits on a page.

        Although the non-technical recruiters might gloss over links, the technical reviewers very much look at your code examples. Why? Because seeing your coding style and hygiene, Git workflow and commit messages, documentation, and overall approach to iterative improvement of a codebase is far more revealing than anything that AI-nonsense coding tests can show.

        So while this won’t necessarily get your resume past the first gate, always be thinking about the different audiences whom your resume might be passed around to, within the prospective organization you’re applying to.

        • _hovi_@lemmy.worldOP
          link
          fedilink
          arrow-up
          2
          ·
          4 days ago

          Thanks yeah. I do make sure to have links to the code and demo/distribution (if the project has one)