How/do I indicate I-am-learning SQL/Python on a resume?
June 5, 2022 6:31 PM Subscribe
In my field, programming knowledge is scarce and almost completely unlikely to be needed for everyday tasks, and yet people fetishize it in their job descriptions and hiring decisions. If it would probably count it as a bonus that I know *any* amount of SQL or Python, how should/can I represent my status as an almost-complete beginner?
I work in international development, helping teams corral small and often messy datasets. I help teams improve data quality by building people’s confidence and credibility in collecting and managing data, usually using spreadsheet-based tools in addition to process and guidance improvements.
For my own interest, I have begun (but only JUST) to learn Python and SQL. I’ve worked my way through about half of GalaxSQL (thanks to MeFite recommendations!), and about 3 weeks of an intro-to-Python Coursera course, plus some sessions with a friend on Replit starting to learn practically how to parse text from the web into a structured dataset (beautiful soup, can’t remember what else at the moment). Somewhere from deep in the past I have a GitHub account.
I want to apply to a job that looks like it would care about these things: not because they need someone who is a database maven, but because the role being hired might interact with folks who would be using SQL to query/manage their data. I want to show that I’m the kind of person who deals well with microdata and team processes, and is willing/capable to learn more about the technical backend in order to collaborate and problem-solve effectively. How can or should I go about doing that? “I’ve spent a couple of weeks learning” does not feel like a place from which *I* can speak with confidence or credibility. Thank you for your advice!
I work in international development, helping teams corral small and often messy datasets. I help teams improve data quality by building people’s confidence and credibility in collecting and managing data, usually using spreadsheet-based tools in addition to process and guidance improvements.
For my own interest, I have begun (but only JUST) to learn Python and SQL. I’ve worked my way through about half of GalaxSQL (thanks to MeFite recommendations!), and about 3 weeks of an intro-to-Python Coursera course, plus some sessions with a friend on Replit starting to learn practically how to parse text from the web into a structured dataset (beautiful soup, can’t remember what else at the moment). Somewhere from deep in the past I have a GitHub account.
I want to apply to a job that looks like it would care about these things: not because they need someone who is a database maven, but because the role being hired might interact with folks who would be using SQL to query/manage their data. I want to show that I’m the kind of person who deals well with microdata and team processes, and is willing/capable to learn more about the technical backend in order to collaborate and problem-solve effectively. How can or should I go about doing that? “I’ve spent a couple of weeks learning” does not feel like a place from which *I* can speak with confidence or credibility. Thank you for your advice!
I have used "familiarity" and "developing knowledge" for such things. I think the key to "familiarity" is to make sure it appears near other descriptions of expertise so there's a little contrast: "Expert in SalesForce and SAS. Familiarity with SQL and Python" or whatever.
posted by If only I had a penguin... at 6:52 PM on June 5, 2022 [7 favorites]
posted by If only I had a penguin... at 6:52 PM on June 5, 2022 [7 favorites]
“Familiarity” would probably be the best word to use on a resume, and hold off until an interview to give more details.
To me “novice” and “beginner” aren’t words you put on a sales document (your resume), and I’d wait until you’ve been working with a language at least once a week for ~6 months before putting it on a resume as a skill the company could rely on and hire you for. If you have finished projects that you’d be willing to show as a portfolio piece, sooner than 6 months is ok, but I’d recommend waiting until you have something to *show* before listing it as a skill.
posted by itesser at 7:51 PM on June 5, 2022 [3 favorites]
To me “novice” and “beginner” aren’t words you put on a sales document (your resume), and I’d wait until you’ve been working with a language at least once a week for ~6 months before putting it on a resume as a skill the company could rely on and hire you for. If you have finished projects that you’d be willing to show as a portfolio piece, sooner than 6 months is ok, but I’d recommend waiting until you have something to *show* before listing it as a skill.
posted by itesser at 7:51 PM on June 5, 2022 [3 favorites]
Write something that does something so you can say "Designed, Developed, and Tested a web scraper in Python"
(Or functionality of your choice)
posted by falsedmitri at 8:47 PM on June 5, 2022
(Or functionality of your choice)
posted by falsedmitri at 8:47 PM on June 5, 2022
Python level: basic
posted by london explorer girl at 4:45 AM on June 6, 2022 [1 favorite]
posted by london explorer girl at 4:45 AM on June 6, 2022 [1 favorite]
« Older What are all the scripts on the LA Central Library... | Learning Spanish for a not quite preteen. Newer »
This thread is closed to new comments.
posted by humbug at 6:42 PM on June 5, 2022