How challenges work

A challenge is the unit of work on Ewance. Everything else — the certificate, the recruiter view, the catalogue — sits around it.

If you've used a course platform before, the easiest way to understand a challenge is to contrast it with what you're used to.

A challenge is not a course

A challenge starts as a brief — typically two to four pages — that lays out:

• The scenario (who you're working for in the fiction, what they need).
• The deliverable (what "done" looks like — a deck, a report, a circuit, a campaign concept).
• The constraints (time, budget, technical limits, audience).
• The rubric (what reviewers will look for when they evaluate your submission).

You'll see most of this on the challenge page before you commit. There's no surprise after you sign up.

The three layers of a challenge

Every brief is composed of three layers — they appear in the same order on the catalogue page.

1. Title

The line that hooks you. A title like "Design a low-power sensor cluster for a glacier-monitoring station" tells you the field, the constraint, and the deliverable in under fifteen words. If the title doesn't grab you, skip the challenge — there are plenty more.

2. Executive summary

One paragraph. The brief in miniature: the scenario, the deliverable, the constraint. If you can't picture the work from the summary, the challenge is probably not well-scoped for you. Move on.

3. Full description

The full brief — scenario, deliverable, constraints, rubric. Read this carefully before you commit. The clearer the brief, the cleaner your final submission will be.

What makes a good challenge for you?

A good rule of thumb: pick a challenge you'd want to talk about in an interview. If the work would make you proud to walk a recruiter through it, the credential will be worth earning. If the work feels like an exercise — the kind that looks identical to everyone else's exercise — pick a different one.

The catalogue has challenges across:

• Engineering — mechanical, electrical, structural, aerospace, biomedical.
• Computer science & data — back-end, ML, security, data engineering, distributed systems.
• Business & strategy — market entry, operations, finance, GTM, M&A.
• Life sciences — clinical reasoning, public health, biotech commercialisation, lab design.
• Design & creative — product, brand, campaign, UX research.
• Social sciences & policy — research design, programme evaluation, policy briefs.

Filters let you narrow by discipline, time commitment, and team format.

Where do the briefs come from?

Briefs come from two sources:

• Ewance's editorial team — the bulk of the catalogue. Designed in-house, modelled on real professional work without being transcripts of any specific company's project. This lets the catalogue grow quickly across many disciplines without bottlenecking on industry contributors.
• Industry partners — companies that sponsor a brief directly. These are even more apt for the learning experience because you're working on a problem shape that maps to a real company's actual priorities, and the sponsor reads your submission. Sponsored briefs are flagged on the challenge page.

This is different from platforms that promise only "Fortune-500 internal projects." Single-source formats hit a ceiling fast because real companies don't release internal work into a public catalogue at scale. Ewance pairs editorial breadth with industry depth so the catalogue keeps growing.

What you produce, you keep

A challenge is your work, full stop. You retain the intellectual property in everything you submit. We cover this in detail in Who owns your work? — the short answer is "you."

The journey

A challenge runs through four milestones. Each gets its own page:

1. Scoping and pitching — what you do before you start producing the deliverable.
2. Teams and collaboration — solo, classmate pair, or mixed-discipline squad.
3. Final submission — what "done" looks like and how review works.
4. Certificates — what gets issued when your submission is accepted.

Next: Scoping and pitching.