Compilation and source of a XeLaTeX implementation of my CV. The CV is built according to the currently considered best practices by the majority of US companies for Software Development roles.
Switch branches/tags
Nothing to show
Clone or download
Latest commit 003c2a6 Oct 28, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
fonts Added CV built and updated Readme Jan 25, 2018
.gitignore Initial commit Jan 22, 2018
.travis.yml Added full texlive dependencies to travis ci yml file Jan 25, 2018
LICENSE Initial commit Jan 22, 2018
README.md Update README.md Jan 30, 2018
awesome-cv.cls Added CV built and updated Readme Jan 25, 2018
fontawesome.sty Added CV built and updated Readme Jan 25, 2018
resume.pdf - updated cv Oct 29, 2018
resume.tex - updated cv Oct 29, 2018

README.md

My CV in TeX Build Status

XeLaTex implementation of my CV.

The guidelines that led me to this CV design and layout were the following rules that I found in this Quora answer and believe to be the current standard considerations in recruitment nowadays:

  • A single pager. Unless you have two+ decades of experience you do not have enough interesting things to say on your resume, and I just won't read it. Include a github link or a personal site if you want to show off what you've done.
  • Projects, with technical implementation descriptions. Recruiters look for keywords, engineers look for algorithms, techniques and niche software. "Wrote sorted hash map" is more interesting than "used jsonp for Javascript AJAX UI".
  • Technical proficiencies. Listing the twenty languages you've used is pretty standard, but we both know that you'd be most comfortable with a small subset, so try to specify which those are. I don't do this, but some interviewers will pick an area that you've listed on your resume and deep dive on the nuance, and hold it against you when you flounder.
  • Post code online. There's only so much you can get across in an interview setting (especially when accounting for nervousness, bad questions, scheduling, etc.), and I'm always looking for more evidence outside of the interview if you can provide it. You also get the benefit of having spent much more time & having had many more revisions for anything you post online.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

Install the dependencies

If you wish to be able to develop and support several types of latex and tex files, the best bet is to install the full dependencies package:

sudo apt-get install texlive-full

Easy GUI for editing, previewing and compiling the .tex file (optional)

I personally prefer to use Texmaker, to install it run in your terminal:

sudo apt-get install texmaker

Clone this repository

First clone this repository in any folder you like:

git clone git@github.com:zepedropaixao/paixaocv.git

Compile the .tex file to get your .pdf resume

Make the modifications you wish and then compile the .tex file using XeLaTex

cd paixaocv
xelatex -synctex=1 -interaction=nonstopmode resume.tex

Alternatively you can use the Texmaker interface to very easily edit and preview your changes. For further instructions on how do compile .tex files using Texmaker please refer to their online documentation.

License

This project is licensed under the MIT License - see the LICENSE file for details