Extract. Transform. Read.

A newsletter from PipelineToDE

Hi past, present or future data professional!

If you’re a job seeker in the data space, your GitHub portfolio has only one job: To act as a calling card that gets you to the next step of the hiring process.

Too often, I review portfolios for potential referrals and see brilliant code buried under structural mistakes that have nothing to do with programming skill. Your GitHub is not just cloud storage for your code; it’s a public display case, and you must treat it like a technical resume.

Here are three non-code mistakes that land promising portfolios in the reject pile, and how to fix them today.

Poor User Experience (UX)

A technical reviewer (or recruiter) should not have to spend minutes figuring out which project you want them to review. If your GitHub link requires the user to do work, you’ve already created a bad impression.

• Mind the Audience: Design your GitHub for a specific user: a busy prospective employer.
• Use GitHub Pages: This built-in feature allows you to create a clean, seamless, and easy-to-navigate site that showcases your projects directly.
• Link Directly: Don't link to your main profile page. Link directly to the specific repository or even the project’s landing page that is most relevant to the job.
• Enhance READMEs: Include images, demos, or a GIF in your README files to immediately show the project's output, especially for code files that aren't notebooks.

Lack of Documentation

My journalism background taught me one thing: excellent documentation is a game-changer. Forgetting to document or doing it poorly is the biggest missed opportunity on GitHub.

For a job seeker, documentation is your chance to frame your work for both technical and non-technical reviewers. It should be as simple as answering these questions in your README:

• What does your script do? (Function)
• How does this solve a particular problem? (Business Value)
• Why did you choose your methodology? (Technical Rationale)

Adding a thorough README and clear in-line commentary elevates your code without having to change any functionality, making it easy for reviewers to advocate for you.

Irrelevant Projects

If I see a project derived directly from a textbook exercise or a "learn to code" program, it shows a lack of creativity and relevance to the target role. I (and many other reviewers) generally don't care what you did in school unless you take it to the next level.

• Quality over Quantity: Think of your portfolio as a curated showcase of your absolute best work, not a dump of every script you've ever written.
• Demonstrate Creativity: Your personal projects should solve an independent problem that you chose. This shows initiative and problem-solving acumen.
• Convey Domain Knowledge: The ultimate next-level GitHub features work in the same domain as the jobs you are applying for (e.g., creating a finance dashboard for a fintech company application). This simultaneously sells your technical and industry knowledge.

Read the original story to discover the fourth red flag I consistently see in GitHub portfolios.

Last Call: Your Final Chance For Exclusive Access

I created my first ebook to solve the exact problems highlighted above to turn generic ideas into job-landing portfolio projects that impress recruiters and employers.

This is the final newsletter before the waitlist is locked. Join now to secure your private access link next week, ahead of the general public release at the end of the month.

Don’t miss the chance to start building your career calling card:

👉 Join the Exclusive Waitlist

-Zach