A portfolio for remote roles has one job: to let a stranger verify, asynchronously, that you can do the work in their listing. That favors a few deep projects over many shallow ones.
Start from the bundle, not the tool
Pick your target role family and look at its top skills and most common pairs. Then design a project that uses the bundle together, the way a team would. Examples drawn from the data:
- Software engineering: a TypeScript application with a React front end and a Node.js API, backed by PostgreSQL and deployed on AWS. React and TypeScript co-occur in 117 positions.
- Data engineering: an ELT pipeline into Snowflake or BigQuery, modeled with dbt and scheduled with Airflow. Snowflake and dbt co-occur in 39 positions.
- DevOps and platform: infrastructure for a small service defined in Terraform, deployed to Kubernetes through a CI/CD pipeline. AWS and Terraform co-occur in 68 positions.
- LLM engineering: a retrieval-augmented question-answering service with evaluation, using Python, a vector store and an orchestration framework.
Make quality visible
- Tests that run in CI, with a status badge.
- A README that states the problem, the design, the trade-offs and how to run it.
- A short architecture diagram and a list of what you would do next.
- A live deployment or recorded demo where possible.
Write about it
Remote teams communicate in writing. A short write-up of a design decision or a bug you chased down demonstrates the same skill a hiring manager will rely on every day.
Every skill profile on this site ends with a concrete "how to show it" suggestion, and each learning priority includes a portfolio project that proves the whole bundle.