An engineering company that writes down what it does not know.
Ferrite builds infrastructure for data in motion. We work with engineering organisations that have outgrown batch pipelines and want a system whose behaviour under failure is documented rather than discovered.
Four commitments we can be held to
- 01
Precision over persuasion
If we have not measured it in your environment, we do not put a number on it. Claims that cannot be reproduced are worse than no claim.
- 02
Engineers in the first conversation
Technical questions are answered by people who work on the system, not relayed through an account layer.
- 03
Scope discipline
We would rather do the log, the runtime and the read surfaces properly than add adjacent products for the sake of the diagram.
- 04
Documented failure behaviour
How the system behaves when things go wrong is part of the product, and it is written down before you ask.
We are not listing vacancies on this page.
When roles are open, they are posted here with the actual scope of the work. Until then, we would rather leave this section honest than fill it with placeholder openings.
If you work on distributed systems, storage engines, stream processing or the operability of either, you are welcome to write to us regardless of whether something is advertised. Tell us what you have built and what you found hard about it.
Write to usWhere to direct different questions
- Use the contact form and describe the data flow you want to run.
- Send your questionnaire through the contact form; it reaches the engineering team.
- Mark the message as a press enquiry. We do not publish statements we cannot substantiate.
- Describe the systems you have built. There is no application form.
Start with the technical question.
Whatever the reason for getting in touch, being specific gets a faster and more useful answer.