Sorry, but lose the photo. It's super cute and endearing, but it distracts from the resume. It feels like a big facebook'ish.
Simplify the formatting, nix the markdown: I understand that the hashes on the side are for headings and the bracket-parens format for links, but the resume is already visually formatted, so the markdown style isn't needed.
Similarly for the monospace: for headers or links, it's useful, but for body-text, stick with non-monospace, sans or sans-serif.
Edit out anything that isn't unique for your resume. Looks like you mostly took care of this in the second edit.
Love seeing the data included in items. It's one thing to "maintain website" but it's another to "maintain website with X users per day with Y uptime" etc. Use this to also bring attention to projects that are especially important to you and that you want to be important to the reader. I'd suggest also including business value, like "this program reduced latency by X ms, which allows us to use fewer hosts, reducing costs by Y% ($Z)"
Careful when putting "experience with" when you're listing technologies you're interested in and have played with but wouldn't be able to hit the ground running. I'm including myself in this. I would really like to work with Go, Clojure, etc. but I haven't built anything significant or professionally with them. It's totally fine to put "If you're working with these, I'm interested and passionate about them" but be aware that anything on your resume is fair game for an interviewer. A question that I often ask is "I see you have experience in X and Y. Can you tell me when you would use X over Y in a project, and vice versa?" I don't drill them on all of them, but it's a soft enough question to just make sure they're not padding the resume. (Not saying you're doing that! of course)
Edit: I did want to say, overall looks good. Just tweaks and polish and potentially making it custom based on where you're applying.
Ryan is an engineer in the Sacramento Area with a focus in Python, Ruby, and Rust. Bash/Python Exercism mentor. Coding, physics, calculus, music, woodworking. Looking for work!
That's great feedback, I appreciate it thank, you. The monospace font and raw markdown syntax are my attempt at a "unique design" and a bit of "personal brand." I'm torn as to whether or not it's too distracting and needs removed or if it adds a bit of personal touch/interest and I can keep it.
I'll definitely look at coming up with some more metrics and see if I can translate them to direct business value. I think that's a really good though.
And I think you're right on the "experience with" section. My goal was to show that I like to learn new things/languages and express an interest/openness to working with them, but the last thing I want to do is come across like I'm padding my resume. I'm sure I could be productive with them after a quick ramp-up, but I don't want to be phony either.
I definitely resonate and respect wanting to have a resume with some personality. Maybe limit the monospace to your name across the top, the headings and anything bolded? Just want to keep the body text readable. Maybe use a body font that's just not like Ariel or Helvetica for a little "oomph" I especially like the Google fonts which give a bit of uniqueness while still staying incredibly readable
I also really get the challenge in the "experience with" section. Especially when you're transitioning careers, it's tough to show "this is what I want to work on" and not getting shoehorned into only what you've already worked on. It's hard to communicate "I've done X for Y years, but I want to work on Z"
Maybe include data or lines that emphasizes how quickly you pick up tech? "Delivered ABCv1 in only X weeks after ramping up on Y language"
Ryan is an engineer in the Sacramento Area with a focus in Python, Ruby, and Rust. Bash/Python Exercism mentor. Coding, physics, calculus, music, woodworking. Looking for work!
Quick suggestions:
Edit: I did want to say, overall looks good. Just tweaks and polish and potentially making it custom based on where you're applying.
That's great feedback, I appreciate it thank, you. The monospace font and raw markdown syntax are my attempt at a "unique design" and a bit of "personal brand." I'm torn as to whether or not it's too distracting and needs removed or if it adds a bit of personal touch/interest and I can keep it.
I'll definitely look at coming up with some more metrics and see if I can translate them to direct business value. I think that's a really good though.
And I think you're right on the "experience with" section. My goal was to show that I like to learn new things/languages and express an interest/openness to working with them, but the last thing I want to do is come across like I'm padding my resume. I'm sure I could be productive with them after a quick ramp-up, but I don't want to be phony either.
I definitely resonate and respect wanting to have a resume with some personality. Maybe limit the monospace to your name across the top, the headings and anything bolded? Just want to keep the body text readable. Maybe use a body font that's just not like Ariel or Helvetica for a little "oomph" I especially like the Google fonts which give a bit of uniqueness while still staying incredibly readable
I also really get the challenge in the "experience with" section. Especially when you're transitioning careers, it's tough to show "this is what I want to work on" and not getting shoehorned into only what you've already worked on. It's hard to communicate "I've done X for Y years, but I want to work on Z"
Maybe include data or lines that emphasizes how quickly you pick up tech? "Delivered ABCv1 in only X weeks after ramping up on Y language"
Mmm. That's a good compromise on both counts. I'll definitely look at that. Thanks for the detailed help!