How recruiting works on Ewance

Recruiting on Ewance is a four-step loop. Most teams settle into it within an afternoon.

1. Search

You open the talent search and filter the pool by what matters for your role:

• Discipline — engineering (with sub-disciplines), software, data, business, life sciences, design, social sciences, policy.
• Deliverable types completed — e.g. "shipped a market analysis," "shipped a code repo with tests," "shipped a clinical decision tree."
• University and region — useful for in-person roles, visa scoping, or alumni-network preferences.
• Team format — did they ship solo, in pairs, or in mixed-discipline squads? Different signals for different roles.
• Challenge sponsor — students who completed challenges sponsored by you (or by an adjacent industry) surface here.
• Rubric outcome — accepted on first submission, or accepted after revision. Both are valid signals, depending on the role.

The result is a list of candidates, sorted by how closely their portfolio matches your filter. We cover this in detail in Searching for talent.

2. Read the work

This is the step Ewance is built around. Every candidate row in your search result opens into a portfolio of the challenges they completed, with:

• The challenge brief — what was asked.
• The candidate's role — solo, pair, or squad (and if squad, the specific role they played).
• Outcome — accepted, accepted-after-revision, or in progress.
• A verifiable credential link — where you (or your ATS) can confirm the credential is real.

For most candidates, you can read at least one full submission to gauge how they think. A 10-page market analysis tells you more about a junior strategy hire than any phone screen would.

3. Reach out

When a portfolio fits, you message the candidate directly. The message lands in their Ewance inbox and also gets emailed to them.

There's no bidding, no escrow, no platform-mediated negotiation. The conversation moves to your normal channels (email, calendar, ATS) as soon as both sides want it to.

Best practices we see:

• Tell them which work caught your eye. Generic outreach gets ignored; specific outreach ("your market analysis on Spanish solar caught my eye because we're hiring for our renewables analyst team") gets replies.
• Be honest about the role. Junior students appreciate clarity on level, comp range, and timeline. You'll lose less of your own time too.
• Don't oversell. If the role is a contract or a temp role, say so. Strong students have options.

4. Interview and hire

From here, Ewance steps out of the way. You run your normal interview process. You make your offer. You hire them.

The candidate can revoke your messaging access at any time if they're no longer interested — they're not contractually bound to engage with you. (You wouldn't want them to be, either; non-mutual interest at the recruiter stage is not the foundation of a good hire.)

What Ewance doesn't do

Worth being explicit about, so you can build it into your own process:

• No comp data. We don't surface salary expectations. Talk to candidates directly.
• No background checks. Standard caveat — credentials prove the work was shipped; they don't prove general professional history. Use your normal background-check vendors.
• No applicant tracking. Most recruiters drop candidates from Ewance into their ATS when they move to interview. We integrate via simple links/CSV export rather than via deep ATS sync (for now).
• No automated outreach. Bulk messaging is not supported on the free tier. It will be supported on a paid tier when that launches, with rate limits.

What about active candidates?

Every candidate has an availability signal: actively looking, open to conversations, or not currently looking. The pool skews toward students still studying and recent graduates, so most are at one of the first two states.

You can filter by availability. If you're looking for someone right now, set the filter to "actively looking" + "graduating this term." If you're building a longer pipeline, "open to conversations" widens the pool considerably.

How long does the loop take?

Typical first-search-to-first-message: 20 minutes. Typical first-message-to-first-reply: 2-3 business days for engaged candidates. Typical first-message-to-interview-loop: 1-2 weeks if both sides move.

Faster than a traditional inbound pipeline. Comparable to a good agency-sourced pipeline, with the difference that the cost is zero and you're reading their work yourself rather than trusting an agency's screening.

Next

To understand exactly what the credential proves and what verification looks like: Verified credentials.