Internships & placements
Discover opportunities, review applications, and manage student placements.
Made for students, employers, and placement teams.
Overview
This platform family is under active development. The scope below describes its intended design; deployment readiness and supported capabilities must be confirmed for each engagement.
Students need more than a generic jobs list. A useful internship search must relate to a course of study, skills, location, and the student's stage of education. Companies need to understand those applicants and manage the process after an application arrives.
Baobab's platform connects discovery, recruitment, and placement records. It gives students a clear application journey, companies a focused recruitment workspace, and operators the controls needed to review participants and listings. The relationship continues beyond acceptance through placement and logbook workflows.
What is included
Student experience
Discover and apply
Students build profiles containing educational and skills information, browse opportunities, and narrow their search using relevant filters. Listing details explain the role before a student applies, while application history provides a place to follow submitted applications.
Deterministic matching rules connect student-profile information to opportunity relevance. Because the matching logic is explicit, the product can explain and test its behaviour without treating an opaque model as the authority over a student's prospects.
Guided onboarding helps students provide useful information while communicating profile visibility. Public opportunity pages support discovery before sign-in; protected application and profile actions belong to the authenticated student experience.
Company workspace
Recruit with context
Company representatives create and maintain a company profile, author listings, and manage listing lifecycles. Applicant review connects applications to the student's relevant course, graduation-year, and profile information, with filtering suited to recruitment decisions.
Companies can follow applications and accepted placements through their own workspace. Ownership checks keep applicant information within the company responsible for the opportunity. This gives the recruitment process a defined place to happen, with less dependence on scattered emails and unrelated spreadsheets.
Placement and logbook
Document the experience
Accepted applications connect to placement records. Students and companies can work with internship logbooks and placement-related documents, extending the platform from recruitment into the experience itself.
Reports provide a way to bring placement information together. The practical journey is a student finding an opportunity, submitting an application, being accepted, and maintaining a record of the placement. The platform therefore supports both the discovery problem and the administrative work that follows a successful match.
Operator controls
Maintain public quality
Administrative workflows support company verification and listing moderation. Admission and listing-publication states determine what becomes publicly discoverable, keeping the public catalogue connected to a reviewed process.
The operator's role is distinct from the company's recruitment role. Verification establishes whether a company can participate in the intended workflow; it does not turn an operator into the owner of every applicant record.
Built with
Baobab separated internship domain rules, data access, interface components, and deployment concerns in a TypeScript monorepo. A React application communicates with a Hono API on Cloudflare Workers, backed by Neon PostgreSQL. Clerk supplies identity, while role and ownership checks protect the business operations.
The application supports both public discovery and authenticated work. Build-time public pages and request-time listing rendering connect search-oriented access to the same product that handles applications and placements. The matching engine is independently testable, and remote repositories connect the frontend to persistent API records rather than requiring the prototype's local storage.
Questions
Is this available for deployment?
Deployment readiness has not yet been verified for this catalogue entry. Contact us to discuss current scope, release gates, and your requirements.
Who owns this software?
This is owned engineering work from The Baobab, a brand of Fortezza Nuova Enterprise. Deployment and licensing terms are agreed for the relevant product.
Run Internships & placements in your organisation
Discuss the capabilities you need, deployment environment, and integration responsibilities. We will confirm current readiness and agree a scope before committing to a release.