Careers.
Engineering at Mobile Byte Sensei spans mobile, games, web, desktop and applied AI, on client engagements and on products we operate ourselves.
Open positionsNone at present
careers@mobilebytesensei.comRoles are published on this page when they open. To be considered for a future role, email one thing you built and what you would change about it now.
What engineers work on.
Client applications and products of every kind, built to requirement, and a line of our own products that are public and can be inspected. Three of them:
Developer infrastructure: one Kotlin Multiplatform billing API, with public documentation and a status page.
Web, Android, iOS and Desktop
Applied AI on the handset: speech recognition and a local language model running entirely on the phone.
Android and AI
A consumer web product: film picks chosen by mood rather than by genre.
Web
How engineering work is organised.
The conditions that apply to every engineer, whichever product or engagement they work on.
- A named team, not a resource pool
- You remain on a product long enough to see the consequences of your decisions. There is no rotation to balance utilisation.
- Scoping is engineering work
- Engineers take part in client scoping sessions, so the people who build a feature have a say in how it is defined.
- Estimates made by those doing the work
- Estimates come from the engineers who will do the work, and scope changes are priced for the client rather than absorbed into your evenings.
- Remote-first by design
- Scheduled around your working day, with four hours of overlap. The remainder of the day is yours to arrange.
- Open source on company time
- Open-source contributions are made on company time.
- An annual learning budget
- A conference, a course or hardware, agreed once a year. An unspent budget is treated as a planning failure, not a saving.
When a role opens, this is the process.
Published in advance, so it is a commitment rather than a description.
Step 1
Submission
A CV, a repository, a project or a paragraph. Everything submitted is read, and you receive a reply within two working days either way.
Step 245 min
Conversation
A conversation with the person who would lead your work, about what you have built. It is not a screening call.
Step 34 hours
Paid exercise
A real problem from a real project, paid at your day rate. You keep the code, and it is not used by the company.
Step 42 hours
Team meeting
Time with the people you would work alongside, including someone from outside your discipline.
Step 5
Decision
An offer or a reason, within one week. A declined application receives the actual reason in writing.
- No CV is required
- A CV mainly measures how well a CV is formatted. The two written questions indicate more in five minutes than a document does in an hour.
- The exercise is paid
- Four hours at your day rate, on a real problem. You keep the code and it is not used. Unpaid take-home work transfers value from the candidate to the company.
- Every applicant receives a real answer
- Including a declined application: the actual reason, in writing, within one week, rather than a form response.
- Applications are not retained indefinitely
- Unsuccessful applications are deleted after twelve months. You may request earlier deletion at any time, without giving a reason.