Contact person: Business Client

Phone:Show

Email:Show

Location: Wilayah Persekutuan, Malaysia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I run an IT training institute and now that several cohorts have graduated, I want to give them a single destination to present their skills and secure work. I need a web-based portal that serves three audiences—Students, Employers, and an internal Admin team—while remaining simple enough to launch quickly and iterate.

Scope of work
• Design the overall information architecture: authentication, role permissions, and navigation for the three user types.
• Draft wireframes or low-fidelity mock-ups for each dashboard:
– Students: profile completeness indicator, résumé upload, tailored job matches, application timeline, and quick links to interview prep material.
– Employers: company profile, job posting wizard, saved searches, filterable talent list, and candidate short-listing.
– Admin: user management, job moderation, analytics (sign-ups, applications, hires).
• Build the core modules:
– Profile & résumé builder that stores skills, certifications, GitHub/LinkedIn links, and a PDF résumé.
– Job board with tagging and application tracking; students should see status updates in their dashboard.
– Employer filters for skills, location, and experience level with instant candidate cards.
– Messaging/notification layer (in-app + email) for interview requests and system alerts.
– LinkedIn OAuth so students can import basic data and share applied-jobs on their feed (optional in Phase 2).
• Define an MVP roadmap with milestones, estimating roughly 3 incremental releases:
1. Phase 1: Authentication, basic student profiles, manual job posting, static employer list.
2. Phase 2: Advanced filtering, résumé parsing, notifications, and LinkedIn import.
3. Phase 3: Analytics dashboard, automated interview scheduling, and rich content library for career guidance.

Tech stack guidance
I’m open to a modern low-code route (Bubble, Glide, Softr) if it accelerates Phase 1, but I’m equally comfortable with a conventional full-stack setup—React or [login to view URL] front end, Node/Express or Django back end, PostgreSQL, and AWS or Vercel for hosting. Please weigh the trade-offs and suggest what best fits an MVP that can later scale to ~5 000 users.

Deliverables
1. Wireframes or Figma designs for all main pages.
2. Technical architecture document outlining chosen stack, third-party integrations, database schema, and user-flow diagrams.
3. Working MVP deployed to a test domain with the Phase 1 feature set.
4. Clear setup instructions and a backlog plan for Phases 2-3.

If you can cover UI/UX, development, and deployment—or can assemble a small team—please explain your proposed stack, timeline, and any similar projects you’ve shipped." (client-provided description)