Loading…
An honest offer: we can't pay you — yet. But we can teach you skills your first job probably won't.
Three ways to grow with us — and with your own career.
Learn how to market a platform to its potential users
You'll take ScholarBase to the people it was built for — scholar by scholar, university by university. Campus by campus, community by community, you'll figure out what makes academics care, sign up, and stay. Along the way you'll learn:
Learn how professionals find every bug, in every corner
You'll put ScholarBase through every scenario a real user could throw at it — and plenty they shouldn't. Our developers will know about every teeny-tiny bug in every corner before our users ever find them. Along the way you'll learn:
Find verified opportunities and build the directories scholars rely on
You'll grow ScholarBase's most valuable asset: trustworthy information. That means finding and verifying opportunities in admissions, vacancies, events, and results, and building our directories — PhD supervisors, research grants, research tools, the learning zone, and research journals — so scholars everywhere get one reliable place for everything academic. Along the way you'll learn:
Skip the toy projects. Everything you do — campaigns, curated listings, bug reports — happens on a live, open-source platform used by scholars around the world, and your contributions are public for everyone to see.
Growth marketing, quality assurance, and research curation are three of the most in-demand, hard-to-teach skills. You'll learn them by doing, not by watching tutorials.
Every experiment, campaign, and bug report gets detailed feedback. You'll learn the why behind every decision, not just the what.
Grew signups from a new campus? Caught a critical bug before launch? That's a measurable, interview-ready achievement with your name on it.
Students, fresh graduates, and early-career folks who want to break into growth marketing or software QA. We don't care much about your degree or your college name — we care about:
* All em dashes on this page are 100% human-written. An AI would have used far more of them — believe us — and we simply refuse to be outdashed by a machine. Yes, we see the irony of that sentence.