Jobsly has three visual surfaces: career pages, contracts, and scheduling pages. That’s it. Everything else — candidate management, scoring, communication, pipeline tracking — happens through conversation with Rob.
This isn’t minimalism for its own sake. It’s a design principle rooted in how hiring actually works.
Most hiring tools have dozens of screens. Pipeline views, candidate profiles, settings pages, analytics dashboards, email templates, scheduling interfaces. Each screen is another thing to learn, another place for errors, and another surface to maintain. We asked ourselves: which of these screens actually need to exist?
The candidate experience test
We use a simple test to decide whether something should be a visual surface: does the candidate see it? If yes, it needs to be polished, branded, and pixel-perfect. If no, it doesn’t need to be visual at all.
Candidates see three things from Jobsly: the career page where they discover the role, the scheduling page where they book their interview, and the contract they sign when they’re hired. Each of these moments is a brand touchpoint. Each one shapes the candidate’s perception of the company.
Everything else — the scoring, the pipeline tracking, the communication between hiring manager and recruiter — is invisible to the candidate. It’s internal tooling. And internal tooling has different requirements than candidate-facing surfaces.
Why only three surfaces
Visual surfaces are what the candidate sees. They need to be polished, branded, and professional because they represent your company. Career pages attract candidates. Contracts close them. Scheduling pages make the logistics frictionless.
Everything else is internal tooling. And internal tooling doesn’t need to be visual. It needs to be fast, accurate, and invisible. That’s what conversational AI is good at.
There’s an operational benefit too. Three surfaces means three things to design, three things to QA, three things to keep updated. When a company rebrands, they update three pages in Jobsly, not thirty. When we ship a new feature, it usually doesn’t touch any visual surface at all — it’s a new capability in the conversation layer.
The conversational advantage
When hiring managers interact with Rob through conversation instead of through a dashboard, the interaction is faster and more natural. You don’t need to learn a UI. You don’t need to find the right button. You just say what you need.
This also means we can ship new features without redesigning screens. A new capability is just a new thing Rob can do. No new tabs, no new menus, no training required.
Consider the alternative: adding a new scheduling feature to a traditional tool means designing a new UI, building the frontend, writing help documentation, and training users. In Jobsly, adding a new scheduling capability means teaching Rob a new action. The user discovers it naturally through conversation. “Hey Rob, can you schedule this for next Tuesday?” “Yes, done.”
This architecture also makes the product more resilient to changing requirements. When a customer asks for a workflow that we didn’t anticipate, we don’t need to redesign a screen. We extend the conversation layer. The surface area stays the same even as the capabilities grow.
What we chose not to build
The list of things we decided not to make visual is long: analytics dashboards, email template editors, interview rubric builders, org charts, approval workflows, reporting pages. All of these exist as capabilities in Jobsly — but they live in the conversation layer, not in a visual interface.
“Show me the interview completion rate for the last 30 days” is faster to type than to navigate to an analytics page, find the right chart, and set the date range. “Create an interview rubric for a senior designer” is faster to say than to fill out a form. The conversation interface is the UI.
We’re not anti-visual. We love good design. But we believe that the right interface for internal hiring workflows is conversational, not graphical. The three visual surfaces exist because they need to be beautiful. Everything else exists because it needs to be functional.
The counterargument
The obvious pushback: some people prefer visual interfaces. They want to see the pipeline. They want to drag and drop. They want charts and graphs on a screen.
We’ve found that this preference is usually about familiarity, not effectiveness. People are used to dashboards because every tool has one. But when we give them a week with the conversational interface, most don’t go back. The dashboard was never the goal — it was a workaround for tools that couldn’t just answer your question directly.
For the subset of users who genuinely need a visual overview, we offer a simple list view. It’s read-only, it’s clean, and it’s optional. It exists because some people think visually, and we respect that. But it’s not the primary interface. Rob is.