Own the outcome
Understand the business problem, question weak assumptions, and stay responsible for the thing after it reaches production.
- Home
- Careers
Careers / Teslian Tech
Do work that survives the demo.
We build software that businesses run on — billing that has to reconcile, stock that has to be right, apps used all day by people with no patience for a spinner. If that sounds like a constraint rather than a chore, we should talk.
How we work / 01
Four expectations, held consistently.
These apply to everyone here, on the first project and the fiftieth.
Craft with evidence
Research, prototypes, tests and observability over presentation theatre. If we cannot show it working, it is not done.
Communicate clearly
Make decisions, risks and progress understandable to technical and non-technical people in the same sentence.
Leave it maintainable
The next engineer is the real user of your code. Write for the person who arrives in eighteen months with no context.
Disciplines / 02
Where we look for people.
These are the areas our work sits in. Applications are reviewed against active project needs rather than a permanently open list of roles.
Product design
Interface and interaction design for operational software — the kind used all day, not glanced at once.
Mobile engineering
Flutter and native work on products with offline states, device integrations and real field usage.
Backend engineering
Laravel and API work on systems where billing, stock and permissions have to be exactly right.
Frontend engineering
Performance-minded interface work in React, Vue and Blade with a real eye for detail.
Data and automation
Pipelines, integrations and model-assisted workflows that keep humans in the loop.
DevOps
Environments, deployment, monitoring and the recovery path nobody wants to need.
We do not publish placeholder vacancies. When a specific role opens, it will be listed here with its actual scope.
Hiring process / 03
Four steps, no theatre.
We try to make this respectful of your time, because a bad hiring process is its own signal about a company.
Apply
Send work we can actually look at — a repository, a shipped product, a case study, a piece of writing. A CV alone tells us very little.
Conversation
A call about what you have built, what went wrong in it, and what you would do differently. We are more interested in the second two.
Practical exercise
A scoped, realistic problem — no whiteboard puzzles, no unpaid production work. We discuss your solution together.
Decision
A clear yes or no with reasons, in reasonable time. If it is a no, we say why.
Open applications
Send us something you built.
Email a link to a repository, a shipped product or a piece of work you are proud of, with a short note about what you want to build next. Tell us what was hard about it and what you would change.
We read every application from a person. If there is no current fit we will say so rather than leaving you waiting.
Apply by email