All capabilities · 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 hoursbeginner
Explore 4 tools for this project
Market relevance

Which roles ask for this — and how often

Share of job postings in India, per role, that name this capability.

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

Tools for practice

Choose a tool for the job

Start with one tool for each part of your project. You don’t need to learn them all.

Go to the practice brief

4 tools to explore

GitHub

Code · Plan & explain

Publish a project, review changes and explain how someone can reproduce your work.

Hugging Face Spaces

Deploy

Host an interactive model demo with instructions and examples others can try.

Practice

Portfolio audit and rebuild: 2 deployed AI/automation projects

Take two projects you have already built — earlier practice projects on this path count — and bring them to a bar a recruiter can read in two minutes. Deploy both to live URLs. Rewrite both READMEs to lead with what the project does and what it scored, with an architecture diagram and a demo GIF above the setup instructions. Then wire both into the Featured section of your profile with a one-line description each.

Start from

Two projects you have already built, plus their current READMEs and commit history

Milestones
  1. Audit both repos against a recruiter's two-minute read and list what is missing · ~1.5h
  2. Deploy both to live URLs and confirm each works from a clean browser · ~2.5h
  3. Rewrite both READMEs with an architecture diagram and real result numbers · ~2.5h
  4. Record a demo GIF or clip for each and wire up the profile links · ~1.5h
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 URLs that work in a private browser window with no setup asked of the visitor
  • Two READMEs that open with what the project does and what it scored, architecture diagram above the install steps
  • A demo GIF or clip in each README showing the thing running in under 30 seconds
  • Commit history on both showing incremental work rather than one dump commit
Signal it

Two AI/automation projects deployed to live URLs, each with an architecture diagram, a 30-second demo clip and measured results in the README — both featured on my LinkedIn profile.

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?