Product + optimisation
Are we making better decisions?
Optimisation models, decision quality, network intelligence and product reasoning.
Do work that
has consequences.
Ordinal is building Logistics Decision Intelligence; technology for understanding the network consequences of operational decisions before those decisions are made.
The work sits at the intersection of optimisation, logistics operations, data systems and enterprise technology. The problems are complex, the constraints are real, and the consequences are measurable.
We are building the company with the same discipline: clear ownership, meaningful authority, direct access to the problem and very little unnecessary hierarchy.
Clear ownership.
Meaningful authority.
We want people to understand the problem, have the authority to act on it, and take responsibility for the outcome.
Own outcomes
You should understand what the work is supposed to change, not simply complete a queue of instructions.
Authority follows context
The people who understand a problem should have meaningful influence over the decision.
Challenge is expected
A weak idea does not become stronger because it came from the founder or someone senior.
Stay close to reality
Engineers should understand operators. Commercial people should understand the product. Decisions should survive contact with real operations.
The problem comes before the process.
Context before instructions
People should know why something matters, not simply what they have been asked to do.
Written decisions
Important reasoning should survive the conversation in which it happened.
Evidence over seniority
The strongest evidence should be allowed to change the direction, regardless of where it came from.
Few unnecessary meetings
Meet when interaction materially improves the outcome. Write when writing is enough.
Direct access to the operator
The further we get from operational reality, the worse our decisions become.
Complexity must earn its place
More software, more process and more structure are not automatically signs of progress.
Good judgement requires context. Good ownership requires authority.
Structured around responsibility, not status.
Ordinal is organised around domains of ownership. Each domain has a fundamental question it is responsible for answering.
Platform + data
Is the system reliable, secure and usable?
APIs, data systems, infrastructure, integrations, security and reliability.
Logistics solutions
Does Ordinal work in the real operation?
Operator requirements, network analysis, implementation, workflows and operational outcomes.
Commercial + market
Does the market value what we're building?
Operator relationships, pilots, enterprise sales, partnerships, procurement and commercial strategy.
Company operations
Can Ordinal operate properly as it grows?
Finance, legal, people operations, administration and internal systems.
These are areas of responsibility, not walls between people.
Product decisions need operational understanding. Commercial conversations need technical credibility. Engineering needs exposure to what operators actually experience.The interfaces between disciplines are part of the work.
Authority should move towards context.
Ordinal should not require every meaningful decision to travel upwards through layers of approval.
ContextOwnerDecisionOutcomeLearning
- Every meaningful decision should have an owner.
- Anyone can contribute.
- Anyone can challenge.
- The decision owner decides.
- Disagreement should improve decisions, not prevent them.
- Decisions can change when the evidence changes.
- Escalation should not automatically mean finding the most senior person.
Roles clarify responsibility. Titles do not determine whose thinking matters.
Autonomy requires accountability.
Accountability requires trust.
Ordinal asks of you
- Take ownership.
- Exercise judgement.
- Surface problems early.
- Tell us when we're wrong.
- Care about the outcome beyond your immediate task.
- Communicate clearly.
- Change your mind when the evidence changes.
Ordinal should give you
- Context.
- Clear authority.
- Candid feedback.
- Freedom to disagree.
- Respect for your time.
- The tools required to do the work properly.
- Credit for your work.
High ownership should never be an excuse for unclear expectations, poor communication or unnecessary pressure.
Management is not the only form of progression.
Ordinal should allow people to grow through deeper expertise as well as organisational leadership.
Craft
Grow through increasing expertise, judgement, problem complexity and influence within an important discipline.
Examples may include optimisation, engineering, data, logistics operations, implementation or enterprise commercialisation.
Organisational leadership
Grow through responsibility for people, coordination, organisational capability and increasingly broad decisions.
Neither path should automatically rank above the other.
Someone with exceptional technical or operational judgement should not need to become a manager simply to keep progressing.
You may like working here if you:
- Form independent opinions
- Enjoy difficult problems
- Can operate with ambiguity
- Communicate clearly
- Take responsibility
- Are comfortable changing your mind
- Enjoy working across disciplines
- Want meaningful autonomy
- Are comfortable talking to customers and operators
- Care whether the work produces something real
Ordinal may not be the right environment if you strongly prefer:
- Detailed instructions for every task
- Rigid departmental boundaries
- Decisions based primarily on seniority
- Predictable problems with established solutions
- Management titles as the main form of career progression
- Being insulated from customers
- Waiting for approval before exercising judgement
There is nothing inherently wrong with those preferences. They simply describe a different kind of organisation.
How we work, decide, disagree and build together.
- 01Authority follows context, not title.
- 02Every important outcome has an owner.
- 03We own outcomes, not task lists.
- 04Everyone has the right to challenge.
- 05Disagreement cannot become paralysis.
- 06Evidence outranks seniority.
- 07Customer reality outranks internal opinion.
- 08Information is open by default.
- 09We write important things down.
- 10Decisions are allowed to change.
- 11Problems travel towards expertise, not upwards.
- 12Leadership is a responsibility, not a reward.
- 13We prefer focused teams with meaningful responsibility.
- 14We organise around missions when the problem requires it.
- 15We distinguish mistakes from negligence.
- 16Intellectual honesty matters.
- 17Security and privacy are part of the product.
- 18Complexity must earn its place.
- 19We measure ourselves by value created.
- 20We are building for the real world.
Did we create measurable value for the operator?
Find your place in Ordinal.
We hire deliberately, around work that carries real responsibility.
Current opportunities will appear here as they become available.
If your work sits at the intersection of logistics, optimisation, engineering, data or enterprise technology, we are interested in hearing from exceptional people.
Introduce yourself →