You ship, not propose
No six-week spec cycles. You take a problem, decide how to solve it, and put it in production.
Careers
Build the thing that builds everything else.
We are a small team shipping fast. If you want your work in front of real users within days rather than quarters, read on.
You own your area
Every engineer owns a surface end to end — from the data model to what the user sees.
Small on purpose
We keep the team small so decisions stay fast and nobody spends their week in meetings.
Twelve languages, one product
What you build is used in a dozen languages across a dozen markets from day one.
Open roles
4 positions open right now.
You will work on the part of YeshBe that turns a sentence into a working application — prompt architecture, model orchestration, evaluation, and the retry logic that makes the difference between a demo and a product.
What you'll do
- Design and iterate on the prompt and tool-calling pipeline behind app generation.
- Build evaluation harnesses so we can tell whether a change actually improved output quality.
- Reduce latency and cost per generation without losing quality.
- Work with the product team on where the model should ask instead of guess.
What we're looking for
- 3+ years in software engineering, with at least one year shipping LLM features to production.
- Strong Python or TypeScript.
- Practical experience with function calling, structured output and RAG.
- You measure before you optimise, and you can prove a change worked.
- Comfortable with ambiguity — this area has no settled best practice yet.
How to apply
No forms and no portal. Send us an email with four things:
- Subject line:
AI Developer — [Your name] - Your CV. PDF, one or two pages. A LinkedIn link on its own is not enough.
- Links. GitHub, portfolio, or anything you built that we can actually open.
- One specific thing. Describe one LLM feature you shipped: what broke in production, and what you changed.
You will build the services behind every app our users generate — provisioning, databases, auth, billing and the APIs that hold it together. Reliability here is the product.
What you'll do
- Design and build .NET services that provision and run user applications.
- Own data modelling, migrations and query performance as usage grows.
- Build internal APIs consumed by the web, mobile and AI teams.
- Improve observability so we find problems before users report them.
What we're looking for
- 4+ years with C# and .NET in production.
- Solid SQL — you can read a query plan and fix what you find.
- Experience with cloud infrastructure, containers and CI/CD.
- You write tests where they earn their keep, not everywhere.
- Multi-tenant or platform experience is a strong plus.
How to apply
No forms and no portal. Send us an email with four things:
- Subject line:
C# Backend Developer — [Your name] - Your CV. PDF, one or two pages. A LinkedIn link on its own is not enough.
- Links. GitHub, portfolio, or anything you built that we can actually open.
- One specific thing. Tell us about a system you scaled: what the bottleneck was and how you found it.
You will build the editor our users spend their day in — the canvas, the chat, the preview, the moment where a prompt becomes something they can click. Interface performance and feel are the whole job.
What you'll do
- Build and refine the editor UI, from the prompt surface to live preview.
- Keep the interface fast with large, deeply nested app trees.
- Own accessibility and RTL across twelve languages.
- Work directly with design and turn rough directions into shipped screens.
What we're looking for
- 3+ years with React and TypeScript.
- Real command of CSS — layout, animation and where things get slow.
- You have profiled a React app and fixed what you found.
- Care about the small details: focus states, empty states, loading states.
- RTL or multilingual interface experience is a plus.
How to apply
No forms and no portal. Send us an email with four things:
- Subject line:
React Developer — [Your name] - Your CV. PDF, one or two pages. A LinkedIn link on its own is not enough.
- Links. GitHub, portfolio, or anything you built that we can actually open.
- One specific thing. Send a link to an interface you built and tell us which detail you are proudest of.
You will own the YeshBe Android app — building on the go, reviewing generated apps from a phone, and pushing to production from a train. It is a small surface, so quality is very visible.
What you'll do
- Own the Android app end to end, from architecture to Play Store release.
- Build a mobile editing experience that is genuinely usable, not a shrunken desktop.
- Handle offline states, push notifications and background sync.
- Keep startup time and battery use honest.
What we're looking for
- 3+ years shipping Android apps in Kotlin.
- Jetpack Compose in production.
- You have taken an app through the full Play Store release cycle.
- Comfortable being the only mobile engineer for a while.
How to apply
No forms and no portal. Send us an email with four things:
- Subject line:
Android Developer — [Your name] - Your CV. PDF, one or two pages. A LinkedIn link on its own is not enough.
- Links. GitHub, portfolio, or anything you built that we can actually open.
- One specific thing. Send a Play Store link to something you shipped, and what you would change today.
Nothing here fits, but you think we should talk?
Tell us what you do and what you would want to own here. We read everything.