Code that lasts
We optimise for the version of the codebase that exists three years from now, not three weeks. The boring decisions get the same care as the exciting ones.
Leafy CodeCareers2026No openingsBuild software people still rely on in ten years.
Twelve years in. Four continents. A podcast, a robotics lab, and one rule that hasn't changed: ship code that's still running long after we've moved on. We hire engineers who think the same way.
- Industry
- Software · Robotics · Applied AI
- Founded
- 2014
- Team
- 20–40 people · Kottawa + On-site
- Phone
- +94766707355
- Address
- 269/1 High Level Rd, Pannipitiya
We started Leafy Code in 2014 because we were tired of software that broke six months after launch. We wanted to build the kind of code that just works — year after year — and lets the team building it sleep on weekends.
That's still the bet. We work with startups and enterprises across four continents on the boring-and-important things — web platforms, mobile apps, ERPs. We also run The Lab, our R&D division building drones, computer-vision rigs, and applied LLM workflows; and SLDevTalks, the podcast that grew into the largest developer community in Sri Lanka.
We hire two kinds of people: engineers who can ship something end-to-end on their own, and engineers who can't help but make the team around them better. Often the same person.
§ 02 · Values
How we work.
The lens we hire against — what we believe, how we decide, what stays consistent when everything else is moving.
Ship the whole thing
Pull requests aren't handoffs. The author owns deploy, follow-up, and the email when something breaks at 2am. If you can ship it, you can support it.
Lift the team you're on
The best engineers we have make every other engineer better. Review like the code is yours. Document like you'll forget. Mentor like you'd want to be mentored.
Build, then write about it
Most of what we learn gets handed back — talks, podcasts, open-source patches. If you do good work and tell no one, half the work is wasted.
Real-world first
Demos are easy. Tea estates are not. Whatever you're building, assume the network drops, the user is tired, and the last person to touch this code six months from now is you.
§ 03 · Benefits
What you get.
The handful of things we extend to every full-time hire, without asking.
- A new stack every quarterWeb, mobile, embedded, ML — in a single year, not a decade
- The Lab is openDrones, computer vision, applied LLMs — it's part of the job, not a perk
- Real mentorshipSixteen years of engineering judgement, on tap
- Code review you learn fromNot the kind you flinch from
- Calm by defaultSustainable pace. No 11pm Slack, no weekend deploys, no "crunch"
- Open-source with your name on itPatches go upstream under your handle. The work travels with you
- Work that actually shipsProduction with real users, not a slide deck
- SLDevTalks stageA podcast, a meetup, an audience — if you've got something to say
§ 04 · Roster
Open roles.
No openings live right now.
Loading roles…