Product Engineer
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 2d ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 131d ago
The date the source published, not the day we noticed it (2026-06-01). Last seen at its source 2h ago.
We have tracked this listing since 5 Oct 2026 (5 days). The employer's own board has carried it every time we have read it, most recently 2 hours ago.
Is it remote?
Remote
That is the location the employer filed this posting under. Quoted as written — we do not re-word the source's own location.
Who may apply?
Not stated
The description states no restriction of its own. This is the source's own tag.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Ashby employer's own board first seen 5d ago · last seen 2h ago
The listing
Build the Future of Autonomous Companies
At Twin, we're building a world where anyone can deploy AI agents capable of running real business operations.
Not chatbots.
Not copilots.
Autonomous agents that take actions, make decisions, execute workflows, and create value.
In just a few months, we've seen explosive adoption, thousands of users building businesses on top of Twin, and millions of agent actions executed.
We're still at the beginning.
We're looking for a Founding Product Engineer to help build the company that builds companies.
The Role
This is not a traditional software engineering role.
You won't receive tickets from a product manager.
You won't spend months discussing roadmaps.
You won't optimize a tiny corner of an existing system.
You'll work directly with founders, users, and other builders to design, build, and ship product every day.
You'll move across product, engineering, design, AI, infrastructure, and growth whenever needed.
One day you might:
Build a new agent capability from scratch
Design an onboarding flow that doubles activation
Improve infrastructure supporting millions of executions
Talk directly with power users
Ship a feature in the morning and iterate on feedback the same afternoon
Use AI to prototype something in hours that would previously have taken weeks
If that sounds exciting, keep reading.
Who We're Looking For
We're looking for builders.
People who create.
People who ship.
People who don't wait for permission.
You might be a fit if:
You've built products people actually use
You've launched startups, side projects, open-source projects, or meaningful products
You think about users as much as technology
You enjoy turning ideas into reality extremely quickly
You thrive in ambiguity
You naturally take ownership
You care about product quality
You love learning
AI-Native Engineering
We believe the best engineers of the next decade will not be those who type the fastest.
They will be those who can effectively direct, evaluate, and collaborate with AI.
AI coding assistants should already be part of your daily workflow.
Cursor.
Claude Code.
Codex.
Or whatever tools help you move faster.
You should be comfortable:
Pair-programming with AI
Generating and reviewing large amounts of AI-generated code
Using AI for debugging, prototyping, testing, and research
Building dramatically faster without compromising quality
Leveraging AI as a force multiplier
The question is no longer:
"Can you write the code?"
The question is:
"Can you use AI to build the right thing, verify it, and ship it?"
Strong Signals
These are not requirements, but they tend to correlate with success here:
Former founder
Early-stage startup experience
Open-source contributor
Exceptional side projects
Competitive programming background
Olympiad participant
Hacker mindset
Product obsession
Evidence of unusually fast learning
What We Value
Ownership
You see a problem, you solve it.
Speed
Fast iteration beats endless planning.
Judgment
Good decisions scale better than good code.
Ambition
We're building something that shouldn't be possible.
Craft
Fast doesn't mean sloppy.
Why Twin?
Most companies hire engineers to execute a roadmap.
At Twin, you'll help define it.
Most engineers optimize existing systems.
At Twin, you'll help invent new ones.
Most jobs offer impact on a feature.
This one offers impact on the future of the company.
If you've ever thought:
"I wish I had joined earlier."
This is one of those moments.