Careers

We are growing, carefully.

We hire slowly and keep the team small. That means fewer roles than a larger agency, and considerably more responsibility in each one.

  • Based in

    Madurai, Tamil Nadu

  • You would write

    React, React Native, Node, Laravel

  • Every change

    Reviewed by a senior engineer

  • How to apply

    One email, no tracking system

Open roles

Nothing listed today, which is not the same as nothing coming.

We would rather show an empty list than advertise a job we have not decided to fill. We are still growing, so if you write React, React Native, Node or Laravel, send us your work and we will come back to you when a role opens.

What we will open first

  • React and React Native engineers, mid to senior
  • A backend engineer across Node and Laravel
  • Anyone who has shipped a native module and enjoyed it

Written down so you can hold us to the shape of the team, not as a vacancy. None of these are open today.

Working here

What the job is actually like.

Small teams are sold to candidates as freedom and experienced as exposure. Both are true here, so this is written as plainly as we can manage rather than as a benefits list.
  • You work on the whole problem

    Small team, no ticket conveyor belt. You talk to the client, shape the approach, and ship the thing you designed.

  • Senior review on everything

    Your code is read by someone with production experience, and you read theirs. That is how both of you get better.

  • Modern stack, no legacy tax

    React, React Native, TypeScript, Node and Laravel. New projects on current tooling, with no legacy to work around.

  • You will go below JavaScript

    Swift and Kotlin modules are ordinary work here, not one person's specialism. If you have never written one, you will.

How to apply

Send us your work.

One email, read by the people you would be working with. No form, no applicant tracking system, no automated rejection three weeks later.

We are based in Madurai, Tamil Nadu. Ask about remote arrangements when you write — we would rather discuss it than rule it out on a web page.

  • Something you have shipped

    A GitHub profile, a package, an app in a store, or a repository we can read. Work in the open beats a description of work.

  • A paragraph on what was yours

    Which part you built, what was hard about it, and what you would do differently. Two sentences is enough.

  • A CV, if you have one

    Optional. We would rather read your code than your formatting. Nobody has been turned down here for not having a CV ready.