Recruitment workflow
The workflow diagram traces candidate discovery, recruiter offer publishing and application status tracking, based on the project documentation.
Interlance
My contribution
Where I focused.
- Contributed to the Spring Boot backend and recruitment API workflows.
- Worked on backend testing and API validation.
- Collaborated with teammates on the Angular web and React Native mobile clients.
01 / The problem
Recruitment and freelance operations become fragmented when company records, offers and candidate applications live in separate tools. Teams lose context and spend time reconciling status changes manually.
02 / My response
Our team built web and mobile recruitment workflows around a Spring Boot API and MongoDB. I focused on backend development and testing, collaborating with teammates on the client applications and integration.
What changed
01
Unified the core recruitment workflow
02
Made application state visible at a glance
03
Designed for web, mobile and API consumers
A quick product walkthrough
Evidence & verification
Architecture
The system diagram connects Angular and React Native clients, Spring Boot, MongoDB and explicitly optional integrations.
Candidate and recruiter actions converge on the application record.
Documented local setup, with optional production integrations.
Engineering decisions
The choices behind the interface.
Domain-first backend
Separated users, companies, offers, applications and subscriptions so each workflow can evolve without becoming tightly coupled.
Role-aware interfaces
Adapted navigation and actions to the person using the system instead of exposing one overloaded dashboard.
Integration boundaries
The architecture separates core recruitment data from configurable authentication, file storage, matching and payment integrations.
Stack & capabilities
Spring BootMongoDBAngularReact NativeDocker
View source on GitHub ↗