I agree on the information grouping Peter suggested. Recruiters spend just seconds scanning CVs so clear display of your skills and experience is crucial.
I would also like to add that, since you mention in your homepage that you are learning about UX, maybe try to implement what you have learned on your CV. It's nice that you stick with the "backend" style but the combination of font, font-size and grouping makes it difficult to extract information fast. Preserve your style but focus on presentation and readability!
Keep it up with the projects! Hands-on experience is important and appreciated!
So basically, the "plaintext" look, but with a tad of HTML for titles and important labels?
Sure that could work!
Or maybe like a nice GitHub Readme.md page? Good backend developers always have very readable documentation on APIs for example. This way you can use markdown to highlight and categorize
I guess the HTML version could match what you were trying to propose?
Note that the txt version is made to be sent over e-mail, directly embedded as text message.
Yes that looks much better!
Try combining that with any new UX concepts you are learning about plus the suggested grouping.
Totally agree with @Kostas.
Also add links to the git repo, and make sure that each project is well documented and have clean code, even if is not a very complicated project. There is a good article here about how to make readme files.
Here's some feedback from me:
hope this helps!
Thanks for the overall feedback though
It's hard to read in the format it is right now - it is nice to have stuff broken into multiple sections as it is easy to read - even if you only have 1 item in each section. You're writing this for the purpose of getting invited to the interview/get hired, so do anything you have to, to make the decision easier for the people reading your resume :). Here's how I'd break it up:
2017 - .... Backend developer at Archipad.com, Sophia-Antipolis
Backend developer working on API and message queues with Ruby, Redis, Docker, ....
2017 Code paste bin
Built a code pastebin equivalent with Golang and Redis, hosted on my own server
2016 Picture image hosting Android client
An Android app built with Java/Kotlin. Available at http:/...
2017 - 2018: License of computer science, Nice
Arithmetics, development, electronics and OO basics
2016 - 2017: DUT (HND equivalent), Sophia-Antipolis
Systems' architecture, networking and distributed computing
2015 - 2016: DUT (HND equivalent), Nice
Development and OO basics, databases
The one thing to keep in mind about resumes is that audience is important. If a recruiter is looking at your resume, will a quick scan of it make the right things pop out? The idea of your resume style matching your skillset is wonderful, but it still needs to work for you in the right scenarios!
I focused it on my serious projects and tried to keep the school/work-related info as clear as possible, so from my point of view, this is achieved.
I think the brevity and clarity of the writing is positive. My "pop" advice was more on design. I understand simplicity but a block of text doesn't draw the eye and engage someone. Recruiters see so many resumes it's good to have the layout and design do some of the work for them. But it's ultimately up to you how you want to present your resume.
I think Baccalauréat is in french right?
Indeed. After discussing with a few colleagues, we came to the conclusion that diplomas and titles should not be translated, especially since there's probably no strict equivalent in other languages.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.