Careers
Algorix works on infrastructure other products depend on. The work rewards people who care what happens at the tenth-billionth row, not the tenth.
Philosophy
01
These are not values in the poster sense. They are the tie-breakers used when two reasonable engineering options are on the table.
A number without a stated basis does not ship. Every metric on this site names where it came from, and the ones we do not have are omitted rather than estimated.
History should survive a change of vendor, including a change away from us. Architectures that make a client dependent on the supplier to read their own record are a commercial tactic, not an engineering one.
Early work is labelled as early, and unfinished work is not published at all. A portfolio that presents everything as finished tells an assessor nothing, and costs credibility the moment one item turns out to be earlier than it looked.
Off-the-shelf software is the right answer more often than vendors admit. Custom work is justified by regulation, residency, or bilingual requirements — not by preference.
Not yet published
Algorix is not advertising positions right now, and no vacancy is listed here that does not exist. Engineers working in machine intelligence, telematics, data systems or platform engineering are still welcome to write to us.
Infrastructure more often than interface: ingestion layers, normalisation above mixed hardware, time-series stores that have to stay fast as they grow, and the operator-facing platform on top. The interesting problems here are the ones that only appear at the tenth-billionth row, or when the third hardware vendor arrives, or when a system has to keep working while it is being changed.
Four principles do most of the tie-breaking: measure before claiming, the data belongs to the operator, say when something is early, and build only what cannot be bought. They are not posters. They are what settles an argument when two reasonable engineering options are on the table, and they are why this site omits figures rather than estimating them.
Machine intelligence applied to a specific operational decision; telematics and device integration at the hardware level; enterprise automation and the exception paths that make it survivable; time-series and geospatial data systems; and bilingual product engineering where Arabic is an operative language rather than a translation pass at the end.
No roles are advertised right now, and none are listed here that do not exist. If you work in these areas, a short note about a system you have built and what was hard about it is more useful than a CV. We read them.