You have opted out of job matches in .
To undo this, go to the 'Skills and Interests' section of your preferences.
Shared by 
9 days ago
warning
Heads-up
Requirements and responsibilities
The RoleThis 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 scratchDesign an onboarding flow that doubles activationImprove infrastructure supporting millions of executionsTalk directly with power usersShip a feature in the morning and iterate on feedback the same afternoonUse AI to prototype something in hours that would previously have taken weeksWho We're Looking ForWe'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 useYou've launched startups, side projects, open-source projects, or meaningful productsYou think about users as much as technologyYou enjoy turning ideas into reality extremely quicklyYou thrive in ambiguityYou naturally take ownershipYou care about product qualityYou love learningAI-Native EngineeringWe 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 AIGenerating and reviewing large amounts of AI-generated codeUsing AI for debugging, prototyping, testing, and researchBuilding dramatically faster without compromising qualityLeveraging AI as a force multiplierThe 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 SignalsThese are not requirements, but they tend to correlate with success here:Former founderEarly-stage startup experienceOpen-source contributorExceptional side projectsCompetitive programming backgroundOlympiad participantHacker mindsetProduct obsessionEvidence of unusually fast learningWhat We ValueOwnershipYou see a problem, you solve it.SpeedFast iteration beats endless planning.JudgmentGood decisions scale better than good code.AmbitionWe're building something that shouldn't be possible.CraftFast 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.
Optionally, you can add more information later (benefits, pre-screening questions, etc.)