Seems Like you have all the necessary soft skills in place (communication, multitasking, writing, leading, heck even being able to talk to people is a plus in software engineering(SWE)), thats an overall big plus and will make lots of things easier for you. The design of your resume is clean, I like it. (Not a fan of the font but thats personal preference)
BUT,
What I am missing is the common thread in your professional experience.
You are trying to give the whole picture who you are and what you are doing. The employer is looking for someone with a certain skill set and he needs to be able to skim your resumé (he has hundreds) and find the skills he needs. What I would do is:
follow the KISS principle (Keep it simple, sherlock). I would maximum write one page as resumé (if possible). Shorten the description of the work experience that has nothing to do with the position you are applying (or even leave the work experience out without any gaps of course (thats what I did)) (I am a civil and a software engineer). Ask yourself: What (hard-)skills can you offer to the employer for that specific position.
Maybe have two versions, one for SWE and one for the mechanical engineering.
More KISS: Sentences like "love to program, especially when learning new things". What do you want to say with it? You don't like to program once you mastered the thing? (Sorry for mocking, but I think you get the point). Leave it out, if you don't love programming (liking is actually enough), you should not apply for a SWE position in the first place. "Comfortable giving, receiving, and incorporating feedback." Are you? prove it! otherwise leave it out.
What roles are you applying for? Don't get me wrong but I think with your resume that you can apply for junior positions in the software engineering field. (If that's not true, then I misunderstood your resumé ) I have a similar story to you and thats what I did. I can't see your "I've been programming for over 10 years". ask yourself, why is that so?
Are you more into frontend, backend, SysOps, data science, security or fullstack? The resumé does not tell me. Maybe try Q&A positions or management positions and transition into SWE. (In my current company, they encourage transitions from different roles. (Its good to fight attrition))
checked your github: there is no link to your personal blog in your readme of the project (rpalo/personal-blog). A missed opportunity to showcase your skills, since I (as an hypothetically employer) was interested. (*edit: found the url in the resumé but still better to add it to the readme)
Getting the first job in SWE is usually the hardest, don't give up too early.
If you are interested, I could send you my resumé. Its not a beauty (not a designer) but it got me a job.
Hope this helps and good luck.
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!
tl;dr: Important things first, leave out or shorten the unnecessary stuff.
I just checked your (first version of the) resumé again. You have "Create software tools [...], Implement company’s current website" in your current professional experience as the last points. You lost me at "Manage ~10 simultaneous....".
Do you have to directly deal with customers as a "Customer Success Engineer"? And if not I would remove/ shorten everything else from this work experience and extend on the implementation of the current website or the create software tools.
E.g: "Took over ye olde website of company x [written in ancient language] and implemented the current version of it [in just two weeks, ...] using [hype/ relevant tech stack] [url]. [optional: greatest achievement or problem and how you solved it]..."
Focus on outcomes and achievements (credits to Rolf Streefkerk))
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!
If you have a minute, I created an updated version (see the update above). I tried to streamline things and, since none of my programming experience is professional software engineering, I tried to showcase my open-source/hobby work more clearly. Is that any better?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Seems Like you have all the necessary soft skills in place (communication, multitasking, writing, leading, heck even being able to talk to people is a plus in software engineering(SWE)), thats an overall big plus and will make lots of things easier for you. The design of your resume is clean, I like it. (Not a fan of the font but thats personal preference)
BUT,
What I am missing is the common thread in your professional experience.
You are trying to give the whole picture who you are and what you are doing. The employer is looking for someone with a certain skill set and he needs to be able to skim your resumé (he has hundreds) and find the skills he needs. What I would do is:
Getting the first job in SWE is usually the hardest, don't give up too early.
If you are interested, I could send you my resumé. Its not a beauty (not a designer) but it got me a job.
Hope this helps and good luck.
This is some really good feedback, thank you. I’ve got some solid action items to address. 😁
tl;dr: Important things first, leave out or shorten the unnecessary stuff.
I just checked your (first version of the) resumé again. You have "Create software tools [...], Implement company’s current website" in your current professional experience as the last points. You lost me at "Manage ~10 simultaneous....".
Do you have to directly deal with customers as a "Customer Success Engineer"? And if not I would remove/ shorten everything else from this work experience and extend on the implementation of the current website or the create software tools.
E.g: "Took over ye olde website of company x [written in ancient language] and implemented the current version of it [in just two weeks, ...] using [hype/ relevant tech stack] [url]. [optional: greatest achievement or problem and how you solved it]..."
Focus on outcomes and achievements (credits to Rolf Streefkerk))
If you have a minute, I created an updated version (see the update above). I tried to streamline things and, since none of my programming experience is professional software engineering, I tried to showcase my open-source/hobby work more clearly. Is that any better?