Home - OmarAbdelmotaleb/Jobber GitHub Wiki
Project Overview
Imagine a job search where juggling multiple applications and deadlines doesn't feel like a overwhelming and chaotic act. Introducing Jobber, the Job Application Tracker, your one-stop software solution for organization and efficiency. Designed for job seekers across industries and experience levels, it tackles the common pain points of managing applications, boosting your chances of landing that dream role.
The Problem: Disorganized applications, forgotten deadlines, and scattered information can leave you feeling overwhelmed and frustrated. Struggling to track progress and tailor applications for each opportunity hinders your chances of success and therby leading to missing job opportunities.
The Solution: Jobber centralizes everything. Create detailed profiles for each application, storing resumes, cover letters, notes, and interview information. Visualize your progress with customizable filters, receive timely reminders, and never miss a job opportunity. Manage company and contact details effortlessly, and leverage the resume parser to tailor your applications with missing keywords from the job description.
What does success look like for us?: We measure success by your transformed job search experience. Imagine feeling organized, confident, and in control. Picture yourself landing more interviews, securing offers, and ultimately, landing that dream job. With Jobber, your job search becomes a strategic journey, not a chaotic scramble. Let's get you there!
Roles
- Project Lead: Raj Palival
- Back-End Developer: Omar Abdelmotaleb, Dev Patel
- Front-End Developer: Raj Palival
- Dev-Ops Engineer: Arjun Khatri, Amith Vishnu
Communications Plan
- Our only means of communication is Discord.
- All the project submission files are shared on OneDrive so that it's easier for the project lead to submit them to canvas. If you want to find this common shared folder, it's link is in the resources channel.
- If you have any sort of future resources that you may have used or if the team can find it helpful it should be shared in the resources channel of discord only.
Working team meetings
These meetings form the core of the team’s collaboration and can be used for brainstorming, pair-programming, debugging, prototyping, internal reviews of each other’s work, etc. Except for the weekly status meetings, these are done without the manager’s (the instructor) involvement. Often it can be done by the team during the time of the scheduled class while other teams are having status meetings, but this may not be convenient if the team is a hybrid mix where some members are on campus while others are remote.
Whether you have your working meetings during class time or not, each team should also agree upon some recurring time(s) when to meet to work as a group in case it is needed. State here what has been agreed upon for the working team meetings.
Decided upon: Decision of working team meetings will be done after Feb 6, 2024 class hours and updated here.
Issues meetings
If a problem does arise, never surprise your manager. Schedule a meeting at his or her earliest convenience. This section describes how alerts will arise and the governance of when to trigger an alert – usually after a discussion at a working team meeting.
Status meetings
Status meetings are meetings where the project manager and/or project leader reports on status to the instructor. These will occur weekly over the duration of the project during scheduled class time with the entire team present so they can all speak to any questions of status to the instructor.
Timeline and Milestones
Look forward for the next 10 to 13 weeks and plan out a set of target milestones (estimated) that the team expects to meet over the duration of the project, culminating in the final presentation at the end of the semester.
Risks
Describe any risks that you see for this project, and how they will be track and monitored.
Assumptions
State any assumptions you have about this project.