Made by recruiters, for recruiters.
Signals is engineered in Hong Kong and Venezuela and shaped by twelve years on recruitment desks. Built for agencies across Asia Pacific, Europe and the Americas.
The two of us
Julio Orr
Twelve years running recruitment desks, at Adecco and Allegis, and then his own agency. Julio makes sure the product does what its name says: cuts the noise, and leaves the signal.
Roger Lam
An engineer with a track record building technology for complex, people-driven businesses. Roger makes sure Signals works the way recruiters actually think.
Why we started
Recruitment software was built when the constraint was storage. You needed somewhere to put candidates, so you got a database, and every year since somebody added a field to it.
The constraint now is conversations, and everything after a conversation is admin nobody has time for. So the record goes stale and the system becomes a place you put things rather than a place you get answers.
That needs a different system, not another field.
Why we are called Signals
A recruiter's day is mostly noise. Notifications, statuses, dashboards, a hundred things a system knows and shows you anyway. Almost none of it changes what you do next.
A signal is the small part that does. A client who just raised. A candidate who has gone quiet. A role that has stopped moving.
That is what we build, and how we decide what to build.
One principle. No exceptions.
If a feature does not reduce admin, surface an opportunity, or help close a deal, it does not ship. Not as an option, not behind a setting, not later.
Most recruitment software grew by addition. Every request became a field, every field became a screen. We would rather say no.
More placements. Less everything else.