Asire

Build something real,
and keep it in your portfolio.

These are unpaid positions. You're trading your time for portfolio work with real users behind it, and we'd rather you knew that in the first ten seconds than the last.

Apply for a role

Open role

Where we need help

The Product Designer role below has been filled. We're still hiring for Cybersecurity Specialist.

Product Designer Filled

This role has been filled — thanks to everyone who applied.

Rethink the product, then draw the version we should have built.

What you'd do

  • Conceptualise the app end to end — what it is, who it's for, and where the current design is fighting the user.
  • Rebuild the UI in Figma as a proper design system: components, tokens, states, not a folder of disconnected screens.
  • Produce mockups we can actually hand to an engineer, including the empty, loading, and error states everyone skips.
  • Design the UI for new features as they come up, and stay in the room while they're built.

What we're looking for

  • A portfolio or Figma file we can open and read — process matters more to us than polish.
  • Comfort with components, auto-layout, and variants. You should be building a system, not decorating screens.
  • The willingness to argue for a design decision, and to drop it when the argument doesn't hold.
Cybersecurity Specialist

Try to break what we shipped, then tell us exactly how you did it.

What you'd do

  • Test the products — web app, desktop build, mobile app, and the API behind all three — against a scope we agree up front.
  • Probe the parts that actually decide things: authentication, workspace role enforcement, invitations, file uploads, and the public endpoints.
  • Write findings up so they're reproducible and ranked by real impact, not by scanner severity.
  • Re-test after we fix, and tell us plainly when a fix doesn't hold.

What we're looking for

  • A GitHub profile, write-ups, CTF work, or lab notes — anything that shows how you think through a target.
  • Working knowledge of the OWASP Top 10 and a tool you're fluent in, whether that's Burp, ZAP, or your own scripts.
  • The discipline to stay inside an agreed scope and to report rather than exploit. This is authorised testing, with rules.
Before you apply

There's no money in this

These roles are unpaid — no salary, no stipend, no equity. We'd rather say that plainly on the page than let you find out on a call after you've written an application.

What we're actually offering is the thing that's hard to get on your own: a live product, real users, and work that someone will hold you to. If that trade isn't worth it to you right now, that's a completely reasonable call, and we'd rather you made it before applying than resent it after.

We'll put the arrangement — scope, hours, how long, and what you're free to publish — in writing before you start, so there's nothing to be surprised by later.

Apply

Tell us who you are

Ten minutes, honestly answered, beats an hour of polish. We read every one of these ourselves.

Pick the role you're applying for

Your name is required

Enter an email we can reach you on

Somewhere we can open without requesting access. A Figma community file, a Behance page, a PDF on Drive set to "anyone with the link" — all fine.

Add a link to your work

Add a GitHub profile or a link to your write-ups

What you'd want to change about Asire, or what you'd test first and why. Specific beats enthusiastic.

A couple of sentences at least — tell us what you'd actually do

We'll email you a confirmation, then get back to you either way. Your details go to us and nowhere else.