New: Original View reports — findings directly on the original document See what's new
Careers

Help build detection institutions can actually trust

iOriginally is a small team building a plagiarism and AI-writing detection platform — and the engines behind it — in-house. There's no sprawling job board here: just the areas we hire ahead for, and a straight way to introduce yourself.

Remote-friendlyEngines and platform built in-houseEvery introduction read by the team
Modern team workspace with desks and laptops
Working here

What you'd actually be joining

An early-stage product company with the whole problem on the table — detection quality, report design, institutional workflow — and no layer of process between you and it.

The engines are in-house

Similarity, paraphrase-aware matching, anti-masking and AI-writing analysis are built and evaluated here — not white-labelled from a vendor. Detection quality is our problem, which makes it your problem too.

The platform is the product

Original View reports, verifiable certificates, LTI 1.3 launches, self-hosted deployments — the workflow around detection is where institutions live, and we build all of it.

Small team, real ownership

You own problems, not tickets. Work ships end-to-end and lands in front of real integrity offices, instructors and students — usually much sooner than you expect.

Honest framing: we're early-stage. That means outsized ownership and direct impact — and it also means ambiguity, unglamorous work, and priorities that move. We'd rather you know both sides before you write in.
Values

What we optimize for

These show up in the product — in the policy note on every AI screen, in metering that never bills a failed check — and they show up in how the team works day to day.

Evidence over vibes

Scores are aids for human judgment, never verdicts. Everything we ship has to show its work — matched spans, sources, sentence-level probabilities — so an integrity office can defend a decision, or overturn one.

Honest numbers

No invented statistics in the product or the marketing, no metering tricks, and comparison pages that admit where competitors lead. If we can't back a number, we don't print it.

Institutions own their data

Student work never trains models. Retention, export and deletion stay under the institution's control, and fully self-hosted deployment is a first-class option — not a concession we make reluctantly.

Ship end-to-end

One team owns the path from detection research to the PDF an integrity office files. You see your work in use — and you hear about it directly when it falls short.

Open directions

Areas we hire ahead for

These aren't vacancies with closing dates. They're the areas where the roadmap will need people — and where we read every introduction that comes in.

Detection research

Similarity matching, paraphrase detection and AI-writing analysis — building corpora, evaluating detectors honestly, and hardening them against homoglyph and masking tricks.

Remote-friendlyExpression of interest
Introduce yourself

Full-stack engineering

The platform around the engines — exact-layout report viewers, submission pipelines, LTI 1.3 integrations and self-hosted deployments — across the web app, APIs and document pipeline.

Remote-friendlyExpression of interest
Introduce yourself

Institutional success

Onboarding, training and policy guidance for integrity offices — helping institutions use similarity and AI signals responsibly, from first evaluation through exam season.

Remote-friendlyExpression of interest
Introduce yourself
No fake job board: when a role does open, it starts from the introductions on this page. If your work fits one of these areas — or argues for one we haven't listed — write in.
The process

How introducing yourself works

1

Write to us

Email careers@ioriginally.com with whatever shows your work best — a repo, a paper, something you shipped, or a straight letter about what you'd want to build here.

2

We read it

Introductions go to the team, not a tracking system. We read every one, and we reply when we can see a fit — for a role now, or for one we hire ahead for.

3

We talk about the work

If there's a fit, the conversation is about the problems themselves — detection quality, the platform, institutions — not whiteboard riddles.

Think you should be here?

Tell us what you'd build. A short, specific introduction beats a long CV — and the team reads all of them.