# Searching for talent

> How to use Ewance's filters to find candidates whose shipped work matches your role, and which signals are worth weighting.

Search on Ewance is built around one assumption: **you find candidates by what they shipped, not by what they said about themselves.**

The filter set reflects that. There is no "years of experience" filter. That is a CV-shaped question, not a portfolio-shaped one. What you do find are filters that map to "what kind of work has this person actually produced". The filters available to you can depend on your plan and the current version of the app.

## The filter set

### Discipline

The primary axis. Pick from:

- **Engineering**: mechanical, electrical, structural, aerospace, biomedical, chemical, civil.
- **Software and data**: back-end, front-end, mobile, machine learning and AI, data engineering, security, DevOps, distributed systems.
- **Business and strategy**: corporate strategy, market entry, M&A, operations, finance, consulting-shaped work.
- **Life sciences and medicine**: clinical reasoning, public health, biotech commercialisation, lab design.
- **Design**: product design, UX, brand, campaign creative.
- **Social sciences and policy**: research design, programme evaluation, policy briefs.

You can stack disciplines for roles that span fields, such as software plus product design for a generalist product-engineer hybrid.

### Deliverable type

Independent of discipline. It filters by what kind of artefact the candidate has shipped:

- **Written analysis**: reports, market analyses, research papers, policy briefs.
- **Slide deck**: strategy decks, pitches, campaign concepts.
- **Code repository**: software projects with READMEs, tests and deployment notes.
- **Design artefact**: Figma files, wireframes, brand systems, CAD models.
- **Mixed or multi-format**: combinations.

If you are hiring a strategy associate, you want slide deck plus written analysis. If you are hiring a back-end engineer, you want code repository. Filter accordingly.

### University and region

For in-person roles, visa scoping or specific alumni preferences. Coverage is broadest where the most students have joined, and it keeps growing.

### Team format

What kind of collaborator are you hiring for?

- **Solo-only** surfaces candidates whose portfolio is entirely individual work. Signal: this person can carry a project alone.
- **Team-experienced** surfaces candidates who have shipped at least one team submission. Signal: this person can integrate with others.
- **Mixed-discipline experience** is the narrowest filter. It surfaces candidates who have worked in multi-disciplinary squads. Signal: this person can translate between professional vocabularies. A strong fit for larger organisations.

### Challenge sponsor

If your team or an adjacent industry has [sponsored a challenge](https://ewance.com/companies/), candidates who completed your sponsored brief surface here. This is the highest-signal filter for sponsoring recruiters, because the candidate's first project on the platform is close to the work you would ask them to do.

### Rubric outcome

The most subtle filter. Options:

- **Accepted on first submission.** Signal: got it right the first time. Bias: rewards candidates with prior exposure to the work shape.
- **Accepted after revision.** Signal: responded well to feedback. Often a better hiring signal than first-submission acceptance, because it tells you the candidate can take criticism, integrate it and ship.
- **Both.** The default and the widest pool.

Many experienced recruiters filter for "both" or lean toward "accepted after revision". First-pass perfection is a flat signal. Responsiveness to feedback is a growth signal.

### Availability

Candidates can say whether they are actively looking, open to conversations or not currently looking. Set this loose at the discovery stage and tighten it before outreach.

## Reading a candidate's profile quickly

Once you have a shortlist, you review profiles. A good triage flow:

1. **Headline read.** Discipline, the top one or two challenges, university, year.
2. **Open one submission in full.** Pick the challenge closest to your role. Read the deliverable the way you would read a junior employee's first work.
3. **Skim the others.** What is the range? Are they good at one thing or several?
4. **Check rubric outcomes.** First-submission versus revision patterns tell you something about the candidate's growth profile.
5. **Verify one credential.** Open a verification link in a new tab. It confirms the record is real.

After these steps you will have a strong sense of whether to message. Do not message before you have read at least one submission. Generic outreach gets ignored, and you waste your own time.

## Signals worth weighting up

These tend to be under-weighted by recruiters new to skills-based hiring:

- **Range across deliverable types.** A candidate who has shipped both a written analysis and a code repository shows a flexibility CVs do not capture.
- **Submissions outside their stated discipline.** A business student who shipped a software prototype, or an engineer who shipped a strategy deck. A strong signal of intellectual range.
- **A long revision history.** A candidate who took three revision rounds to ship something genuinely hard often beats one who flew through three easy challenges.
- **Mixed-discipline squad experience.** Pays back disproportionately for larger organisations.

## Signals worth weighting down

- **Pure quantity.** Twelve easy challenges are worth less than three substantial ones. Read the work, not the count.
- **University prestige in isolation.** You can see the university, but the portfolio is the primary signal. Otherwise you are back to CV screening with extra steps.

## Saved searches and alerts

What your plan includes for saved searches, alerts and exports is shown in the app. See [ewance.com/pricing](https://ewance.com/pricing/) for what each plan offers.

## Next

Once you have a candidate you would like to talk to, read [From shortlist to hire](/docs/companies/from-shortlist-to-hire.md).
