Build the workspace research is written in.

Folio is opening six roles across engineering, design and brand, partnerships, implementation and support. Each one owns a part of the product outright, from deciding what it does to answering for it in production.

See the roles Apply

Six roles, opening soon

Apply now and you hear about your role before it is posted anywhere else.

What Folio does

Folio is one workspace for researching, writing and checking a paper. While the work happens, Folio keeps a record of it: which sources were opened, whether each quotation matches its page, and how the draft changed between saved versions. At submission the record goes with the paper, and an instructor or reviewer can check it without taking anyone’s word for it.

The product exists because universities began judging student work with AI detectors, which return a probability nobody can verify. A record of how the work was made can be verified, and building that record well is the job.

The rules every role works under

  • It does not write your paper.Scholar finds sources, checks citations and reviews an argument when asked. No feature in Folio writes into your document.
  • It checks what can be checked.Folio does not score writing for signs of AI. It resolves each reference against Crossref, OpenAlex and the other public databases, flags retracted papers, and matches quotations to the page they came from.
  • It does not watch you type.The authorship record is built from saved versions of the document. Folio does not log keystrokes and does not build behavioral profiles.
  • Your work stays yours.Documents and sources are stored encrypted, never sold and never used to train models. You can export everything or delete your account at any time.

How the work runs

Remote

The team works remotely. Where you live matters only for planning overlapping hours.

Ownership

Each role runs an area outright: deciding what it should do, building or running it, and writing the words inside it.

Written decisions

Decisions are written down next to the code or document they affect, so the reasoning survives without a meeting about it.

AI, used openly

AI tools are part of daily work in code, design and writing. The expectation is to read the whole diff, check the citation, and answer for anything shipped under your name.

The roles in full

Open one to read the work, what you need, and what helps.

EngineeringEngineer Opening soon

Owns one area of Folio end to end: what it should do, how it is built, and whether it holds up in real use. Remote.

The work

  • The writing surface. Citations in Folio are structured objects, and they have to survive copy and paste, undo, two people editing at once, and export to Word.
  • Or the integrity checks: matching a quotation to the page it came from, reconciling references against the public citation databases, and producing a record an instructor can verify.
  • Or the institution side, where a university runs Folio under its own name, with its own rules about who can see what.
  • And the maintenance that comes with any of these: migrations, the bug that only appears in one person’s document, and the export that has to stay correct while an upstream service is down.

What you need

  • You have built something and kept it running in production for a good while.
  • You write TypeScript fluently and are comfortable with a relational database.
  • You have worked where correctness mattered more than speed.
  • You test with the messiest input you can find. In academic writing, messy input is the usual case.

Helps, not required

  • Experience with a rich-text editor or a canvas surface.
  • Experience with real-time collaboration.
  • An export you shipped that had to be exactly right, in publishing, law or finance.
Apply for this role
Design and brandDesigner Opening soon

Responsible for how Folio looks and how it reads, on the website and inside the product. Remote.

The work

  • The identity. Folio should read as an academic tool, which comes down mostly to typography and restraint. The current system is a starting point to take further.
  • Illustration and icons for abstract ideas such as provenance, verification and authorship, where the usual visual shortcuts do not help.
  • The words: headlines, button labels, the line under a form field, release notes. About half of the job is writing.
  • The hard cases: Arabic and Hebrew running right to left, dark mode, and small phones.

What you need

  • A portfolio with a clear point of view.
  • Close attention to type, down to the choice of one italic at one size, and the ability to explain it.
  • You write well, in full sentences as well as headlines.
  • You have talked a team out of a design that looked impressive and was wrong.

Helps, not required

  • You can build what you design, at least as far as a working page.
  • You have set up a design system that other people used without needing you.
  • You have designed for a right-to-left language.
Apply for this role
PartnershipsUniversity partnerships Opening soon

Brings Folio into universities and keeps those relationships healthy after the contract is signed. Remote.

The work

  • Conversations with the people who decide: usually a dean, a registrar, someone from IT and the faculty who will use the product. Each wants something different, and the demo changes with the audience.
  • Procurement: the security review, the data agreement, a pilot with one department, a committee that meets monthly, and the question of which budget pays. It is slow, and it is most of the job.
  • Reporting blockers precisely. Integration with existing systems and the location of data decide most deals, and the product team needs the specific constraint.
  • Keeping accounts after signature: getting a department started, noticing when instructors stop using Folio, and finding out why. One renewal is worth more than three trials that fade.

What you need

  • You have sold to a university or worked inside one, and a sales cycle measured in semesters does not surprise you.
  • You can talk to an IT director without bluffing and to a dean without talking down.
  • You promise only what the product does. In this sector one oversold feature can end a relationship.
  • You are comfortable with a small number of accounts that each matter a great deal.

Helps, not required

  • Experience of a procurement process from the inside.
  • Familiarity with the systems universities already run.
  • Arabic or Hebrew, both of which Folio supports throughout.
Apply for this role
ImplementationImplementation lead Opening soon

Takes a newly signed institution to a department that runs real coursework through Folio within weeks. Remote.

The work

  • The first ninety days of each institution: importing the roster, setting up sign-on with their IT team, branding, terms, courses and permissions.
  • Training faculty who did not choose Folio and have taught the same way for years. The work is persuasion as much as instruction.
  • Being the named contact the institution calls. Universities want one accountable person, and at the start that is you.
  • Renewal, which is decided long before anyone discusses it: watching whether departments use Folio for real work, and stepping in early when they do not.

What you need

  • You have onboarded organizations rather than individual users, and can run a training session for people who did not ask to be there.
  • You can keep a project on track for months, because these rollouts run over whole terms.
  • Your follow-up emails are clear enough that an institution trusts them.

Helps, not required

  • Experience inside a university, in a registry, faculty office or IT department.
  • You have moved an organization off a system it had used for years.
Apply for this role
SupportSupport Opening soon

The person students and staff reach when something breaks, often in the week it matters most. Remote.

The work

  • First response for students and instructors. Term time follows deadlines, so a problem at eleven at night before a submission is an emergency.
  • Reproducing issues properly, fixing the small ones yourself, and giving engineering a report it can act on.
  • The help center, which should answer common questions before anyone has to ask them.
  • Reporting patterns. Support sees recurring failures weeks before anyone else does, and that knowledge shapes the product.

What you need

  • Technical enough to reproduce a bug, read a log and run a query, even when someone else writes the fix.
  • You write calmly and plainly to people who are stressed and short on time.
  • You can tell what is urgent from what can wait until Monday, and you are usually right.

Helps, not required

  • Experience supporting an education product or working at a university help desk.
  • SQL, or the willingness to learn it in a couple of weeks.
Apply for this role
EngineeringIntegrations engineer Opening soon

Connects Folio to the systems a university already runs, which is often what turns a pilot into a contract. Remote.

The work

  • Single sign-on with SAML and OIDC, against whatever identity provider the institution uses, including providers that read the specification creatively.
  • Rostering: getting students and staff into the right courses from the system of record, whether it offers an API or drops a file every night.
  • Standards-based interoperability, so Folio can work next to an existing LMS without replacing it first.
  • Making all of it debuggable. When a sync fails on the first morning of term there are hours to fix it, and the cause has to be visible immediately.

What you need

  • You have shipped SAML or OIDC in production and dealt with a provider that did not follow its own documentation.
  • You are comfortable with retries, partial failures, idempotency, and two systems that disagree about the same student.
  • You write documentation an IT department can follow without a call.

Helps, not required

  • LTI, education rostering standards, or a student information system integration.
  • Experience on the institution side of one of these projects.
Apply for this role

Apply

A short note and a couple of links say more than a CV. Applications are read by the people you would work with.

Only used to reply to you.

Choose “Something else” if none of them quite fit. Those notes are often the interesting ones.

A repo, a site, a portfolio, a paper, something you sold. One per line is fine.

CV or resume

Optional.

A city or a time zone is enough. It helps plan overlapping hours realistically.

This is read first. What caught your interest, and what you would want to work on. A few sentences is plenty.

Comes straight to the team.

Questions

When do these roles open?
Soon, and not all at once. Anyone who applies now hears about their role before it is posted anywhere else.
Where is the team?
Remote. The application asks where you are based so that overlapping hours can be planned realistically.
What happens to an application?
It arrives as an email and a person reads it in full. There is no applicant tracking system or screening software in front of it.
What if none of the roles fits?
Apply anyway. Choose “Something else” and describe work you have finished. That says more than a matching job title.

Apply before the roles are posted.

Say which role is yours and what you would do with it. A short note is enough, and it goes straight to the people you would work with.

Apply More about Folio