Principles
Software should just work.
And it should never make you angry. Six principles that decide how we design, build and run every Khoob platform.
Why we exist
You have seen it happen
The exam that will not load. The candidate who cannot log in at 8:59. The teacher who spends the evening fighting the platform instead of preparing the next lesson. The support email that starts with “I tried everything”.
We think this is unacceptable. Good software is invisible: you open it, it works, and you get on with your day.
Making software feel that simple is hard. That work is our job, not yours. Teachers should teach; the platform should do the rest.
Simple outside, serious inside
One button. Everything behind it.
A candidate sees one button. Behind it, every integrity control starts in the right order, in seconds.
What the candidate sees
- 01Identity check: document and face match
- 02Device and connection test
- 03Lockdown browser engaged
- 04AI proctoring starts: webcam and audio
- 05A unique, randomised question set is generated
- 06Timer, autosave and recovery if the connection drops
- 07AI-generated text detection on written answers
- 08Full audit trail for every action
What we believe
-
01
It just works.
If a teacher needs a manual, or a candidate needs a tutorial, we have failed. We design for the person with the least time and the least patience.
In practice
Every screen we ship passes one test: can a first-time user finish the task without help?
What we will not do
Add features that need training to use. More features are not more value.
-
02
Complexity is our job.
Simple on the surface, serious underneath. We absorb the hard parts: security, scale, integrity, recovery. You get one clear button.
In practice
When a requirement makes the interface harder, we solve it behind the interface first.
What we will not do
Push technical decisions onto teachers, candidates or administrators.
-
03
Frustration is a bug.
If our software makes someone angry, we treat it like a crash. It gets a fix, not an explanation.
In practice
Every support request is logged as a design question. The fix goes into the product, not into the FAQ.
What we will not do
Answer a usability problem with “it works as designed”.
-
04
A result is only worth what it can prove.
An exam that can be cheated is not an exam. Integrity comes first, even when it costs us an easier sale.
In practice
Every assessment we build starts from one question: how would a candidate try to cheat here?
What we will not do
Switch off an integrity control to make a demo look smoother.
-
05
No surprises.
Fixed scope, fixed price and a launch date, in writing. If something is at risk, you hear it from us first, the day we know.
In practice
Bad news travels faster than good news at Khoob. Every risk comes with a plan.
What we will not do
Hide a delay until the last week, or sell a feature we cannot deliver.
-
06
Your name, not ours.
We work white-label only. When a platform works well, the credit should go to the institution that runs it, and to its teachers.
In practice
Your brand on every screen, certificate and email. Khoob stays behind the scenes.
What we will not do
Put our logo in front of your students, or use your name in our marketing without written permission.
Work with us
Boring exam days, on purpose.
The best exam day is the one nobody talks about afterwards.