---
# System prepended metadata

title: First Team Meeting Worksheet

---

# First Team Meeting Worksheet

[click here for selfie](https://freeimage.host/i/Lq9Spa)

## Team Members Present

* William Toth
* Christopher Long
* Emily Zhou
* Karsten Kleyensteuber

## I. Identify a Common Vision
Tech recruiting/job recruiting is a tedious and confusing process. We want to create something that helps those looking for jobs break through the existing barriers of entry and make the process smoother and easier to navigate. 

### Commonalities
Common interest: 
* Shared experiences / frustrations with the recruitment process.
* Want a good selection of potential jobs without wasting time that we could be enjoying in our last year of college.

### Inspiration
*What are some things each of you is inspired by?*
* The potential to create a product which could benefit our peers at Dartmouth, other institutions and the professional world. 


### Problems of Interest
*What problems are you looking to address? Why?*
* Applying to jobs and never hearing back
* Know about the interview process of a company
* Organizing jobs you're interested in when you've applied to many. Google docs gets tedious
* Figuring out what companies have jobs available, community lists are outdated and roles are sometimes added weeks after they first became available
* Knowing about compensation/benefits before applying, sometimes the potential benefits allow you to judge whether you even need to apply (the case of an existing offer from another company paying way better or the potential company having a nonstarter of a location) 
* Identifying possible referral sources
* Knowing when jobs were posted, if they are stale
* Different tech stacks make it hard to sift through roles you actually fit
* Centralizing components of the application process which would otherwise be separated.
* Increasing time-efficiency of applying for tech jobs.


### Identify
*Which of the above is most interesting to all of you?*

* Knowing when jobs were posted, if they are stale
* Figuring out what companies have jobs available, community lists are outdated and roles are sometimes added weeks after they first became available
* Organizing jobs you're interested in when you've applied to many. Google docs gets tedious

## II. Narrow In
*Now let's try narrowing in on a problem that interests all of you. Make sure to go around the table and listen to everybody on your team without interruption.*
* The frustration of organizing many jobs you've applied to efficiently and not hearing back from companies because job postings are not relevant, stale

#### Coolness
*What could be cool about this potential project?*
* Immediate impact; this project doesn't rely on a large user base or outside parties to be useful or valuable for users.
* Can be shared easily amongst existing communities (reddit, github)

#### Challenges
*What could be challenging / unfun about this potential project?*
* Staying up to date with current companies applications (still taking applications, new applications, closed applications)
* Filtering or sorting irrelevant or poor quality opportunities.
* Creating a product specific enough to address our problem, while being general enough to have a significant user base.
* Getting compensation/benefits data about companies (glassdoor is too out of date and not specific enough, blind is not filterablee enough, and levels hides data until a certain number of entries since they share too many details)
* Crafting a product that is unique and doesn't overlap with an existing product in the tech recruitment space without significant innovation

#### Success
*What does success look like for this project?*
Create a product that is easy to navigate and can address the core issues we mentioned above. A product that catches on with reddit communities and among students looking for tech jobs. Becomes synonymous/inseparable with the tech recruitment process