Careers at Vampelium Inc.

The work is ordinary.
That's what makes it serious.

We build the everyday services people keep their lives in — files, messages, an assistant, and the protection around them. There are no roles open today. This page is where that will change first.

Hiring status

No open roles

We're not hiring right now.

We could fill this page with roles we might open one day. We'd rather show you an empty page that's true. When we do open something, it will be described here in plain words — the actual work, and what we can honestly say about it — before it appears anywhere else.

Open roles
0
Posted at
vampelium.com/careers
Last reviewed
26 September 2026

What happens when a role opens

  1. It gets written down here

    One posting, on this page, describing the work someone would actually do in their first few months.

  2. The awkward parts are in the posting

    Where the work happens, how it's paid, and who you'd be working alongside are stated in the posting itself — not discovered three conversations later.

  3. One route in, and it works

    A single way to apply that reaches a person. [TO BE CONFIRMED: how applications will be received — no applicant tracking system is in place]

Careers enquiries

Applications are not open.

We are not collecting CVs or candidate introductions. General questions about future roles can go to careers@vampemail.com; do not include candidate personal details.

How to reach us

Careers enquiries

We are not accepting candidate applications or keeping introductions on file. You may ask about future roles without sending a CV or other candidate details.

careers@vampemail.com

A candidate retention policy, deletion procedure and application instructions will be published before recruitment opens.

Go to our contact page

What we'll do with it

What you can expect back

There are no open roles and no application process at present. We will publish application instructions and a candidate retention policy when a role opens.

  • No unpaid trial projects, ever
  • A straight answer instead of a maybe
  • Privacy questions: privacy@vampemail.com

Interview steps and timings: [TO BE CONFIRMED: hiring process, once a first role is defined]

What you'd be working on

One account. A whole family of everyday services.

An account, files and photos, messaging, an assistant, sync, protection and the compute underneath — built to behave like a single product, because that's how they're made.

The product

Things people use without thinking

The photographs someone would be devastated to lose. The document they need on the worst day of the year. The message that has to arrive. Our services sit in the most ordinary parts of people's lives, which is exactly why the standard is high: nobody applauds software that works, and everybody notices software that doesn't.

  • One sign-in across every service
  • The same on every device someone owns
  • Privacy controls on one screen, not buried
The job

Harder than it looks, on purpose

Making seven services feel like one is the difficult part. So is a recovery flow that a tired person can complete at two in the morning, and a default that protects someone who will never open the settings screen. If you like the invisible work — the part users never see because it simply behaved — you'd recognise this place.

  • Care about the worst case, not the demo
  • Finish things, including the unglamorous ones
  • Say clearly when something isn't good enough yet
How we work

The same four commitments, from the inside.

These are the principles we publish on our About page. They aren't a poster in a hallway — they decide what gets built, what gets refused, and what a good day here looks like.

01

People first

We build for the person holding the phone, not the feature list. Here that means you'll be asked who a change helps, and "it's technically correct" is not an answer. If something needs explaining twice, we've built it wrong, and we go back and build it again.

02

Nothing to set up

Our services are built to fit together, so everything works from the moment someone signs in. That standard is paid for in the work: shared foundations, fewer special cases, and the patience to make the seam disappear rather than document it.

03

Private and secure

Privacy is a property of the product, not a premium tier. Protective defaults, the least access a feature actually needs, and the discipline to argue for collecting less — including when collecting more would have been convenient for us.

04

Straight answers

We say what we collect and why, and when something goes wrong we explain what happened. Internally it's the same rule: bad news early, plainly, without the padding. That applies to how we talk to candidates too.

Straight answers

Things we're not going to guess at.

Principle 04 applies to this page as much as to anything we ship. Here's what we can't state yet, marked as exactly that.

  • How many of us there are

    A number we're not going to round up for effect.

    [TO BE CONFIRMED: team size, if we choose to publish it]

  • Where the work happens

    Remote, hybrid, or somewhere in particular — this will be stated in the first posting rather than implied by a photograph.

    [TO BE CONFIRMED: working location and remote policy]

  • How roles are paid

    We'd rather publish a range than make you ask for one. We just don't have one to publish yet.

    [TO BE CONFIRMED: compensation approach and published ranges]

  • What comes with the job

    Leave, equipment, healthcare and the rest. No list here until there's a real one.

    [TO BE CONFIRMED: benefits, once a first role is defined]

Still here?

Nothing open today. Say hello anyway.

If the work described on this page sounds like yours, we'd like to know you exist before we need you. Come back to this page for postings — it's the only place they'll appear.

Careers enquiries: careers@vampemail.com