🔥 Live 2,847 QA engineers learning right now — Start Free Automation Roadmap →
SDET · Portfolio

The GitHub profile that proves you can do it

Recruiters will open your GitHub. Two or three clean automation projects prove your skills before you say a word. Here are three that cover the full SDET stack.

Updated for 2026 · ~9 min read · by Naveed Tawargeri

Recruiters and interviewers will open your GitHub. An empty or messy profile undoes a strong resume; two or three clean, well-documented automation projects prove your skills before you say a word. Here are three portfolio projects that cover the full SDET stack — build these and you have concrete answers for every "have you worked with…" question.

Three projects that prove your skills

Project 1: E2E Web Automation Framework

PurposeShowcase: Selenium, Java, POM, TestNG, CI/CD, Docker, Reporting
StackJava 17 + Maven + Selenium 4 + TestNG + Allure + Jenkins + Docker
What to automateOpen source site: OrangeHRM (free demo) or AutomationExercise.com
Key featuresPOM architecture, TestNG parallel execution, Allure HTML report, Jenkinsfile, Docker Compose Grid
README must includeArchitecture diagram, how to run, CI badge, Allure report screenshot, Docker Grid screenshot
Estimated time2–3 weeks to build properly
Impact on salaryDirectly proves Phase 1+2 skills. Most important project.

Project 2: API Automation Framework

PurposeShowcase: RestAssured, Java, API design, CI/CD integration
StackJava + Maven + RestAssured + TestNG + GitHub Actions + Allure
What to automateReqres.in (free fake API) or JSONPlaceholder — full CRUD coverage
Key featuresRequestSpec/ResponseSpec, chaining, schema validation, data-driven tests, GitHub Actions workflow
README must includeAPI coverage table, how to run, GH Actions badge, sample response assertions
Estimated time1.5–2 weeks
Impact on salaryProves RestAssured expertise — most asked in product company SDETs

Project 3: Mobile Automation (Appium)

PurposeStrengthen 'exposure' → 'hands-on experience' for Appium
StackJava + Appium + TestNG + Android Emulator (free) + Page Object Model
What to automateAndroid Emulator + open-source app OR ApiDemos.apk (bundled with Android SDK)
Key featuresAppiumDriver setup, POM for mobile, TestNG suite, touch actions, scroll/swipe
README must includeSetup instructions, emulator config, test run GIF/screenshot
Estimated time1–1.5 weeks
Impact on salaryConverts 'exposure' to proven skill. Differentiator vs other candidates

What makes a portfolio project actually count

  • A real README — architecture diagram, how to run, what it demonstrates. Most candidates skip this; it is the first thing a reviewer reads.
  • Clean commit history — small, meaningful commits, not one "initial commit" dump.
  • It runs — a reviewer should be able to clone and run it in minutes. Include setup steps and, ideally, a dockerised run.
  • It maps to the job — the stack should match what your target companies use.
✍️ Link your reposOnce you have built these, link your actual GitHub repositories here so this page doubles as your portfolio index.

Build, then prove it in the interview

These projects answer the framework and API rounds directly.

Framework Simulator → Docker + Grid Resume Builder

Frequently asked questions

What projects should an SDET have on GitHub?

A web E2E automation framework, an API automation framework, and a mobile automation project cover the full stack. The three above specify the exact stack and features for each.

Do recruiters actually look at GitHub?

Yes — for SDET and engineering roles, interviewers routinely open your profile. Clean, documented projects prove your skills before the interview.

How long does it take to build a portfolio project?

Roughly two to three weeks per project to build it properly with a good README and clean structure. Quality beats quantity — three solid projects beat ten half-finished ones.

What makes a portfolio project stand out?

A real README with an architecture diagram, clean commit history, an easy way to run it, and a stack that matches your target companies.

Tool versions in the stacks evolve — use current Selenium/RestAssured/Appium versions when you build.

Related guides & practice