01 / How we work
A small team and a high bar.
Ren is early. The founding team is small and the bar is high. Join now
and you own a surface, not a ticket queue: work that's still
load-bearing two years from now. Every task Ren completes also teaches
it how an institution actually behaves versus how it claims to, and
that map is the company. You'd be building it.
We hire for the same short list across every role:
/Slope over pedigree
We don't care where you've been. We care how fast you climb and
how hard you sweat the details.
/Craft
You finish the part nobody sees. You can tell the difference
between something that works and something that's right.
/Ownership
You don't escalate problems, you close them. You pick the thing
up and carry it.
02 / Open roles
Pick the surface you want to own.
ROLE 01
Internship / Multiple tracks
Internships
A term where you ship something people actually touch, not a research
branch that dies on a Friday. You'll take a real piece of Ren and
own it end to end, with the founders in the room.
We take interns across
-
Client / iOS. The app where a live call becomes
something you can watch and trust.
-
Backend / agent. The systems that let Ren make a
phone call and drive a browser to finish a task.
-
Design. The interaction details that make handing
off a dreaded task feel calm instead of like more work.
-
Growth. The channels, pages, and creative that
get Ren in front of the people who need it most.
What we look for
You've built something on your own before anyone asked you to, and
you can point to it.
ROLE 02
Full-time / Client
iOS Engineer
The app is where a task Ren runs in the real world becomes something
you can watch and trust. You hand off something you've been dreading,
then see the call transcript stream in live, the browser pilot
itself, the one decision that needs a human surfaced for a tap, and
the result land. That surface is wide open and it's everything.
You'll go deep on at least one of these
-
The live task surface. The real-time view of a
call or browser action in flight. Duration overlays, the seams of
a genuine hold, the moment Ren pauses and hands the decision back.
-
System integrations. Push is live today. App
Intents, Shortcuts, and Live Activities are next: the entitled APIs
that let a task start and surface anywhere on the phone, not just
inside the app.
-
Conversation. Today you talk to Ren on a real
phone call it places to you, and type in the app between calls.
Making that hand-off seamless, and deciding what on-device voice
should become, is wide open.
-
Interaction craft. SwiftUI, motion, the small
details that make delegation read as relief, not another inbox.
What we look for
You've shipped something real (App Store, TestFlight, a project
people use), and you know what Apple's APIs do versus what
the docs claim.
ROLE 03
Full-time / Core
Member of Technical Staff
The hard center of Ren: getting one real-world task done by moving
between a live phone call and a browser session, reliably, as
concurrency grows. One missed task costs trust permanently, so
reliability isn't a chore here. It's the product.
T-shaped, deep in at least one
-
Agent runtime & orchestration. Deciding when
Ren calls, when it clicks, when it stops and asks you. Tool use,
model selection, and output quality in production.
-
Telephony & voice. Real-time audio over Twilio
and the OpenAI Realtime API, sub-second latency, the difference
between a call that sounds human and one that gets hung up on.
-
Reliability & evals. Making
"Ren did the thing" true every single
time, and proving it with evals instead of vibes.
-
The operational map. Turning every completed task
into structured knowledge of how a booking platform, an airline, or
a clinic actually behaves. The flywheel that compounds with usage.
Our stack
We work mostly in Node on
Firebase Cloud Functions and
Cloud Run, with
Firestore, Twilio, and real-time model
APIs in the loop. Not knowing our exact stack isn't a dealbreaker;
depth and ownership are.
ROLE 04
Full-time / Growth
Marketing Engineer
Ren's growth doesn't come from a clever headline. It comes from
being measurably, provably useful about things everyone hates. You
build the engine that proves it: programmatic pages, compounding
loops, and data nobody else has.
You go deep on at least one of these
-
Data as marketing. Ren makes real calls every
day, which means we can publish what no one else can: a hold-time
index for the companies everyone dreads, a difficulty ranking for
canceling a subscription, the real cost of bureaucratic friction.
You turn that into pages people link to and journalists cite.
-
Programmatic & SEO. Landing pages at scale
for every task, institution, and city Ren handles. A moat under
the funnel that doesn't depend on spend.
-
Loops & lifecycle. Referral, retention, the
"Call Ren" hotline as a permanent civic
reference rather than a campaign.
-
Paid, when it earns its place. Reading a
campaign, killing what doesn't work, putting weight behind what
does.
What we look for
You ship pages, not decks. You do not wait for permission to test
something.
ROLE 05
Full-time / Creative
Creative / UGC
Ren's best ad is a real recording: Ren getting someone's flight
refunded, talking a plumber down on a quote, paying off a parking
ticket while the user does nothing. The work is real moments, cut
well, not hype over a product shot.
You go deep on at least one of these
-
Production at volume. UGC, static, and video,
shipped every week. You have a point of view on what makes a hook
land and a system for testing it.
-
Story from real calls. Mining actual Ren task
recordings for the funny, the impressive, the deeply relatable,
and turning them into things people send to a friend.
-
Tone. Ren is institutional with warmth: calm,
precise, a little dry. You can hold that voice instead of
defaulting to the same hype every AI ad uses.
What we look for
Send the thing you made that performed, and tell us why it worked.