MEDIJobs
MEDIJobs
Fixing the critical flow that was costing revenue and overloading support
Fixing the critical flow that was costing revenue and overloading support
Fixing the critical flow that was costing revenue and overloading support
How we redesigned the one flow that mattered most in a healthcare hiring marketplace, replacing manual support team coordination with a scheduling experience users could complete on their own.
How we redesigned the one flow that mattered most in a healthcare hiring marketplace, replacing manual support team coordination with a scheduling experience users could complete on their own.
How we redesigned the one flow that mattered most in a healthcare hiring marketplace, replacing manual support team coordination with a scheduling experience users could complete on their own.
Industry
Industry
HealthTech
SaaS
Growth stage
Growth stage
Pre-Seed → Seed
Pre-Seed → Seed
Services
Services
UX Audit
Strategy & Discovery
User Testing
Product Design
MEDIjobs is a career marketplace for healthcare professionals, connecting candidates with medical practices in Romania and the US. The platform worked. Most of it. But there was one flow that broke down every time it mattered: scheduling the interview between candidate and clinic. Two weeks of focused work to redesign it.
MEDIjobs is a career marketplace for healthcare professionals, connecting candidates with medical practices in Romania and the US. The platform worked. Most of it. But there was one flow that broke down every time it mattered: scheduling the interview between candidate and clinic. Two weeks of focused work to redesign it.
MEDIjobs is a career marketplace for healthcare professionals, connecting candidates with medical practices in Romania and the US. The platform worked. Most of it. But there was one flow that broke down every time it mattered: scheduling the interview between candidate and clinic. Two weeks of focused work to redesign it.
2 weeks
2 weeks
2 weeks
Discovery to validated solution
Discovery to validated solution
Discovery to validated solution
5 customers
5 customers
5 customers
Tested the new flow
Tested the new flow
Tested the new flow
1 flow
1 flow
1 flow
Scheduling, end-to-end
Scheduling, end-to-end
Scheduling, end-to-end
the situation
Most of the platform worked. The
part that mattered didn't.
Most of the platform worked. The part that mattered didn't.
MEDIJobs gives medical practices fast access to qualified healthcare candidates. The team had built the search, the matching, the candidate profiles, and the messaging. The platform was used by both sides of the marketplace. People showed up.
MEDIJobs gives medical practices fast access to qualified healthcare candidates. The team had built the search, the matching, the candidate profiles, and the messaging. The platform was used by both sides of the marketplace. People showed up.
What kept breaking was the moment after the match. When a clinic and a candidate had to actually agree on a time to talk. Both sides reached out to the support team to coordinate. Phone calls and emails replaced what should have been a few clicks. For a recruiting platform where the entire promise is "we make hiring faster," that was the wrong place to lose people.
What kept breaking was the moment after the match. When a clinic and a candidate had to actually agree on a time to talk. Both sides reached out to the support team to coordinate. Phone calls and emails replaced what should have been a few clicks. For a recruiting platform where the entire promise is "we make hiring faster," that was the wrong place to lose people.
The pressure showed up in two places. The support team was spending hours every week on scheduling logistics that had nothing to do with the value of the platform. And every interview that didn't get scheduled was an interview that didn't generate revenue.
The pressure showed up in two places. The support team was spending hours every week on scheduling logistics that had nothing to do with the value of the platform. And every interview that didn't get scheduled was an interview that didn't generate revenue.
A flow that was supposed to take three clicks
Scheduling between two parties is a coordination problem at the best of times. The existing flow didn't sync calendars, didn't handle availability windows, and didn't make rescheduling possible.
Support absorbing the friction
Every booking that didn't work meant a phone call to support. The team was triaging logistics that the platform was supposed to handle on its own.
Revenue events stuck behind the wrong UI
Interviews are where the platform's value gets realised. If candidates and clinics couldn't book one, the rest of the funnel didn't matter.
Two user types. Different habits. Same flow.
Some clinics worked with digital calendars. Others didn't. The team had assumed everyone did. Discovery surfaced that assumption fast, and it had been baked into the original design.
the situation
the situation
Powerful features that nobody could find
Powerful features that nobody could find
Powerful features that nobody could find
Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.
Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.
Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.
The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.
The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.
The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.
In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.
In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.
In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.
Product didn't match the team's ambition
A flow that was supposed to take three clicks
A flow that was supposed to take three clicks
Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.
Scheduling between two parties is a coordination problem at the best of times. The existing flow didn't sync calendars, didn't handle availability windows, and didn't make rescheduling possible.
Scheduling between two parties is a coordination problem at the best of times. The existing flow didn't sync calendars, didn't handle availability windows, and didn't make rescheduling possible.
Product didn't match the team's ambition
Support absorbing the friction
Support absorbing the friction
Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.
Every booking that didn't work meant a phone call to support. The team was triaging logistics that the platform was supposed to handle on its own.
Every booking that didn't work meant a phone call to support. The team was triaging logistics that the platform was supposed to handle on its own.
Product didn't match the team's ambition
Revenue events stuck behind the wrong UI
Revenue events stuck behind the wrong UI
Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.
Interviews are where the platform's value gets realised. If candidates and clinics couldn't book one, the rest of the funnel didn't matter.
Interviews are where the platform's value gets realised. If candidates and clinics couldn't book one, the rest of the funnel didn't matter.
Product didn't match the team's ambition
Two user types. Different habits. Same flow.
Two user types. Different habits. Same flow.
Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.
Some clinics worked with digital calendars. Others didn't. The team had assumed everyone did. Discovery surfaced that assumption fast, and it had been baked into the original design.
Some clinics worked with digital calendars. Others didn't. The team had assumed everyone did. Discovery surfaced that assumption fast, and it had been baked into the original design.
"The way candidates and medical practices manage to schedule interviews needed to be fixed ASAP since it was the major point in our application."
"The way candidates and medical practices manage to schedule interviews needed to be fixed ASAP since it was the major point in our application."
"The way candidates and medical practices manage to schedule interviews needed to be fixed ASAP since it was the major point in our application."
Catrinel Hagivreta
Catrinel Hagivreta
Co-founder + CEO
Co-founder + CEO
the results
the results
A flow that does the work the support team used to do
Validated before code. Adopted after launch.
Five customers tested the new flow before any code was written. Calendar sync, async availability windows, the option to add a second interview without picking up the phone: each one came directly from a real user reaction in testing. The redesign didn't replace the platform. It replaced the workaround.
Five customers tested the new flow before any code was written. Calendar sync, async availability windows, the option to add a second interview without picking up the phone: each one came directly from a real user reaction in testing. The redesign didn't replace the platform. It replaced the workaround.
Five customers tested the new flow before any code was written. Calendar sync, async availability windows, the option to add a second interview without picking up the phone: each one came directly from a real user reaction in testing. The redesign didn't replace the platform. It replaced the workaround.
Validated solution
Validated solution
Validated solution
Support team load
Support team load
Support team load
Projected revenue
Projected revenue
Projected revenue
"This project had a major impact on our product roadmap and business overall."
"This project had a major impact on our product roadmap and business overall."
"This project had a major impact on our product roadmap and business overall."
Catrinel Hagivreta
Catrinel Hagivreta
Co-founder + CEO
Co-founder + CEO
how we got there
how we got there
Three phases. Two weeks.
One flow, fixed.
Three phases. Two weeks.
One flow, fixed.
Three phases. Three weeks. An MVP validated by 5, adopted by 50,000.
diagnose
diagnose
diagnose
Where exactly is the platform losing people?
What does this community actually need from a product?
Discovery workshop with the founders, product marketing manager, sales manager, and senior recruiter. Mapped competitors, defined the primary user persona, and built the customer journey end-to-end. The work surfaced one specific bottleneck: scheduling. That was where the platform's value was breaking down.
Discovery workshop with the founders, product marketing manager, sales manager, and senior recruiter. Mapped competitors, defined the primary user persona, and built the customer journey end-to-end. The work surfaced one specific bottleneck: scheduling. That was where the platform's value was breaking down.
Discovery workshop with the founders, product marketing manager, sales manager, and senior recruiter. Mapped competitors, defined the primary user persona, and built the customer journey end-to-end. The work surfaced one specific bottleneck: scheduling. That was where the platform's value was breaking down.
define
define
define
What does this flow look like for
users who don't think like us?
What's the smallest version of this that's worth testing?
Walked through the existing process with founders and customers, breaking an early assumption that everyone used a digital calendar. Aligned the team on long-term goals, researched comparable patterns, and ran a sketching exercise where every team member proposed a solution. Built a clickable prototype from the most promising direction.
Walked through the existing process with founders and customers, breaking an early assumption that everyone used a digital calendar. Aligned the team on long-term goals, researched comparable patterns, and ran a sketching exercise where every team member proposed a solution. Built a clickable prototype from the most promising direction.
Walked through the existing process with founders and customers, breaking an early assumption that everyone used a digital calendar. Aligned the team on long-term goals, researched comparable patterns, and ran a sketching exercise where every team member proposed a solution. Built a clickable prototype from the most promising direction.
refine
refine
refine
What did engineers need to ship
the fix without breaking the rest?
What do engineers need to ship without ambiguity?
Tested the prototype with five customers. The flow itself got positive feedback. Testing also surfaced label confusion, a need for monthly availability options, and a dashboard that wasn't doing the job we thought it was. Each finding became a specific design decision before the team moved into development.
Tested the prototype with five customers. The flow itself got positive feedback. Testing also surfaced label confusion, a need for monthly availability options, and a dashboard that wasn't doing the job we thought it was. Each finding became a specific design decision before the team moved into development.
Tested the prototype with five customers. The flow itself got positive feedback. Testing also surfaced label confusion, a need for monthly availability options, and a dashboard that wasn't doing the job we thought it was. Each finding became a specific design decision before the team moved into development.
where we start
where we start
Let's find out where users get stuck, and what to fix first.
Let's find out where users get stuck,
and what to fix first.
Let's find out where users get stuck,
and what to fix first.
We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.
We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.
We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.
more case studies
more case studies
Different products.
Same pattern of outcomes.
Different products.
Same pattern of outcomes.
Different products.
Same pattern of outcomes.
Product Design Studio
for growth-stage SaaS teams
© Durran 2026
Product Design Studio
for growth-stage SaaS teams
© Durran 2026
Product Design Studio
for growth-stage SaaS teams
© Durran 2026
Product Design Studio
for growth-stage SaaS teams
© Durran 2026