this post was submitted on 27 Mar 2024
334 points (96.4% liked)

Open Source

31188 readers
234 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

Hi all,

I made this typst template originally to port my personal resume to typst from Latex. It tries to be a faithful port of the Awesome-CV latex template that I was previously using. Hope you find it useful.

https://github.com/DeveloperPaul123/modern-cv

Edit: added missing link

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 2 points 7 months ago* (last edited 7 months ago) (1 children)

As a manager who sometimes hires, I can't say that I would ever particularly care about the education section for the types of roles I hire for, let alone put it first and foremost.

Also, personally, my own CV combines my role's duties and its achievements/projects together for each of the jobs I've had, with a primary focus on the recent.

[–] [email protected] 2 points 7 months ago (1 children)

Education section first for very junior roles. Experience first for anyone with professional experience

[–] [email protected] 1 points 7 months ago

If you don't have an experience section at all, then sure that'd bump it up the list.

[–] [email protected] 5 points 7 months ago (1 children)

This is great! How would you describe your experience creating this template? I've been wondering about porting the modern-cv template from LaTeX myself.

[–] [email protected] 5 points 7 months ago

Overall it was pretty nice honestly. Especially coming from Latex. Creating a template in Latex was very difficult but in typst it's way more intuitive (at least to me) and it's easy to control every aspect of the text and its layout.

[–] [email protected] 5 points 7 months ago (1 children)

I was using a template like this several months ago, (in typst) I think someone had already ported awesomecv beforehand.

[–] [email protected] 2 points 7 months ago (1 children)

Oh really? I couldn't find a port of this before. Do you happen to have a link?

[–] [email protected] 2 points 7 months ago (1 children)

Several of the ones listed on awesome-typst are similar, notably:

Not to knock the work you have done though

[–] [email protected] 2 points 7 months ago

Ahh yes, I tend to forget about these "awesome" lists. Thanks for the links.

It seems that Brilliant CV is a direct port of the same latex template I used to use as well. The developer references it as well in the README. I do think my template is a bit easier to use and is more up to date with the latest typst version but there are some really nice templates on there.

[–] [email protected] 24 points 7 months ago* (last edited 7 months ago) (2 children)

This looks good.

A few unsolicited nit-picky suggestions;

  • I'm not a big fan of mixing colors in a single word. 'Taky' might the be the right to describe why. I do like the color blue you used - if you're going to do it, make it the whole word. The name should also be consitent. Bold and either black or blue, not black and blue.
  • The light blue and light gray body text is difficult to read. Colors should be solid black, or navy blue. Bright and 'fun' colors are heard to read for some. Assume they're colorblind or will print it on a B&W printer with poor contrast.
  • I like to lead with the job title instead of the company. Where you worked is largely irrevelvant compared to what you've done at those places. It also makes it easy to combine company, city and years in one line.
  • start with previous jobs (unless education was most recent or more relevant to new job). Typically the order is job > skills > education.
  • Avoid italics they can be unnecessarily diffuclt to read

Engine Mechanic

Bob's Auto | City, ST | 2017-2021


Education does not need so many details (if relevant to job, include specific courses and projects). Grad date can be omitted to help obfuscate you're age (a grad from 2024 is probably inexpirenced, while a 1967 grad is going to be retiring soon).

Two lines is all you need;

Bob's University, City, ST

B.S. Computer Science, minor electrical enginnering

[–] [email protected] 3 points 7 months ago (1 children)

I'm working on some of the changes your suggested. Here are screenshots of the adjustments. I'm curious to hear your thoughts. Thanks!

Here is a monochrome version without colored headers. I also adjusted the default accent color, but this is user configurable as well.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago)

It looks a lot cleaner now.

The body text seems too light still, but that might be my phone screen. It should be solid black.

~~Only~~ One change from here I would strongly recommend making is the blue "city" text black.

Treat blue and bold text as your 'highlighter', there to help someone quickly navigate to the important sections of the page. City is not important. Your use of varriying font sizes and bullet lists is great for page navigation.

If I was going to use color, I'd highlight the jobs before the city name/git link.

The rest is personal taste.

Personally, I think the blue headers is enough. It might get to too blue if you color job titles as well. You don't need a separate monochrome version, the dark blue will show as black if it happens to be printed in B&W. You should also test print your resume in B&W. I find easier to spot errors on paper.


Edits as I spot more little things.

(Also there's an extra space in the second skill name - Event Bus)

(You also have space to make programming languages one line. At first glace I though you had a blank section for "languages". Could probably just say "programming", but I'm not in that field so maybe that's frowned upon?)

(In education, you have an example line underneath the university name, what is that line for? I would put the degree in that space, not off to the side. That's technicaly more important that the university it self, but it's probably "improper form" to list that above the uni name. (or whatever some one snoby would say).

(One last thing, you don't really need your full street address. Its unlikely anyone will mail you a response, and its just as likely you'll have to enter it into the application form anyways. City will suffice.)

(One last last thing, if you're going to give yourself titles at the top, you better show them in your expirence section. (I know this is just an example template and I am being incredibly picky) but I don't see architect anyware in the actual resume. That communicates to me you're just calling yourself related titles hoping one sticks)

[–] [email protected] 5 points 7 months ago

Thanks for all the feedback! I'll take each point into consideration as I work on the next version of the template :)

[–] [email protected] 1 points 7 months ago

I haven't had a single page resume in over a decade, I think you usually want to have more for SEO purposes. A lot of places filter by keywords.

[–] [email protected] 4 points 7 months ago* (last edited 7 months ago) (2 children)

Somewhat unrelated question:

How do you list experience based on projects under single employer with timeline?

Right now I have it like this:

  • Consultant

    Employer - 2020 - 2023

    • Developer - June 2023 to August 2023
      • Description 1
      • Description 2
    • Analyst - March 2021 - May 2022
      • Description 1

I havent found any resume template that can handle this (nested experience) automatically

[–] [email protected] 3 points 7 months ago (1 children)

I put this together in a few minutes using my template. Does this address what you meant?

Here's the typst code:

#import "@preview/modern-cv:0.1.0": *

#show: resume.with(
  author: (
      firstname: "Person", 
      lastname: "Lastname",
      email: "[email protected]", 
      phone: "111-111-1111",
      github: "DeveloperPaul123",
      linkedin: "LinkedIn Name",
      address: "111 Road Dr. City, Place 111111",
      positions: (
        "Software Engineer",
        "Software Architect"
      )
  ),
  date: datetime.today().display()
)

= Experience

#resume-entry(
  title: "Company, Inc.",
  location: "Place, Earth",
  date: "2022 - 2023"
)

#secondary-justified-header(
  "Developer",
  "June 2023 to August 2023"
)

#resume-item[
  - #lorem(10)
  - #lorem(11)
]

#secondary-justified-header(
  "Analyst",
  "March 2021 - May 2022"
)

#resume-item[
  - #lorem(10)
  - #lorem(11)
]
[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

This is very close. The only thing missing is job title for the parent along with the company name for each nested experience

[–] [email protected] 2 points 7 months ago (1 children)

Whoops! I ommited that on purpose. But you can add the job title back in. And yes I see how that would be good for each sub section to have the company name.

This should be doable, I'll update this thread if I can implement it.

[–] [email protected] 1 points 7 months ago

Appreciate it

[–] [email protected] 2 points 7 months ago (1 children)

@tarius @devpaul

What you can do is more important that who you have done it for. I prefer to see skills, experience, employment history, and education in that order.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

I understand. But, consultants could work on so many various things based on the project. Its better to provide context of the role and what industry that project was instead of only showing one block of text.

As an example, If I worked at a company for 2 years, I could have used GitHub for 3 months in one project and used GitLab for 6 months in another project. If I write both of them in the same block, you would think I have 2 years of experience in both which is not accurate.

Obviously there are ways you can write that in the description. I was just wondering if there are options to have nested experience.

[–] [email protected] 1 points 7 months ago (1 children)

@tarius
The skills section is the place you can list years of use of each tool or technology. The experience section is a place to list accomplishments, independently of what tools were used.

My recommendation is based on science consulting, where a pretty clear division can be made between tools and accomplishments.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

I dont use a Skills section at all in my resume. How do you determine the quality of skills based on just keywords in the skills section?

In description if you show that you worked in certain technology for "this" long, you would get somewhat an idea of how skilled that person is in that tech

Lets say I put Office in skills section, you wouldnt know how skilled I am in office. I might have only worked with it for a month. And I am talking about resume without any fancy graphics with bar graph to show the skill level

[–] [email protected] 1 points 7 months ago (1 children)

@tarius
The same question would apply to skills mentioned in the experience section--unless the experience section is nothing but a description of use of those skills. It seems as if you and I may be valuing the experience section in different ways.

But the direct answer to your question is in an interview. If you assert both valuable skills and experience, then you will get pressed to demonstrate or explain those face-to-face.

[–] [email protected] 1 points 7 months ago (1 children)

The same question would apply to skills mentioned in the experience section–unless the experience section is nothing but a description of use of those skills.

That's why I said if the skill is listed as a description in the experience (not literally the keyword), the "time range" would give you somewhat of an idea about the person. Key here is not listing just the skill, but what they actually did with that skill.

It seems as if you and I may be valuing the experience section in different ways.

If you are a recruiter/manager that gives a call to everyone, then I appreciate what you do. But, wouldn't your job be much easier if you are able to understand the candidate's skill from the description without even talking to them? Filtering out inexperienced people would be much easier instead of just going by the skills section.

But the direct answer to your question is in an interview. If you assert both valuable skills and experience, then you will get pressed to demonstrate or explain those face-to-face.

In the current market for IT folks, its not easy to get an interview. So you wanna give as much information in the resume to get that first call. This is from my personal experience in the last 6-10 months

[–] [email protected] 1 points 7 months ago (1 children)

@tarius

I'm interested in both the candidate's skills and achievements. The list of skills is a quick and easy filter, but once past that, achievements deserve a lengthier explanation--and they may still reference skills.

Having hired for years in an IT-adjacent discipline, I like to see skills and achievements factored out, not unlike the way code or data structures should be factored.

A/B testing of resume structures might be interesting.

[–] [email protected] 1 points 7 months ago (1 children)

Wouldn't the application software filter out the keywords from the description?

[–] [email protected] 1 points 7 months ago (1 children)

@tarius
I don't know what application software you're referring to.

[–] [email protected] 1 points 7 months ago (1 children)

I meant like Workday, Greenhouse, ADP, etc.

[–] [email protected] 1 points 7 months ago

@tarius
I'm not familiar with them. All of our resumes are screened by actual people.

[–] [email protected] 2 points 7 months ago

I am also in the single pager, latex CV club. I ended up splitting into two columns though like -

                 NAME
            contact deets
-----------------------------------------
bio                   |    current workplace
skills                |    old workplace (senior)
education             |    old workplace (midlevel)
projects              |    first workplace
load more comments
view more: next ›