Job Skills Data Science on Github: How to Get Started Quickly

Click For Summary
To secure a position as a data scientist or data engineer, having a strong GitHub presence is often recommended, but the quality and relevance of code shared can vary. Concerns arise about whether code should be basic or advanced, leading to hesitation in sharing work. Some professionals argue that posting code on GitHub may not significantly enhance job prospects and can sometimes negatively impact applications. Instead, contributing to larger, established projects is suggested as a more effective strategy. This approach not only showcases coding skills but also aligns with real-world issues that resonate with recruiters. Engaging with projects that have “good first issue” tags can provide accessible entry points for contributions, making it easier to generate meaningful content for a portfolio.
Avatrin
Messages
242
Reaction score
6
Hi

I have the educational background to do a few jobs I have seen posted as "data scientist" or "data engineer". However, I keep getting told that to get a job like that with my background, in mathematics, I need to post code examples on Github. However, I always feel like my ideas are either too basic or too advanced (so, either it won't look good enough for recruiters or it'll take me forever to actually write the code). I thus never get started.

My question is, how good should my code be? Where should I start?
 
Physics news on Phys.org
Just put it out there. If you include the link in your resume and job application, they'll look at it and decide if it is what they are looking for in a programmer.
 
Avatrin said:
Hi

I have the educational background to do a few jobs I have seen posted as "data scientist" or "data engineer". However, I keep getting told that to get a job like that with my background, in mathematics, I need to post code examples on Github. However, I always feel like my ideas are either too basic or too advanced (so, either it won't look good enough for recruiters or it'll take me forever to actually write the code). I thus never get started.

My question is, how good should my code be? Where should I start?

I don't think you need to post code examples on GitHub to appeal to your employer. I've gone through thousands of applications and actually, on some 90% of the applications where I've seen it included, it has actually hurt the candidate instead.

If you do go the route of including your GitHub profile, I personally feel that a better signal than your own repositories is to have meaningful contributions to large projects. This also gives you an easy way to generate ideas that are relatable to your recruiters - because surely, if it's an important issue to a large project, it's probably accessible to a wide audience. A way to find these is to look for issues tagged with "good first issue" or "contributor-friendly". Here's a few examples for Python: 1, 2, 3.
 
  • Like
Likes CCofADoa and Avatrin

Similar threads

  • · Replies 15 ·
Replies
15
Views
3K
  • · Replies 2 ·
Replies
2
Views
3K
  • · Replies 68 ·
3
Replies
68
Views
10K
  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 29 ·
Replies
29
Views
5K
  • · Replies 29 ·
Replies
29
Views
7K
  • · Replies 3 ·
Replies
3
Views
4K
  • · Replies 15 ·
Replies
15
Views
3K
  • · Replies 13 ·
Replies
13
Views
2K
  • · Replies 4 ·
Replies
4
Views
2K