---
# System prepended metadata

title: Untitled

---

## T2 Project Reflection and Next Steps Worksheet

## Original idea

* Quick and easy way to find relevant jobs for students iun tech
* Easy and intuitive organization of applications
* Tech tips to help students with navigating roles and applications


#### MVP Progress?
* We were able to finish our MVP, which was the feature above minus a way of populating new roles, login, and dynamic widgets.


#### How is it different?
* The UI has of course changed, but we haven't strayed very far from the initial vision. The only big difference is the widget page, which was not part of our initial MVP but proved to be a big success during technigala.

#### Still happy with direction?
* Yes, but we'd like to dive into harder areas like job population and un hard coding widgets.

#### What do you wish went differently?
* I wish we had figmad out everything before diving in. Our lack of figma work caused some UI troubles that could have been resolved earlier

## Feedback
*What feedback from last term do you think is relevant and interesting to incorporate. List your feedback broadly and label them with how they stack up for your vision. These may already be in ZenHub but after this discussion they should be.*

* [critical 🔥]
    * option to get rid of rejected apps
* [stretch goal 🍦]
    * Email widget page
    * Connect users with other people who are applying
* [rejected ⛔]
    * Companies use this to see students who are applying: rejected because already sort of exists and would be beyond the scope of what we are trying to implement

#### Questions
*Think about where the project is headed. What are some questions that you/users/me have about direction/features/functionality that could use some validation?*
* Will the current features planned be compelling to potential users?
* How can we best package are different major features (board, widgets, and job postings) into a cohesive, easy to understand product?
* What solution to the updating the new jobs posting page will best balance difficulty of implementation and effectiveness?

#### Answers
*Think of ways that you might validate these: discussion with your team, advice from me, polling the class, asking users, and/or collecting and analyzing usage data. Write down some ideas here. This isn't how to validate your project as a whole, but about specific feedback/features.*
* The current features would be compelling, but they are not entirely functional
* UI that makes everything connected, lots of buttons the lead to each other
* For effectiveness: web scraping, for ease: posting api

## Vision
*Refine your vision.*

#### Feedback Analysis
Feedback that we thought was particularly interesting was the addition of social/connective features. Potential ideas were connecting users with each other or with the companies themselves. 

#### Pivot/Adjustment
*If you were to consider a pivot or adjustment in what the product is, what would it be?*

Two possible pivots:
* Emphasize social connection and help build a community around the recruitment process
    * Pros: Social Media aspect that if done right can propel user growth
    * Cons: People might not be clamoring to help potential competitors fighting for job positions
* Cater to employers/recruiters rather than applicants by helping to find potential employees with matching skill sets and having a platform for employers to promote themselves to applicants.
    * Pros: Attracts new users on both sides, employers want to have access to a large pool of applicants and applicants can get better visibility with recruiters.
    * Cons: Existing products exist that are close to this (Handshake, LinkedIn to an extent) 

#### Ideal Goal
*In an ideal world if you could build out your project to be anything without any constraints of time or skill what would you want to do? Dream big — you can do more than you think. Try to push the limits. This does **not** commit you to anything, so don't worry about overpromising, this is to get you dream about where you **really** want your project to go without constraints. Please don't skimp on this part.*

In an ideal world, we would want to implement a web scraping tool that had the capability to search through many/all job listings, preferably on the official company websites themselves. This would allow users to have accesible applications in a timely manner to when they were released. 

More generally, we would like to be able to build our database with more information in order to give the user more tools and current up to date information. 

#### Mission Statement

To build a tool for users with features that they not only find helpful but also didn't think they needed.


## How to get there
*Now that you've thought about where your project is headed and where you want it to go write down how might approach getting there.*

We think a 2 weeks RnD phase to flush out what the best way of adding data we don't have and then jump into implementation after that.

#### What are your concrete next steps?
Research jobs api, scraping, and other means of adding jobs in the first few weeks

Find ways to get data for widgets without hard coding, which will vary based on each widget.

Add auth, ability to customize UI in backend
 
Add a calendar for notifications for job deadlines, interviews

#### What are some blockers in your way? 
Time, making sure to prioritize and do the things we are able to get done and implement well versus features that are useful but out of our reach. 

Difficulty of getting data we do not have. Our project relies on it.

## TeamWork

Making sure that all of us are communicating well and holding ourselves accountable for time spent and work done.  

