Full-stack product · Responsive web application
A private job-application management website that helps job seekers capture opportunities, track recruitment progress, plan next actions, evaluate performance, and manage supporting documents in one focused workspace.
LAMARIN is a private job-application management website for people handling multiple recruitment processes at the same time.
It connects vacancy capture, application records, Kanban tracking, recruitment planning, personal analytics, CVs, and cover letters in one account-based workspace. It is not a job marketplace and it is not an applicant-tracking system for recruiters. The product is built for the job seeker.
Defined the problem, user, MVP boundary, feature requirements, business rules, priorities, and acceptance conditions.
Designed the information architecture, application flows, responsive interface, data hierarchy, states, and visual system.
Implemented the website interface, routing, forms, dashboard views, interactions, responsive behavior, and feedback states.
Implemented authentication, application logic, PostgreSQL data access, private storage, document handling, and ownership controls.
Validated end-to-end workflows, production authentication, storage policies, persistence, responsive behavior, and deployment.
One application can involve a job portal, spreadsheet, inbox, calendar, notes app, and several document folders. As the pipeline grows, users lose a reliable view of where each opportunity stands and what should happen next.
Company details, vacancy links, notes, schedules, and documents live in different tools.
Users repeatedly reopen individual records just to understand the state of the recruitment pipeline.
Interview preparation, assessments, recruiter follow-ups, and deadlines compete with unrelated activity.
Users cannot easily see which sources perform well, where applications stop progressing, or which records need attention.
“Active job seekers need one reliable workspace to understand where every application stands, what must happen next, and what their own job-search data is telling them.”
The product strategy was to reduce tool switching without turning LAMARIN into an oversized recruitment platform. Every core feature supports one of four decisions in the job seeker’s workflow.
Create a reliable application record.
Understand progress across the pipeline.
Turn applications into scheduled actions.
Use personal data to improve decisions.
Included in the production scope
Deliberately outside the MVP
The mockups below use desktop browser frames because LAMARIN is a responsive web application. Each section explains the user decision supported by the feature—not only what appears on the screen.
What needs attention today?
The dashboard is the user’s starting point. It summarizes the current application pipeline, recruitment performance, recent activity, and upcoming actions so the user can decide what to do next without reopening every record.
How can a vacancy become a structured record quickly?
Users can begin with the original vacancy link or enter an application manually. Available information can be captured first, while incomplete fields remain editable instead of blocking the workflow.
Where does the complete recruitment context live?
Each application keeps the vacancy data, original source, personal notes, salary range, recruitment status, reminders, and supporting documents in one detailed view. Editing updates the same record used across Dashboard, Board, Calendar, and Insights.
Where is every application in the recruitment process?
The Board turns application status into a visual workflow. Users can scan the entire pipeline, search within the board, open details in context, and move cards between stages while preserving the underlying record.
What happens next, and when?
The Calendar translates next actions into a readable schedule. Interviews, tests, deadlines, and recruiter follow-ups remain connected to the related application instead of becoming isolated calendar entries.
How does a record become a concrete next step?
A reminder can be created from the calendar or application context by selecting the related application, naming the action, and defining its date and time. The result is reflected throughout the workspace.
What is working, and what should change?
Insights transforms application data into practical reflection. Users can review performance by period, understand pipeline health, compare opportunity sources, monitor weekly goals, and identify applications that need attention.
How are CVs and cover letters kept with the right application?
Users can upload, download, and replace the CV or cover letter associated with an application. Replacement is handled safely: the new file succeeds first, then the previous object is removed automatically.
How does each user reach only their own workspace?
LAMARIN supports email credentials and Google OAuth, with protected application routes and password recovery. Authentication establishes the account identity used to scope records, storage folders, and document access.
How can visitors understand the product before creating an account?
Demo mode exposes the core product experience with temporary sample data. It allows visitors and recruiters to explore the workflow without mixing demonstration records with a real user account.
The interface adapts its navigation, content density, and interaction layout across desktop, tablet, and mobile widths. Light and dark themes preserve the same hierarchy, while Demo mode clearly identifies temporary data.
LAMARIN stores private recruitment information and personal documents. Security therefore cannot depend on whether a button or route is hidden in the interface.
Account identity is checked through authentication, application records are protected with Row Level Security, and documents are stored in a private bucket under folders scoped to the user ID.
Responsive website pages, server and client components, routes, forms, interface states, and interaction logic.
Application CRUD, status movement, reminder handling, authentication callbacks, validation, and document replacement workflow.
Application records, ownership, constraints, queries, persistence, and Row Level Security policies.
User-scoped folders, owner-only policies, allowed file types, file-size restriction, and protected downloads.
Environment separation, OAuth callback configuration, protected routes, Vercel deployment, and production smoke testing.
When a CV or cover letter is replaced, the new file is validated and uploaded first. Metadata is updated only after success, and the previous object is then removed so a failed replacement does not erase the user’s existing document.
Validation covered the product from account access to production deployment. The objective was not merely to prove that individual controls respond, but that records, reminders, metrics, documents, and ownership remain correct across the complete workflow.
Email access, Google OAuth, protected routes, forgot password, and reset password
PassedJob-link import, manual entry, validation, document selection, and new record creation
PassedDetail, editing, status updates, persistence, search, and cross-view consistency
PassedReminder creation, calendar display, upcoming actions, metrics, filters, and attention states
PassedUpload, download, replacement, file validation, and automatic old-file deletion
PassedRow Level Security, private bucket, authenticated policies, and account-scoped folders
PassedLive deployment, authentication callback, responsive review, theme behavior, and smoke test
PassedDiscover
Reviewed how job seekers move between vacancy platforms, spreadsheets, email, calendars, notes, and document folders during one recruitment process.
Define
Prioritized application capture, pipeline tracking, planning, analytics, private documents, and account access while excluding recruiter tooling, automatic applications, and broad marketplace features.
Design
Designed Dashboard, Board, Calendar, and Insights as different perspectives of the same application record, supported by detail, reminder, document, and authentication flows.
Develop
Built the responsive product with Next.js, React, TypeScript, Supabase Auth, PostgreSQL, private Storage, protected routes, and Vercel deployment.
Validate
Verified account access, application management, status persistence, reminders, document upload and replacement, ownership policies, and production behavior.
LAMARIN was implemented, secured, tested, and deployed as a working website. Its strongest design decision is not a single screen—it is the consistency of one application record across capture, tracking, planning, analytics, and document workflows.
Dashboard, Board, Calendar, and Insights answer different questions while remaining synchronized through one data model.
OAuth callbacks, password recovery, document replacement, and owner-only policies required validation beyond the visible interface.
Future iterations should use real behavioral data and user research to improve the workflow before expanding into broader features.
Open the live deployment or enter Demo mode to review the complete responsive workflow without relying only on this case study.