# Getting started for students

> Open an Ewance account, pick a challenge that matches your studies, and ship your first deliverable.

You can be inside your first challenge quickly. Earning the certificate takes longer, because that depends on the brief, but signing up does not.

## What you need before you start

- An email address. A university one is fine but not required.
- A rough idea of what you study, so the catalogue can suggest challenges that fit your discipline.
- A web browser. That is it.

You do not need:

- A payment card to start. The free plan does not need one.
- An invitation code, a university partnership or a letter of reference.
- A team. You can work solo if that is how you want to start.

## 1. Create your account

Go to [app.ewance.com/sign-up](https://app.ewance.com/sign-up) and create an account. The free plan lets you explore Ewance and start earning a verified credential. Paid plans give you more verified credentials over time, and you can upgrade at any point, so there is no need to decide now. Plans are on [ewance.com/pricing](https://ewance.com/pricing/).

## 2. Pick a challenge

When you land in the catalogue, filter by:

- **Discipline**, for example engineering, business, life sciences, design or computer science.
- **Time commitment**, from short challenges to capstone-style projects.
- **Team format**: solo, classmate pair or mixed-discipline squad.

Read the **executive summary** first. It is the one-paragraph version of the brief. If it sounds like work you would want to talk about in a job interview, open the full description.

> **Tip:** A challenge slightly outside your comfort zone makes a more credible portfolio piece than one you could do in your sleep. Recruiters can tell the difference.

## 3. Move through the journey

Every challenge has the same shape:

1. **Scoping.** You write a short scoping document. What is the problem really asking? What is in and out of scope? This is where most strong submissions are won.
2. **Pitching.** You present an early solution direction so reviewers can flag dead ends before you sink time into them.
3. **Collaboration.** The actual work. If you are in a team, this is where coordination matters.
4. **Final submission.** You upload the deliverable. The format depends on the challenge: a slide deck, a written report, a code repository, a design file.

Each step is covered in [How challenges work](/docs/students/how-challenges-work.md) and the pages after it.

## 4. Get reviewed and earn your credential

Submissions are reviewed against the rubric stated in the challenge brief. When a submission is accepted, Ewance issues your verifiable credential. See [Certificates](/docs/students/certificates.md) for what that means and how it works.

Your certificate is anchored on a public blockchain (Base) and is verifiable forever by anyone with the link. Even if Ewance disappeared tomorrow, the cryptographic proof stands on its own.

## What is next

- To see how a challenge unfolds: [How challenges work](/docs/students/how-challenges-work.md).
- If you are already in one and want to get the early milestones right: [Scoping and pitching](/docs/students/scoping-and-pitching.md).
- To see how recruiters read your credentials: [the Companies section](/docs/companies.md).
