[theReadora]
Beta
Ctrl + K
Sign InSign In
We're hiring

Help build the platform writers actually own

We're building a place where serial fiction pays its writers properly and readers can find what's good. It's early, the team is small, and the work is unusually visible.

See 5 open rolesInternships & fellowships
Full-Stack EngineerEngineering · Full-timeProduct Designer (UI/UX)Design · Full-timeGrowth Marketing LeadMarketing · Full-timeProduct ManagerProduct · Full-timePeople & Talent InternPeople · Internship · 3–6 months
Why this team

A small team with an unusually clear rule

If a decision is good for the platform and bad for the writer, it's not a good decision — it's a loan against the thing that makes the platform work. That constraint shapes the roadmap, and it's most of what makes the job interesting.

Remote and genuinely async

Written updates over standups. Two hours of overlap is plenty. Deep work is protected because the work needs it.

Small team, wide surface

There are more good ideas here than people to build them. You own whole areas rather than slices, and nothing is someone else's problem.

Ship, then watch

Features go out in small releases and get measured. We'd rather learn in a week than plan for a quarter.

Honest about the stage

Readora is early. Traffic is modest, the budget is small, the roadmap moves. We say so in interviews, and we're saying it here.

Open roles

5 roles, open now

Every role is remote. If you're close but not exact, apply anyway and tell us which part you'd need to grow into.

Full-Stack EngineerEngineeringFull-timeRemote

Own features end to end on the stack Readora actually runs on: Next.js App Router, TypeScript, tRPC, Prisma and Postgres, with MongoDB behind chapter content.

What you'll do

  • Ship reader- and writer-facing features from schema to interface — the editor, the chapter reader, the studio dashboard.
  • Design tRPC procedures and Prisma queries that stay fast as the catalogue grows, and keep an eye on the ones that don't.
  • Work on the parts readers feel: server-rendered chapter pages, time to first paint, and the reliability of publishing.
  • Extend the coin, subscription and payout flows without breaking anyone's earnings.
  • Review pull requests properly. On a team this size, review is the main defence.

What we need

  • Two or more years building production React, with real App Router experience — server and client components, streaming, caching.
  • Comfortable in TypeScript at strict settings, including the parts that are genuinely awkward.
  • SQL and an ORM in production. You can read a query plan and explain why something is slow.
  • You have shipped, operated and debugged something real that other people depended on.

Nice, but not required

  • Worked with tRPC, Tailwind, or a rich-text editor built on ProseMirror or Tiptap.
  • Experience with Stripe billing or a payouts system.
  • You read serial fiction. It shows in the product decisions.
The honest part

Readora is small. You will not have a platform team, a dedicated QA pass, or an on-call rotation to hide behind. You will occasionally fix something you did not build, on a Sunday, because a writer cannot publish. In exchange you get an unusual amount of say in what gets built.

Apply for this role
Product Designer (UI/UX)DesignFull-timeRemote

Shape how it feels to read a chapter at midnight and to publish one at 6am. Reading is the product; the interface should get out of its way.

What you'll do

  • Own the reading experience end to end — typography, pacing, controls, and the long tail of states nobody screenshots.
  • Design the writing side: the editor, chapter scheduling, and the studio where authors watch their work land.
  • Build and maintain the design system alongside engineering, in the components that actually ship.
  • Run small, cheap research — five writers on a call beats a survey of five hundred.
  • Design the empty, error and first-run states with the same care as the happy path.

What we need

  • A portfolio with at least one product you took from problem to shipped interface, with your reasoning visible.
  • Strong typographic judgement. This is a reading product; type is not decoration here.
  • You design in real constraints — components, breakpoints, states — not just artboards.
  • You can defend a decision and abandon it when the evidence says so.

Nice, but not required

  • You can prototype in code, even roughly.
  • You have designed for long-form reading or publishing tools before.
The honest part

There is no design team yet. You are it, which means you set the bar and also do the unglamorous parts — auditing spacing, naming tokens, redrawing the same card six times.

Apply for this role
Growth Marketing LeadMarketingFull-timeRemote

Readora has a discovery problem, not a quality problem. Your job is to get the right readers to stories that already deserve them.

What you'll do

  • Own organic growth: search, the content surface, and the long tail of story and chapter queries that bring readers in.
  • Build the writer acquisition loop — writers bring readers, readers become writers. Find where it leaks.
  • Run the channels where fiction readers actually are, and stop running the ones that don't work.
  • Turn the analytics already in the product into decisions, not dashboards.
  • Write. Launch notes, author spotlights, and contest copy all need a voice.

What we need

  • You have grown a consumer product's audience and can show what you did and what it moved.
  • Working knowledge of technical SEO — enough to argue with an engineer productively.
  • Comfortable with analytics and cohort thinking; you know the difference between a spike and a habit.
  • You write well enough that it does not need rewriting.

Nice, but not required

  • You understand fiction communities from the inside — fanfic, serials, writing forums.
  • You have run a creator or community programme.
The honest part

Traffic today is modest and the budget is small. This is an early-stage growth job: mostly finding what works, not scaling what already does.

Apply for this role
Product ManagerProductFull-timeRemote

Decide what gets built and, harder, what does not. Readora's surface area already outruns its team; the job is to aim it.

What you'll do

  • Own the roadmap for reading and writing, and keep it honest about what a small team can finish.
  • Talk to writers and readers every week, and bring back specifics rather than themes.
  • Define what a feature must do before it ships and how you will know if it worked.
  • Work with engineering and design daily — this is a hands-on role, not a ticket queue.
  • Kill things. Cheerfully.

What we need

  • You have shipped consumer product with a small team and can describe a decision you got wrong.
  • You reason with data without hiding behind it.
  • You write clearly — specs, updates, and the argument for saying no.
  • You are comfortable working without much process.

Nice, but not required

  • Background in marketplaces, creator tools, or subscription products.
  • You have run monetisation for a creator platform.
The honest part

You will not have a research team or a data scientist. Expect to pull your own numbers and run your own calls.

Apply for this role
People & Talent InternPeopleInternship · 3–6 monthsRemote

Help build the hiring process that everyone after you goes through. A real internship with real ownership, not shadowing.

What you'll do

  • Run scheduling and candidate communication, and keep it warm and fast — how we treat applicants is part of the product.
  • Source candidates for open roles and learn to spot signal in a portfolio or repository.
  • Help write and maintain job descriptions, including this page.
  • Own onboarding checklists so a new joiner's first week is not improvised.
  • Keep the applicant tracker honest.

What we need

  • Organised enough that nothing goes unanswered for a week.
  • You write friendly, clear English — most of the job is written communication.
  • Curious about how teams are built, and discreet with confidential information.
  • Available at least 20 hours a week.

Nice, but not required

  • You have coordinated something with many moving parts — a club, an event, a student society.
The honest part

This is a paid internship at a small company. You will be the only person doing this, with support but not supervision. It suits someone who would rather own a small thing completely than assist on a large one.

Apply for this role
Programmes

Internships and fellowships

Three routes in for people earlier in their career, or writers who want six months of support to finish something long. All paid.

Engineering Internship

3–6 months · Paid · Remote

For students and self-taught engineers who want to ship to production instead of building another to-do app.

You join as a working member of the team with your own features, your own pull requests and your own review responsibilities. Interns pair with an engineer weekly and present what they shipped at the end.

  • Work on the real codebase — Next.js, TypeScript, tRPC, Prisma — not a sandbox.
  • Ship to production in your first two weeks.
  • Weekly pairing and code review from an engineer.
  • A written reference and a portfolio of merged work at the end.
Apply

Readora Writers' Fellowship

6 months · Stipend · Open worldwide

A cohort programme for serial fiction writers who are serious about finishing something long.

Fellows commit to publishing on a regular schedule for six months. In return they get a stipend, editorial support, and deliberate promotion across Readora. We do not take rights to the work — the story stays yours, during the fellowship and after it.

  • A monthly stipend for the duration, independent of what the story earns.
  • Editorial feedback on structure and pacing from a working editor.
  • Featured placement and a dedicated launch for each fellow's serial.
  • You keep every right to your work. No exclusivity, no first refusal.
Apply

Design Fellowship

4 months · Paid · Remote

For designers early in their career who want a real product surface and a real user to answer to.

Fellows take a genuine problem — onboarding, the reader's controls, the studio dashboard — and own it from research through shipped interface, with weekly critique.

  • One meaningful problem, owned end to end.
  • Weekly critique with the product designer and engineering.
  • Your work ships and is credited.
  • Portfolio-ready case study support at the end.
Apply
Process

How hiring works

Five steps, about two weeks end to end. The exercise is paid, and we never ask for speculative work we'd actually ship.

  1. 01

    You apply

    One email. A CV or portfolio, and a few lines on why this role and not another. No cover letter theatre, no form with twenty fields.

    10 minutes
  2. 02

    First conversation

    Forty-five minutes with the person you would work with most closely. Mostly about what you have built and what you want to build next.

    45 minutes
  3. 03

    A practical exercise

    A small, scoped piece of real work — a feature sketch, a design critique, a growth teardown. Timeboxed and paid, and never speculative work we would actually ship.

    3–4 hours, paid
  4. 04

    Team conversation

    You meet the rest of the team and ask us the uncomfortable questions. Runway, ownership, what has gone wrong. We will answer them.

    1 hour
  5. 05

    Offer

    A decision within three working days of the last conversation, either way, with feedback if you want it.

    3 days

No form. Just an email.

Send a CV, portfolio or repository, and a few lines on which role you want and why. If none of these fit but you think we're missing something, write anyway and tell us what.

careers@readora.comBrowse roles again
Readora hires without regard to race, religion, gender identity, sexual orientation, disability, age or nationality. Need an adjustment to any part of this process? Say so in your first email — it has no bearing on the outcome. Curious what you'd be joining? Read why Readora exists.
[theReadora]

Readora - Where Stories Come Alive

Readora connects a global community of readers and writers through the power of story. Discover romance, fanfiction, teen fiction, and more.

company

  • About
  • Careers

support

  • Join Affiliate Program
  • Terms
  • Privacy
  • Comparison

community

  • Guidelines
  • Writing Contests
  • Discord
  • Twitter
  • Instagram

Follow Us on

© 2026 Readora - Where Stories Come Alive. All Rights Reserved.