Skip to content

FROM THE FOUNDER / MABASA GUIDES

Why I built Mabasa: fewer websites to check when looking for work

The problem behind Mabasa: repeating job searches across websites and losing track of saved roles and applications.

THE SHORT ANSWER

I built Mabasa to reduce the time people spend finding and organising job adverts. It collects listings from different sources so you can search them together, then open the original posting to apply.

The same search, again

Say you are looking for a financial analyst role in New York. You check a company’s Workday careers page, LinkedIn and eFinancialCareers. This is an example of the search routine, not a claim that every advert on those platforms appears in Mabasa.

You save links. Later, you need to remember where you saw a role and whether you already applied. The problem is both finding opportunities and keeping a useful record.

Put the collected jobs in one view

Mabasa brings adverts from the sources we collect into a searchable feed. You enter a role and location, review the results and follow the original link. You still decide what fits your experience and where to apply.

Make it easier to pick up where you left off

Saved jobs and the application tracker give you somewhere to return to. The free manual CV builder helps you prepare your document. There is still more to build, and feedback about a confusing step helps me decide what to improve next.

Sources & product details

    Product instructions reflect the implementation reviewed on 6 November 2026. Example screenshots may differ from your device or a later release. This guide is prepared by Mabasa; external sources do not endorse the product.