| Cool project. That said, I never send the same resume to everyone. I tailor a resume for each job I apply to. This doesn't mean leaving off positions or lying. It does mean taking the work done in a position and giving it a slant toward the target job. For example, let's say I created a web app that shows a sales dashboard, with stats visualization, from raw daily sales data. Job 1 (applying for Front-End) - Created monthly sales dashboard web site using React, MaterialUI, SASS, Node, Riak, and D3. Dashboard provided grid-based summary over individual weeks, months, and years. It also provided configurable line graphs and pie charts for various sales metrics. Data pre-processing done with Sci-Kit. Later added sales prediction using Machine Learning. Job 2 (applying for Data Analysis) - Analyzed raw daily sales data to determine data cleansing needed, and created tool pipeline using Python NumPy, SciKit, and scikit-learn. Integrated pipeline into Riak data source ingest, and then built sales dashboard web site to visualize the data. Provided ML model for sales prediction built with scikit-learn, with XX parameters. Model achieved YY accuracy with only a ZZ mean error. Same work in both, but I highlight the tasks most relevant to the target job. Other thoughts are that Latex is a good way to get a well laid out PDF resume (PDF is not the web, you should have two versions of your resume), and I agree with other commenters - the final product needs more polish if it was actually going to be used to produce a resume to send in (I think it's fine as a proof of concept though). |