Nojob / Job search intelligence
Useful signals inside the workflow people already use.
A browser product that brings listing, recruiter, and company signals into the moment of decision.
Delivered systemThe problem
Job seekers repeated research across listings, recruiter profiles, and company pages while trying to decide what deserved attention.
The key decision
Put evidence beside the listing or message instead of asking users to break their concentration and search elsewhere.
What we built
Make the work clearer and easier to hand off.
- A browser extension that recognises job listings and presents relevant signals in context
- Listing, recruiter, company, freshness, reposting, salary, and role-relevance analysis
- User accounts, authentication, application support, and a supporting product platform
- Gmail assistance and product infrastructure that keep job discovery and communication connected
Before the project
- Job seekers repeated research across listings, recruiter profiles, and company pages.
- Useful warning signals were separated from the moment of decision.
- Probability and uncertainty could be mistaken for fact without an explanation layer.
Job seekers did not need another place to search.
Nojob began with a practical observation. People often make a decision about an opportunity while they are looking at a listing, a recruiter profile, or an email. Asking them to copy a link into another product each time adds friction at exactly the moment they need information.
The product therefore lives close to the existing workflow. It helps users inspect signals while they are already reading a role, rather than asking them to break concentration and piece the story together elsewhere.
The product needed to explain signals without claiming to know intent.
A listing that has been open for a long time, frequently reposted, or linked to an inactive recruiter can be useful context. It is not proof of an employer's private intention. Nojob had to make that distinction visible in the product itself.
Quindart designed the analysis as evidence and risk signals, not declarations. The user can see why a warning appears, what information is available, and where the evidence is incomplete. The product supports a decision. It does not make the decision for them.
The browser extension had to remain useful without getting in the way.
Building inside third party websites creates a different kind of product challenge. The extension needs to react to changing page structures, retrieve information quickly, respect privacy and platform limits, and stay lightweight enough that the host page still feels normal.
The surrounding platform supports the extension with accounts, data processing, and continuity into communication tools such as Gmail. Together, the pieces help users move from discovery to a better informed next action without turning the job search into another administrative task.
The working process
- A user opens a job listing in a supported environment
- The extension detects the listing and retrieves the available signals
- The product presents a clear summary of what the evidence suggests
- The user decides whether to apply, investigate further, or skip the opportunity
What changed
- Less manual research around each opportunity
- More informed application decisions before a user invests time in an application
- Clearer continuity between job discovery, evaluation, and recruiter communication
- A product that explains uncertainty instead of presenting a probability as fact
Systems involved
LinkedIn · Gmail · Browser extension · User accounts
The lesson
The best interface is often the one that respects the environment where the decision is already being made.
Back to InsightsYour workflow