Careers
Careers at TJS Platforms
We are a small team building software for problems that are usually solved with spreadsheets, phone calls, and paper. If that kind of work interests you, we would like to hear from you.
How we work
We keep teams small and give people real ownership of the products they work on. Most of what we build starts with sitting alongside the people who will use it, understanding the process as it actually runs today, and then removing the parts that waste their time.
We ship in small steps and keep them in front of real users. We would rather release a narrow feature that works properly than a broad one nobody trusts. That applies to engineering, design, and operations equally.
What we look for
- People who ask what a feature is for before asking how to build it
- Comfort with ambiguity — many of our problems have no obvious precedent
- Care about security and privacy as a default, not a final checklist
- Clear written communication, because decisions outlive conversations
- Genuine interest in the industries our platforms serve
- A bias toward finishing things rather than starting them
What happens next
- You send thisTell us what you build and the kind of problems you want to work on.
- We read itEvery introduction is read by someone on the team, not filtered automatically.
- We replyIf there is a fit now, we will get in touch to arrange a conversation.
- We keep it on fileIf there is no role open yet, we come back to you when one opens.
No public openings right nowWe hire when a specific need appears rather than keeping a standing list, so a direct introduction is the fastest route in.
Careers at TJS Platforms: how we hire
Careers at TJS Platforms start with a conversation rather than a form-filling exercise. We hire when a specific need appears, so we would rather keep a real introduction on file than run a permanent pipeline of applications nobody reads.
When a role does open, the process is short and deliberately practical: a conversation about the kind of work you want to do, a look at something you have actually built or run, and a discussion with the people you would work alongside. We do not use puzzle interviews, and we do not ask for unpaid project work.
What working here is like
- Small teams with real ownership of a product area, not a ticket queue
- Direct contact with the people who use what you build
- Short release cycles, so your work reaches real users quickly
- Written decisions, because they outlive the conversation that produced them