If that sounds like a warning as much as an invitation, you have read it correctly.
Most companies build a product. We are building the software a company runs on, which is a different kind of responsibility: if a number is wrong, somebody files an incorrect tax return or pays an employee the wrong amount. That raises the standard for everything, and it is the most interesting constraint in software.
In exchange you get scope that would take a decade to accumulate somewhere large. There is no team that owns the thing you need to change, no quarter-long process to get a decision, and nobody between you and the customer whose problem you are solving.
Small enough that we will not pretend otherwise on a careers page. That means unusual ownership of real work, and it also means none of the structure that a larger company provides. Both parts are true and you should weigh them.
This is not one microservice. It is a suite covering finance, stock, people, support, commerce and the agent layer running across all of it. You will touch parts of business software most engineers never see.
There is no product manager relaying a customer's problem through two documents. You hear the problem, you understand the business behind it, and you build the fix.
The reason a small team can build this much is that the work is done properly the first time. We are slow about the things that are expensive to redo and fast about everything else.
No live vacancies are listed below. These are the profiles that fit the work.
Building applications across the suite. Deep work on business logic that has to be correct, because it decides what a company owes and what it owns.
The layer that lets a language model work safely inside a company's live records: permission inheritance, retrieval without retention, approval gates and evaluation.
Provisioning, isolation, backups, updates, monitoring and cost. The part that makes a Site appear in minutes and keeps every one of them running.
Sitting with a company, understanding how they actually work, configuring the suite around it and running the migration. Half consulting, half engineering.
A note that most companies would not write, for a reason that is obvious once you know how this platform came to exist.
One email to khadeem.smart@tynk-tech.nl. Tell us what you have built, what you want to work on, and what you think is wrong with business software. No cover letter theatre and no portal that asks you to retype your CV into fourteen fields.
Everyone gets an answer, including a no. Being ignored after applying is rude, and it is not difficult to avoid.
There is no published list, and we are not going to invent one to look bigger. When there is a role it will appear here. Meanwhile, unsolicited applications from people who are clearly right are read carefully and answered personally.
Netherlands-based, with real flexibility about where you sit day to day. Some of the implementation work happens at customer sites, because you cannot understand a warehouse from a video call.
A conversation, then something practical drawn from real work rather than a puzzle, then a discussion of it with the person who built the platform. Short, and we tell you where you stand at every step.
Fairly for the stage the company is at, discussed openly in the first conversation rather than extracted from you at the end. We will not waste your time if the number cannot work.
Eventually, certainly. Today the useful non-engineering profile is someone who understands how companies actually run, can sit with a finance team and translate their reality into a configuration. If that is you, write.
