Careers

Early enough that what you build still shapes the company.

Joining now means your decisions about architecture, tooling, and practice become the defaults everyone works to afterwards.

Open roles: 5 positions
Working model: Distributed
Applications: Reviewed within a week

Open roles

5 positions open right now.

Every one of these is a role we are actively hiring for. We do not list positions we have not opened to look busier than we are.

Android Developer

Own Android delivery end to end — architecture, build, store submission, and the release cadence afterwards.

Full-time
2–6 years
Remote, India

Full Stack Developer

Own features from data model to interface, on TypeScript across the stack.

Full-time
2–6 years
Remote, India

AI Engineer

Ship applied AI features with evaluation built in — and the judgement to say when a model is the wrong answer.

Full-time
2–6 years
Remote, India

Freelance Engineers

Project-based work for engineers who want to keep their independence but want the delivery structure of a company behind them.

Contract
2–6 years
Remote

Business Development Intern

Learn how technical services are actually sold — research, outreach, and sitting in on real scoping conversations.

Internship
Fresher — no prior experience required
Remote, India

On compensation. We have not published salary bands. Rather than print a range we would have to caveat, we will tell you the band for the role in the first conversation, before you invest time in a process. Compensation is set on the role and your experience, not on what you were paid previously.

How we work

What you would actually be joining.

Review, always

Every change goes through pull request review. Nobody pushes to a protected branch, including whoever is most senior in the room.

Documented decisions

Architecture decisions get written down when they are made, so the reasoning survives the person who made it.

Real ownership

You own a problem end to end — design, build, test, ship, and operate — rather than a ticket handed down a chain.

No hero culture

Continuity is designed in. If a project depends on one person being available, that is a defect we fix, not a strength we celebrate.

Honest estimates

When something will take longer, we say so the day we know. Nobody is asked to absorb an unrealistic date quietly.

Tools that fit

We pick technology on problem fit and team depth, not on what is trending. You will not maintain a stack chosen for a conference talk.

Hiring process

Four steps, and a decision within a week.

Application

Send your CV and anything you have built. For engineering roles a repository or shipped product tells us more than a covering letter.

Intro conversation

Thirty minutes on what you want to work on and what we actually do. Ask us hard questions here — we would rather you did.

Technical conversation

A discussion of real problems, not a whiteboard puzzle. For engineering roles we will look at code you have written, or work through a small realistic problem together.

Decision

A clear yes or no with the reasoning, within a week. If it is a no, we will tell you why.

Applications go to career@laxorasoftware.com. Put the role in the subject line.

Not seeing your role?

If you are strong and interested anyway, write to us. A good engineer arriving at the right moment has started more than one role that did not exist the week before.

Write to us See our stack

First response within one business day
NDA in place before any disclosure
Scoped proposal, not a generic quote