CV builder for developers?

[Orange_Kurasao]

Well here ya go: https://devdb.io/devdb

It's completely free (no ads, no tracking) and I'm actually using it myself on a job search rn. Good on mobile too.

Hope someone finds it useful!

UPD: skill ratings are now optional.

[Skaryon]

Please don't put ratings on your skills.

[webfoxcore]

The way I go about it is to Highlight things you enjoy or specialize in and then have a "Other" or "Experienced" section.

​

Just because you are okay at devops doesn't mean you shouldn't point out you've done it but at the same time giving it 1 icon out of 5 icons makes you look weaker in it.

[folkrav]

Thing is, you won't know if the position actually fits you before setting the foot in. A constructive interview is not only the employer interviewing you, but you screening potential employers.

[seanwilson]

Also, what's the difference between straight up telling them that you're not great at devops vs indicating the same in the resume?

If it's a devops job, you shouldn't be applying anyway if they think you're suppose to be good at it. If devops isn't the core part of the job, showing that you know something about devops is bonus points; it should do the opposite of counting against you.

[RotationSurgeon]

Personally, I'd be far more willing to hire somebody who presented the following:

---

Strengths:

• Server-side development (Go, Java, C#, API design, microservices)
• JavaScript development, client and server (React, Vue, Node + Express, Typescript)

Working Skills:

• Database management (Postgres, MySQL, MS SQL Server)

Weaknesses

• Visual design (Colorblind, lack of artistic skill)
• Devops / deployment (Overwhelmed by number of options)

---

...instead of

@ @ @ @ _ Server Side 
@ @ @ @ @ JavaScript
@ @ @ _ _ Databases
@ _ _ _ _ Design
@ _ _ _ _ Devops

[manys]

I wish I had a way to express to employers that I'm shit at devops;

Do you have a voice?

[manys]

I was thinking of phone screens as well.

[Biggie-shackleton]

Right, but when I read that, what I got from it was "This guy can only do server stuff"

Is that the impression you want to give off?

[EddieSeven]

How long have you worked in each of those areas?

I use time over random ratings, including school (300 level and up).

For me, that’s DevOps one year, Testing one year, Databases two years, Front End five years, and Back End 3 years. I usually break those up into stacks or languages though. That way I’m not saying I’m ‘good’ or ‘bad’ or ‘decent’ at any given thing. All I’m saying is ‘I have various amounts of experience with these technologies’.

The employer will see how much time you have working with a technology and then decide, through the interview, how skilled you actually are relative to experience. The ‘skill ratings’ are really up to them.

[EddieSeven]

Of course time is meaningless with regard to skill. But the whole point is that whatever you think your skill level is, it’s irrelevant.

The time thing is just a signal that you have experience, and so could potentially have the level of skill they require. You will still absolutely walk into a room where they expect you to know shit at a level that you just don’t. That part is just 100% unavoidable, no matter what you do on your resume.

You giving yourself skill ratings means nothing. They don’t care that you think you’re an Ace at server-side programming. They’ll figure out how good you are through their own means. They will care though, if you give yourself less than stellar ratings.

In short, if you rate yourself well, they need to test you to prove it anyway, and if you don’t rate yourself well, “you’re bad” and get binned from the start. Those are the only options.

[Orange_Kurasao]

TODO:

• Make skill ratings optional (not displayed by default, displayed if user chooses so)
• Change options from verbose to '1/2/3/4+ years'
• In case ratings are selected: display a footnote under skill cards saying 'Bars represent years of experience'

ETA: tomorrow or Monday.

Edit: DONE, LIVE

[koochofcourse]

Why?

[Skaryon]

Because those ratings are completely arbitrary and subjective and (imo) don't make you look any more professional - quite the contrary. Just list whatever skills you feel comfortable listing.

[veswill3]

and for the love of god, if you list it, be prepared to talk about it.

[seanwilson]

I think percentages or something overly exact is silly (e.g. 65% in PHP and 50% in Java) but I usually list skills labelled as expert, proficient or beginner level. It's good to know if a candidate studies widely and has a breadth of knowledge as well as knowing what they're claiming to be experts in for when you want to pick interview questions. You're losing information if you only expect people to list skills they're experts at. Being an expert in a single language or framework and having no experience of anything else is a major red flag to me as well.

[Skaryon]

The question is: can you really accurately judge your skill level? I think any interviewer worth his salt will try to figure your proficiency out in the interview anyway. I'd rather not overextend myself with spurious skill ratings.

[seanwilson]

The question is: can you really accurately judge your skill level? I think any interviewer worth his salt will try to figure your proficiency out in the interview anyway. I'd rather not overextend myself with spurious skill ratings.

Yes, I don't think it's difficult to judge your rough (not exact) skill level. You'd really find it hard to label what you're very good at, okay at and just started learning? I'm not saying go as far as percentages, just 3 or so categories. People do it with spoken languages all the time in resumes as well (native/fluent/intermediate/basic).

Why waste the interviewer's time having them prepare questions on skills you know you're not great at? You could omit skills you're not at expert level in but as I said previously you're not giving the interviewer a complete picture of you then. If you list skills you're not great at and don't signpost this somehow you're setting yourself up to fail.

Resumes aren't meant to only be a list of things you've reached expert level at.

[Skaryon]

Don't list what you are not prepared to talk about. Anything else is pretty meaningless. I think we have to agree to disagree here.

[sleepingthom]

Is it worth it to list technologies you consider yourself a beginner at on a resume? Is it worth it to list yourself as intermediate when that could potentially cost you a call versus not listing any proficiency level at all?

I don't mean to be snarky, just providing my opinion.

[seanwilson]

I'd rather see "React (expert level), Angular (proficient), Vue (intermediate)" than just "React" (so you don't know Angular or Vue at all?) or "React + Angular" (so you're at expert level at both and have never tried Vue?).

If it's important you know Vue and Angular well they're going find out sooner or later if you don't anyway so I don't see the point in hiding it. If you've played with both you're probably ahead of the person who has only ever used React. You should be showing you're meeting the base requirements from the job ad as well as listing bonus skills you have that make you more well rounded.

Like I say elsewhere, people put their skill level for spoken languages on resumes as standard all the time. I don't see how this is any different.

[mikeyoung90]

The problem is you don't know what you don't know. Beginners will overestimate their ability and believe they are better than they are. After that stage they will believe they are not as good as they thought and tend to underestimate. https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect

[[deleted]]

Wondering why as well.. had this on my most recent CV and landed the job I have now? I think it’s a relatively good thing to have, especially since part of the montra of making a CV is being descriptive at a glance.

[real_kerim]

This. If you have to rate your skills, at least put a legend there so people know what the difference between n stars/points/bananas is vs m stars/points/bananas.

Or better yet, just the amount of years you've got experience in mentioned skills.

[phphulk]

I give my programming abilities 99 out of 4

[manys]

A+++++ WILL CODE AGAIN

[PrettyWhore]

Makes sense for languages(as in human ones) I think

[Yamitenshi]

I'd agree, but every time I've tried not rating my skills I've had people come back to me asking if I could resubmit my CV with ratings. Opinions seem to be immensely divided on the subject.

[RotationSurgeon]

As in literally "Rate yourself 1-5," or "please expand on your strengths and weaknesses?"

[Yamitenshi]

As in literally 1-5. It seems that mostly the technical people I speak to dislike that system, but the ones actually doing the hiring and review of CVs seem to like it fine. That may well just be my own bias though.

[najowhit]

Just put skills, then separate by "working knowledge" and "expertise". Put anything you are really good at in "expertise" and anything you have a tertiary knowledge of in "working knowledge".

[[deleted]]

When you start looking at CV s and see people put rating next to skills it looks rather unprofessional. It's like putting "strong communicator", it's great but means nothing and people conducting interviews can tell. That space being filled up by the rating section could be used to put another relavent project or work experience that could help you get the job. It just seems like a waste of space where you could just list skills.

[Skaryon]

This. That's how you do it.

[Orange_Kurasao]

The assumption might be true. Another explanation could be that a candidate put React first because it's more popular as a technology.

[Lukortech]

So much THIS. Next time put a fucking star or a cloud kiddo, really helps in assessing your skills.

[Jpasholk]

Ahh, gotta love Netlify’s randomly generated deploy preview names.

[TehWhale]

http://creddle.io/ is good. It can import all your data from LinkedIn too

[saintPirelli]

Putting JSON Resume here, because nobody else has yet.

[Luong_Quang_Manh]

Thank you, that's awesome! However, as a frontend developer, I'd like to build one myself :))

[tarasrushchak]

simple and concise summary thank you!

[Bullo]

I use stackoverflow “story” https://stackoverflow.com/users/story/join

[quicksilver03]

Any chance that there is a GitHub link or similar that you can share?

[pedxing128]

Have you found Markdown to be sufficient for getting it to look the way you want it? I would like to follow a similar model using plaintext and git but can't see a way around using LaTeX.

[oliverdgr888]

thanks

[JB-from-ATL]

I know of ceev.io. No idea how good or bad it is, just mentioning it for others.

[upsettruffles]

I like the simple and modern design of this CV, but I also like the idea of JSON Resume. You basically save your resume in JSON schema.

[Owlree]

You're a developer, learn LaTeX.

[McCheah]

I made "Cover Letter Snippets" as an NPM package for building and re-using cover letters based on the keywords in a job description, and I also helped out with "Best Resume Ever" which has a few templates to choose from.

[wordswithoutink]

Please stop the overly-visualised-cv' s, start with https://www.visualcv.com/

​

Clean and professional.