Career signal & proof

Publish a portfolio employers can verify

2–3 deployed projects with READMEs, demo links and architecture notes on GitHub; LinkedIn that mirrors it.

~10 focused hours·beginner

Tools: GitHub, a deployed demo host (Vercel/HF Spaces/Streamlit Cloud), LinkedIn

Market relevance — share of job ads asking for this
Prerequisite capability — not asked for directly, but needed for others.
What employers mean

You should be able to…

  1. Publish 2-3 deployed projects with READMEs a recruiter can understand in under 2 minutes
  2. Write a README that shows architecture and results, not just setup instructions
  3. Deploy projects to a live demo link, not just source code
  4. Keep a LinkedIn profile that mirrors and links to the portfolio
  5. Use commit history that shows real, incremental work rather than one giant commit
  6. Write architecture notes explaining key decisions, not just what the code does

Needs first: Collaborate with Git and GitHub

Learn — free, link-checked

The few resources that matter

Practice

Portfolio audit and rebuild: 2 deployed AI/automation projects

Take two of your existing projects (or two from earlier practice projects in this plan) and bring them to a portfolio-ready bar: deploy both to live URLs, rewrite both READMEs to include architecture diagrams, results/eval numbers, and a demo GIF or video, and update your LinkedIn 'Featured' section to link to both with a one-line description each.

Done when
  • Both projects are deployed and reachable via a live URL
  • Both READMEs include an architecture diagram or clear component list, plus results/metrics
  • Both READMEs include a demo GIF, screenshot sequence, or linked video
  • LinkedIn Featured section links to both projects with a one-line description each
Prove it

Evidence a recruiter can check

  • Two live project URLs
  • Two GitHub repos with portfolio-quality READMEs
  • LinkedIn profile link showing the Featured section
Interview

Questions you'll get asked

  1. Walk me through one of your portfolio projects as if I've never seen it.
  2. What would I see if I opened your GitHub profile right now?
  3. How do you decide what goes in a README vs what's just in the code?
  4. Tell me about a project you deployed live — what was the hardest part of getting it running end to end?
  5. How does your LinkedIn reflect the work in your portfolio?