When I started working on Curabix, the idea sounded straightforward: build a place where healthcare professionals could find jobs and employers could find the people they needed.
Once I started building it, I quickly realized that a job platform is much more than a page full of vacancies.
You have job seekers trying to find relevant opportunities quickly. Employers need a simple way to publish and manage jobs. Search engines need pages they can actually understand and crawl. And everything still needs to work properly on a phone with a less-than-perfect connection.
That has made building Curabix an interesting learning experience.
The stack behind Curabix
The frontend is built with Angular and TypeScript. On the backend, I'm using NestJS with PostgreSQL.
I chose this setup because I wanted a clear separation between the frontend and API while still keeping TypeScript across most of the project.
As the platform grew, the work expanded into areas I didn't think much about at the beginning:
- server-side rendering
- authentication and authorization
- structured job data
- search-friendly URLs
- job expiration and reopening
- responsive interfaces
- performance
- technical SEO
Some of these ended up being harder than building the original job posting form.
Job discovery is really an information problem
One thing I've learned is that simply storing jobs isn't enough.
Someone looking for a nursing position in Lahore doesn't want to scroll through unrelated jobs from different cities and professions. The platform has to understand location, profession, category and the status of each vacancy.
That changed how I thought about the site's structure.
Instead of treating every job as an isolated database record, I've been working toward a structure where people can browse jobs naturally by country, city and profession.
It also makes URLs more meaningful for both users and search engines.
Expired jobs need careful handling
This was another surprisingly interesting problem.
Healthcare vacancies don't stay open forever. On Curabix, jobs have a defined active period, after which they can be closed. Employers can also close a position earlier or reopen it when they need candidates again.
It sounds like a small feature until it touches everything else.
An expired position shouldn't continue appearing as an active opportunity. Applications need to respect the job's current state. Search pages need accurate results, and old URLs need sensible behavior.
It taught me that lifecycle rules should be designed as part of the data model rather than patched into the UI later.
SEO changed some architectural decisions
Before working on a job platform, it was easy to think of SEO mainly as titles, descriptions and keywords.
I've learned that technical decisions matter just as much.
If useful job pages aren't rendered properly for crawlers, URLs are inconsistent, canonical tags point to the wrong place, or closed vacancies keep producing low-value pages, good content alone won't solve the problem.
Server-side rendering became especially important for this reason.
I'm also working on structured data and location-based pages so that search engines can better understand what each page represents.
Mobile experience matters a lot
A job site has to work well on small screens.
People may discover an opportunity from a search result or social post and want to check the requirements immediately. They shouldn't have to fight with filters, oversized forms or broken layouts just to read a vacancy.
That has made responsive behavior something I test throughout development rather than something to fix at the end.
What I'm building toward
The goal with Curabix is to make healthcare job discovery simpler for professionals while giving healthcare employers an easier way to reach relevant candidates.
I'm currently focusing on improving search and discovery, employer tools, performance and the overall experience of moving from finding a vacancy to applying for it.
There's still plenty to build.
But one of my biggest lessons so far is that building a useful platform isn't about adding the most features. It's about removing friction from the few things users actually came there to do.
For Curabix, that's helping someone find the right healthcare opportunity — and helping an employer find the right person.
I'll share more of the technical lessons as the platform evolves.
Top comments (0)