Junior Software Engineer

About Runable

Runable is one agent that runs small businesses end to end. It answers on Slack, iMessage, Telegram, Discord, Teams, web, mobile, and desktop — and it does real work: builds and deploys websites and apps, writes documents and slides, browses the internet, and executes long-running jobs in its own sandboxes.

Everyone at Runable wants to be the best in the world at what they do. That’s the bar — not pedigree, not years, but whether being great at this craft matters more to you than being comfortable.

What you’ll do

You’ll learn fast and build real things. There’s no onboarding ramp designed for comfort — you’ll be thrown at hard problems, expected to go deep, and judged on what you figure out and ship.

The work spans:

• Agent infrastructure. Orchestration, tool use, durable execution, the plumbing that makes an AI agent reliable enough to run someone’s business.
• Execution sandboxes and hosting. Where the agent builds, browses, and deploys. Making a unit of agent work cost cents instead of dollars is a real engineering problem here.
• The product surface. Web, mobile, desktop, and every messaging channel — TypeScript monorepo on Postgres, Redis, and DBOS, with Cloudflare and GCP underneath.

What you bring

You don’t need years. You need depth. Specifically:

• You’ve gone unusually deep on something. Rust, Zig, or another language most people haven’t touched. Or networking internals, AI agent architecture, LLMs from first principles, compilers, OS internals — something that proves you don’t stop when it gets hard.
• You build to understand. Side projects, open source contributions, or something you built because you had to know how it worked — not because a course told you to.
• 0–1.5 years of experience — but raw ability over tenure, always.
• High agency. You notice what’s broken, fix it, and say so — without being asked.
• You want to work with AI agents at the frontier: as the product, as the user, and as a collaborator in your editor.

What’s different about working here

• Builders all the way up. Nobody manages as their job. The people setting direction are also shipping.
• Agents write a lot of our code. You’ll get very good at directing AI — and at knowing when not to.
• Small diffs win. The change that deletes code beats the one that adds it. Speculative abstraction gets rejected in review.
• Product depth is an engineering value. You’re expected to understand why a store owner churns, not just the service you own.

Hiring process

Two steps, no gauntlet:

1. A 15-minute introduction call with Saksham, co-founder.
2. A work-day trial in our office — you work on a real problem with the team, and both sides find out what it’s actually like to work together.

Location: In person, Bangalore.