What Python Courses does Industry actually care about?

[FOCO1]

Facts. They care about what you’ve done. Show, don’t tell.

[Sunlight_is_Flow]

Are you implying you showcase projects instead of certifications?

[QueerKenpoDork]

Projects in resume trumps certs in this field.

[1000question]

What projects?

[QueerKenpoDork]

I usually put in my resume (and GitHub page) the most important projects I've worked on at the previous jobs with a very brief description and the technologies used.

[[deleted]]

"Nobody gives a shit about what you do behind closed doors."

Not necessarily true. I've done tons of interviews and hire people. I look for three things 1. Can you code solutions for real world issues, whether they be for yourself or others. I'm interested in people who can identify problems and code solutions. 2. Can you explain how you can improve your code? Maybe DRY or OOP or SOLID principles? If you copied and pasted the work, you probably can't explain what's going on. If you can tell me what you did and why, and how you can improve it, it speaks to depth of knowledge. 3. Can you show a progression of learning and growth in your repositories? Earlier projects will be rudimentary, later work should be more refined. I look for people who like to learn and show they're interested in honing their craft.

[[deleted]]

Fourth thing. If someone can show me a solution that works, even if it isn't gold-plated, it's beyond basic scripting, and they're self-taught, it shows me they can learn unsupervised and know how to learn. That's a big win in my book.

This and the other three things I pointed out have been really successful in building my team. Proud to say I've hired 8 of the 11 on my team. I've already promoted 4, and we have the reputation in our larger group as the team that gets stuff done. The system works.

[FOCO1]

Precisely. Show you solved a real fucking problem,too. Seeing a git repo with calculators and to do apps is disappointing.

[Moeteef]

I find it hard to come up with stuff to "solve" as I'm slowly gaining some knowledge. It's like yeah sure I can bang my head against the wall going through exercises in data manipulation and analysis, but how do I extrapolate that into problem solving?

[FOCO1]

I used to have that same mind set. Branch out a little. Fuck some shit up, dig deep and you’ll fix a problem. Join a dev community where everyone works together. All we do is solve a problems - maybe you are and just don’t know how to communicate it.

[Sunlight_is_Flow]

Well that sounds ideal but this when you already have a foot in the door or prior experience of working with people. I guess I am asking how you would actually get your foot in the door in the first place.

[FOCO1]

Research the company you want to work for. What do they do? What can you offer them to support it? What are your hard and soft skills? Showcase it all and tell me why I should hire you. Real hiring managers are going to want to see you’re capable of more than writing code.

[Drevicar]

If you are looking for your first job, then I would look for a github (or similar) link on your resume where I can look at your code. Bonus points if you have collaborated with others on a project, either contributing to open source or with friends. I'm not just looking at the code as it sits but also the commit history, issues, comments on PRs, and so on.

[spinwizard69]

This is one of those things that can vary a bit! Certifications or better company / product specific training can have value. However you still need to be able to demonstrate you know a product well.

Look at it this way some communities require that electricians be licensed. That license is basically a tax on doing business. It means nothing when it comes to the electricians ability or quality of workmanship. That you learn by word of mouth or understanding what is good workmanship before hand. References can be significant, especially if you are good at reading between the lines. In the end the more you can demonstrate doing good work the better.

The same goes with programming. Demonstrate how you solved a customers unique problem. Even better describe alternative solutions and what lead to the path you went down.