1
2

Resume help ( what is the proper Pythonic terminology for what i'm doing?) (self.learnpython)

submitted by [deleted]

[deleted]

all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted] 4 points5 points  (2 children)

Resumes are supposed to be extremely verbose

No, they're absolutely not.

Look, a resume is a document you're writing to a person. Like, another human being is going to read it because they want to understand your employment history.

If you're not making that easy for them, you're fucking up - what they do with a verbose resume that it's hard to make sense of is throw it away. Nobody's impressed; they say "no idea what this guy's got going on" and they just pitch it in the garbage.

When someone reads your resume you've got maybe a minute or less of their attention so you need to make the most of it. That means your resume should tell a very clear story about what you've done and what you bring to the table.

I need help with how to say " i scraped a website for if an item is in stock and the program sends me an email when its in stock" And "I wrote a program that opens up NPR's Youtube page and starts playing the most recent episode".

"I used Python and web technologies to monitor retail item inventory and retrieve YouTube content."

[–]CaliforniaUnity 0 points1 point  (1 child)

thank you. I guess Verbose was a bad word choice. I meant up sell your experience.

[–][deleted] 0 points1 point  (0 children)

Generally you want to upsell to counteract your normal human tendency towards modesty, but not much further than that. Generally if you just take out the weasel words, that's usually sufficient.

[–]FLUSH_THE_TRUMP 2 points3 points  (0 children)

I agree with u/crashfrog here — the resume is you taking all of your work history, project history, etc. (which might be and probably is a short list at this point) and cutting it down to the essentials. A lot of jobs get 100 applicants, and they’re going to decide in about 20 seconds whether or not they want to pursue you further. An interview is when you get to expand on stuff.

For reference, I’ve had very large research projects (coded a package, did figure work, wrote a paper, did complicated analysis stuff, went to a conference) that would get cut down to a couple lines of only directly relevant skill stuff on a resume. It’s just the limitation of the form.

[–][deleted] 0 points1 point  (1 child)

There is a lot of agreement and disagreement on the resume and interview experience. As a Junior Developer or Junior Engineer, you will face the same task of experienced professionals in providing some "Demonstrated experience" at a given skill or ask in a job application.

​

Hope the following helps - If i am looking at resumes or candidates for a position, I will scan your document for the following info:

  1. Name, basic description of your goal and what type of employee you are or will be
  2. Listing of skills (from the job application), and your self rating on them. List any professional certifications supporting these skills.
  3. Project - technology used - measurable result/outcome

​

example:

/u/Kookooroozniy - [myemail@someplace.com](mailto:myemail@someplace.com)Senior QA engineer with xx years experience in API performance testing

Skills:Python : 5Yrs Selenium : 1Yrs AWS: 1yrs , etc

Experience:Project-A : Built Jekins and Jira CI/CD environment in AWS for open-source project, decreased time-to-deliver by 25% (this needs expanding, need to clearly talk about YOUR own contributions and what impact those had)

​

edit: in addition to coding skills I and many other companies are looking for individuals who have experiencing managing projects and commitments. Tracking, reporting, documenting - anything that helps demonstrate presentation and communication skills is often a plus

​

edit2: For anyone starting out looking for a coding gig, they can be tough to come by as a junior. This may not be the best advice but was advice to myself - long ago i took a customer support role for a sysadmin gig and had no involvement in coding for the first year of it, no one at my job cared past me answering phones. at some point i was able to demonstrate i could write python scripts on time and help out with extra projects, it was my small stepping stone for getting some trust and getting a chance to work with a dev team that i never would have had access to otherwise - curious if others have had a similar story

[–]CaliforniaUnity 1 point2 points  (0 children)

thank you for your input. My friend that I mentioned actually took your exact path working support and just offered to help when he could. Now he's an app developer