I would however do a few things to make the experience worthwhile to the reader: either list the resume directly, or add many "easter eggs" that are the typical commands anyone will use when playing with the shell (as already mentioned: ls/pwd/man/cd etc). And the scrolling should be super fast - that sort of slow display is cooler in a movie than when actually having to wait for it.
If it's to share with someone actually into recruitment I'd do something like pre-write on the line `./resume.sh` and fake "echo" a message saying to just press ENTER, which then prints it all neatly at once for reading (and then you can always have a fake `ls`, a fake `resume.sh` file with read-only attributes, and you can troll your visitor differently depending on if they try to use vim/emacs/nano, and more things along those lines). An option to get a PDF would be awesome too.
I'm having a lot of fun thinking about doing things with what you've done (particularly at the expense of the visitor, I wonder what that says about me..), but ultimately you're the one who coded the site already - so all props to you!!
Just a tip, if you're posting this around places I'd put the acute accents on résumé, at first glance I thought this was going to be something like https://mosh.org/
As someone who occasionally hires technical people, I'm torn on this one.
The process at my employer is that resumes are submitted via the web site, they get stored in a shared folder (each application gets a folder with all of their attachments plus whatever they entered into the form on the web site), and once the competition closes the people doing the hiring (usually a manager and a team lead) review them.
When I review resumes, I spend about 30s per resume on my first pass through. This is where I just visually scan the document for keywords. For example, if I was hiring a Django developer (I'm not, this is contrived), I'd look for Django (obviously), but also for other Python web frameworks (e.g., Flask, Pylons, web2py), other big Python frameworks (e.g., SQLAlchemy), and other related technologies that we might use in conjunction with Django (e.g., PostgreSQL, Celery, etc).
Once I've completed the first pass, I take a deeper dive into the shortlisted resumes, decide who I want to interview, etc.
As a technical person, I'm intrigued by this resume. It's presented in an interesting way, and the presentation itself can even serve as a living showcase of this person's skills.
As someone doing hiring, I'm wondering how this will show up in that shared folder. Will it be a PDF with a link that leads me to this resume? Will there be no files attached and a link placed in the comment box? Will I pass on a potentially great hire because I didn't actually see a resume during my first pass?
I do think this resume would work really well as supplemental material to a traditional one. One of the best people we hired submitted a traditional cover letter/resume as a PDF, but had hyperlinks within the PDF to online supplemental material. This worked really well for my process because they passed the initial scan, and the hyperlinks let the applicant provide a lot of detail that would have overwhelmed a traditional resume format.
> When I review resumes, I spend about 30s per resume on my first pass through. This is where I just visually scan the document for keywords. For example, if I was hiring a Django developer, I'd look for Django...Once I've completed the first pass, I take a deeper dive into the shortlisted resumes, decide who I want to interview, etc.
The way I see it is that this kind of resume is explicitly reverse filtering against hiring processes like yours. Creative people don't want to be compared in the hiring process as part of a "shared folder" against 300 other people, because it becomes basically an SEO game. (Note that this is not saying your process is wrong, it's just not a good fit for more creative and freewheeling programmers).
This is a really good point! I'd say that the process is a reflection of the environment and the work.
My environment is focused on supporting/enhancing/fixing the commercial ERP system that we use to run our business. There's room for creativity, but at the end of the day it's still about supporting a relatively boring HR/Financial system. Technology is not our core business, but we do invest in it in order to better execute on our core business.
Some people thrive working on these systems and in this type of environment, but others would be bored to tears.
If it does work as a reverse filter like you suggest, I lose out on a really good developer, but the really good developer avoids taking a job that he'd find soul destroying. Overall, that's probably a win.
Thanks for your input and sharing some useful info, I already read similar things here on HN and other sites where people describe similar hiring processes. To be honest with you I don't like them, but I understand the need of having one in a bigger company.
I understand your point, however this resume isn't intended to be the first contact with a future employer. It will be contained in my pdf resume once I update it, but I hope the employer will notice it. I'll probably mention it in a cover letter or similar.
But as quadrifoliate already stated, this resume is a reverse filtering against standard hiring processes.
I'm actually looking for a smaller sized team which I hope will be full of hackers that like to fiddle on the low level side of technology etc.
If I were doing this, I'd probably just have two versions of my resume: the creative one and a conventional one. If my application gets through the early screening stage, then maybe it's realistic to expect someone to devote a little more time to my resume.
I'm currently looking for a remote position as an Embedded Engineer.
So I decided to make a shell like resume webpage instead of a classic personal website (since shells = love).
The project is version 0.00001 (lol), just wanted to ask you guys what you think of the idea and if you have any tips on what to improve :).
You'll probably quickly see there are a few bugs (on mobile prolly, etc.) please let me know in the comments. Also, the "help command" feature is not implemented yet, just "help".
I'm not usually into web programming so I used jQuery.
This is cool, but as a hiring manager I prefer to be able to read the resume quickly and easily. I’ll probably have over 100 resumes to look at for any position and a finite amount of time I can allocate to each resume.
On the flip side of that, I doubt OP wants to work for someone who doesn't have the time or the inclination to put serious consideration into something novel.
If someone makes something novel, that can attract attention, sure.
But if you're initiating a communication (e.g. applying for a job), it's polite to communicate clearly and respectfully.
I think making something like this for fun is neat! +1 for sharing it, too. But, it'd still be a poor substitute for a plain-old resume & cover letter.
Agree- but having the time and inclination to put serious consideration into something novel doesn't mean they have the time and inclination to put serious consideration into everything novel. It's a risk. Make it an "also" not an "instead of."
This is pretty cool. From a UX standpoint, my first intuition was to use ls to list out the directories and to use tab to autocomplete, neither of which worked. The animation is cool but it's a little slow and might be frustrating if I was trying to read the resume for real to get info rather than just playing around with the demo.
Still really cool though. I made a prototype resume myself recently[0], great to see more of these creative ways of showing off experience.
Hey thanks for the input!
Good idea, I'll try and implement cd, ls and cat for example.
The tab autocompletion is on my TODO list as well as a simple command history.
Also, thanks for trying to actually read the cv, I'll increase the "typing speed".
This is neat, but doesn’t support the first shell commands I tried- ls, pwd, man.
Maybe try to map these commands to doing something related to your resume.
This plays more like an Infocom text game than a shell because the commands are arbitrary and need to be learned.
If you could treat some of the sections like a file system then I wouldn’t have to type “help” to see I need to run the “skills” command. Maybe just have skills as a file so when I type “ls” I see them. Or when I try to change directories it navigates the resume or something.
Thanks for the input!
I'm planning on adding some basic shell functionality and a "directory structure" with some files which ofcourse will be "fakeish" but it won't seem that way.
The text cursor is put below the prompt when the window isn't fullscreen:
[feelqah@github ~]$
|
Also, on trying to copy the prompt to paste here, I noticed the mouse cursor disappears on everything but links, and whatever I select is immediately unselected.
If you want it constantly running, why not make it a proper service in your systemd config? In that way, yeh it exists. You can follow the logs with "journalctl -u ... -f"
You can preconfigure a screen session in that case. `screenrc` allows you to specify what windows are opened at startup and you can bind specific commands to them.
I would however do a few things to make the experience worthwhile to the reader: either list the resume directly, or add many "easter eggs" that are the typical commands anyone will use when playing with the shell (as already mentioned: ls/pwd/man/cd etc). And the scrolling should be super fast - that sort of slow display is cooler in a movie than when actually having to wait for it.
If it's to share with someone actually into recruitment I'd do something like pre-write on the line `./resume.sh` and fake "echo" a message saying to just press ENTER, which then prints it all neatly at once for reading (and then you can always have a fake `ls`, a fake `resume.sh` file with read-only attributes, and you can troll your visitor differently depending on if they try to use vim/emacs/nano, and more things along those lines). An option to get a PDF would be awesome too.
I'm having a lot of fun thinking about doing things with what you've done (particularly at the expense of the visitor, I wonder what that says about me..), but ultimately you're the one who coded the site already - so all props to you!!