├── .github ├── CODE_OF_CONDUCT.md ├── ISSUE_TEMPLATE.md ├── ISSUE_TEMPLATE │ ├── Bug_report.md │ └── Feature_request.md ├── PULL_REQUEST_TEMPLATE.md └── funding.yml ├── .gitignore ├── CONTRIBUTING.md ├── LICENSE ├── README.md └── docs ├── .nojekyll ├── 01-prepare ├── README.md └── product-manager.md ├── 02-search ├── README.md └── research.md ├── 03-apply ├── README.md ├── cover-letters │ └── README.md ├── online-presence.md ├── replying.md └── skills.md ├── 04-interview ├── README.md ├── answering.md ├── asking.md ├── checklist.md ├── follow-up.md └── intros.md ├── 05-accept ├── README.md └── salary.md ├── _coverpage.md ├── _images ├── favicons │ ├── favicon-114.png │ ├── favicon-120.png │ ├── favicon-144.png │ ├── favicon-152.png │ ├── favicon-180.png │ ├── favicon-192.png │ ├── favicon-32.png │ ├── favicon-36.png │ ├── favicon-48.png │ ├── favicon-57.png │ ├── favicon-60.png │ ├── favicon-72.png │ ├── favicon-76.png │ ├── favicon-96.png │ └── favicon.ico └── icon.svg ├── _sidebar.md └── index.html /.github/CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hello@fvcproductions.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | Insert description of issue here 2 | 3 | --- 4 | 5 | 6 | 7 | 8 | 9 | > ✅️ By submitting this issue, I have verified the following 10 | 11 | * [] Checked to see if the issue has already been discussed before 🤔️ 12 | * [] If proposing new content to be added, made sure enough details were provided 🔍️ 13 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/Bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | 5 | --- 6 | 7 | **Describe the bug** 8 | A clear and concise description of what the bug is. 9 | 10 | **To Reproduce** 11 | Steps to reproduce the behavior: 12 | 1. Go to '...' 13 | 2. Click on '....' 14 | 3. Scroll down to '....' 15 | 4. See error 16 | 17 | **Expected behavior** 18 | A clear and concise description of what you expected to happen. 19 | 20 | **Screenshots** 21 | If applicable, add screenshots to help explain your problem. 22 | 23 | **Desktop (please complete the following information):** 24 | - OS: [e.g. iOS] 25 | - Browser [e.g. chrome, safari] 26 | - Version [e.g. 22] 27 | 28 | **Smartphone (please complete the following information):** 29 | - Device: [e.g. iPhone6] 30 | - OS: [e.g. iOS8.1] 31 | - Browser [e.g. stock browser, safari] 32 | - Version [e.g. 22] 33 | 34 | **Additional context** 35 | Add any other context about the problem here. 36 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/Feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | 5 | --- 6 | 7 | **Is your feature request related to a problem? Please describe.** 8 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 9 | 10 | **Describe the solution you'd like** 11 | A clear and concise description of what you want to happen. 12 | 13 | **Describe alternatives you've considered** 14 | A clear and concise description of any alternative solutions or features you've considered. 15 | 16 | **Additional context** 17 | Add any other context or screenshots about the feature request here. 18 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | Insert description of PR here 2 | 3 | --- 4 | 5 | 6 | 7 | 8 | 9 | ## ✅️ By submitting this PR, I have verified the following 10 | 11 | ### Guidelines 12 | 13 | #### Content 14 | 15 | > If adding new advice or content, 16 | 17 | * [] A tool like [Grammarly](https://grammarly.com/) was utilized to check for spelling and grammar. 18 | 19 | #### Resources 20 | 21 | > If adding a new resource, 22 | 23 | * [] There is a link to the resource. 24 | * [] There is a description describing what benefits the resource offers. 25 | 26 | ### Formatting 27 | 28 | * [] No whitespace. 29 | * [] Spaces, not tabs. Specifically, 2 spaces. 30 | * [] Make sure items in lists are alphabetized. 31 | 32 | ### Adding yourself as a contributor. 33 | 34 | * [] Added my name to the bottom of the list under the _Credits_ section in the `README.md` with a link to my website or GitHub profile 👥️ 35 | -------------------------------------------------------------------------------- /.github/funding.yml: -------------------------------------------------------------------------------- 1 | github: francescoronel 2 | open_collective: francescoronel 3 | ko_fi: francescoronel 4 | liberapay: fvcproductions 5 | otechie: francescoronel 6 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | ## Contributing 2 | 3 | > To get started... 4 | 5 | - 🍴 Fork this repo [here](https://github.com/fvcproductions/hire-me#fork-destination-box) 6 | - 🔨 Hack away 7 | - 👥 Add yourself as a contributor under credits 8 | - 🔧 Make a pull request [here](https://github.com/fvcproductions/hire-me/compare) 9 | - 🎉 Get your pull request approved - success! 10 | 11 | Or just [create an issue](https://github.com/fvcproductions/hire-me/issues) - any little bit of help counts! 😊 12 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2016 FVCproductions 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # hire-me 2 | 3 | A path to getting an awesome tech gig 4 | 5 | > View this project at [`engjobsearch.com`](https://engjobsearch.com) 6 | 7 | ![hire-me](https://i.imgur.com/J1fCB2I.png) 8 | 9 | ## Installation 10 | 11 | I'm using [Docsify](https://docsify.js.org/) as my static site generator to showcase all the resources in this repo. 12 | 13 | To get this up and running locally, type in the following commands. 14 | 15 | ```bash 16 | # It is recommended to install docsify-cli globally, which helps initializing and previewing the website locally. 17 | 18 | npm i docsify-cli -g 19 | 20 | # Run the local server with docsify serve. You can preview the site in your browser on http://localhost:3000. 21 | 22 | docsify serve docs 23 | ``` 24 | 25 | ## Contributing 26 | 27 | > To get started... 28 | 29 | 1. 🍴 [Fork this repo](https://github.com/francescoronel/hire-me#fork-destination-box) 30 | 2. 🔨 View the contributing guidelines at [CONTRIBUTING.md](/CONTRIBUTING.md) 31 | 3. 👥 Add yourself as a contributor under the credits section 32 | 4. 🔧 [Open a new pull request](https://github.com/francescoronel/hire-me/compare) 33 | 5. 🎉 Get your pull request approved - success! 34 | 35 | Or just [create an issue](https://github.com/francescoronel/hire-me/issues) - any little bit of help counts! 😊 36 | 37 | ## Credits 38 | 39 | - [Frances Coronel](http://francescoronel.com) 🍫🍓 40 | - [Brooke Sargent](https://github.com/brookesargent) 41 | - [Brittney Braxton](https://github.com/mintii) 42 | - [Isabel Costa](https://github.com/isabelcosta) 43 | - [Monica Powell](https://github.com/m0nica) 44 | - [Boopathi Kumar](https://github.com/boopathikumar018) 45 | -------------------------------------------------------------------------------- /docs/.nojekyll: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/.nojekyll -------------------------------------------------------------------------------- /docs/01-prepare/README.md: -------------------------------------------------------------------------------- 1 | # Step 1 - Prepare 📚 {docsify-ignore} 2 | 3 | > There are many free resources out there to prepare you for the technical interview. 4 | 5 | 6 | 7 | - [Blogs](#blogs) 8 | - [freeCodeCamp](#freecodecamp) 9 | - [GitHub Repos](#github-repos) 10 | - [awesome-interview-questions](#awesome-interview-questions) 11 | - [code-problems](#code-problems) 12 | - [front-end-developer-interview-questions](#front-end-developer-interview-questions) 13 | - [getting-a-gig](#getting-a-gig) 14 | - [interview](#interview) 15 | - [interviews](#interviews) 16 | - [system-design-primer](#system-design-primer) 17 | - [In-Person](#in-person) 18 | - [Meetup Groups](#meetup-groups) 19 | - [Outco](#outco) 20 | - [Websites](#websites) 21 | - [CodeFights](#codefights) 22 | - [Coderbyte](#coderbyte) 23 | - [Codewars](#codewars) 24 | - [Exercism](#exercism) 25 | - [HackerRank](#hackerrank) 26 | - [Interview Cake](#interview-cake) 27 | - [InterviewBit](#interviewbit) 28 | - [Interviewing.io](#interviewingio) 29 | - [LeetCode](#leetcode) 30 | - [Pramp](#pramp) 31 | - [Further Resources](#further-resources) 32 | 33 | 34 | 35 | ## Blogs 36 | 37 | > If you prefer to read high-level blog posts when trying to ramp up on a specific technology, these blogs come highly recommended. 38 | 39 | ### freeCodeCamp 40 | 41 | [freeCodeCamp's blog on Medium](https://medium.freecodecamp.org/) is pretty amazing and chock full of useful blog posts on development, design and data science. 42 | 43 | ## GitHub Repos 44 | 45 | > GitHub can be an amazing resource for many different topics, especially when it comes to interviewing questions! 46 | 47 | ### awesome-interview-questions 48 | 49 | [awesome-interview-questions](https://github.com/MaximAbramchuck/awesome-interview-questions) is a curated awesome list of lists of interview questions. 50 | 51 | ### code-problems 52 | 53 | [code-problems](https://github.com/blakeembrey/code-problems) covers common code and interview problems solved in multiple languages. 54 | 55 | ### front-end-developer-interview-questions 56 | 57 | [front-end-developer-interview-questions](https://github.com/h5bp/Front-end-Developer-Interview-Questions) is a list of helpful front-end related questions you can use to interview potential candidates, test yourself or completely ignore. 58 | 59 | ### getting-a-gig 60 | 61 | [getting-a-gig](https://github.com/cassidoo/getting-a-gig) is guide for getting a gig in college as a tech major. 62 | 63 | ### interview 64 | 65 | [interview](http://github.com/andreis/interview) provides a full list of useful links that you need to prepare for your technical interview. 66 | 67 | ### interviews 68 | 69 | [interviews](https://github.com/kdn251/interviews) 70 | is your personal guide to Software Engineering technical interviews. 71 | 72 | ### system-design-primer 73 | 74 | [system-design-primer](https://github.com/donnemartin/system-design-primer) helps you learn how to design large-scale systems and prep for the system design interview. 75 | 76 | ## In-Person 77 | 78 | ### Meetup Groups 79 | 80 | There are actually quite a few [Meetup groups](http://www.meetup.com) out there that are fully dedicated to preparing folks for coding interviews and provides the opportunity to also practice with others. 81 | 82 | For example, these are Meetup groups in the NYC area that focus on interview prep. 83 | 84 | ![Meetup Interview Groups in NYC](https://i.imgur.com/mA4TeXW.png) 85 | 86 | And these are a few Meetup groups in SF that focus just on interview prep as well. 87 | 88 | ![Meetup Interview Groups in SF](https://i.imgur.com/DmLncmU.png) 89 | 90 | ### Outco 91 | 92 | [Outco](https://outco.io/) is essentially a coding bootcamp but for getting a job. So it's a job bootcamp for engineers. You spend a full month dedicated to learning how to master the data structures/algorithms tech interview, negotiate your salary, and apply to jobs. 93 | 94 | It looks very promising but keep in mind that the program does cost $4.5K if you go with the upfront tuition option (as of 2017). Another option is paying $0 upfront but then 8% of your starting salary. 95 | 96 | ![Outco](https://i.imgur.com/GDy7nk4.png) 97 | 98 | ## Websites 99 | 100 | ### CodeFights 101 | 102 | [CodeFights](https://codefights.com/) allows you to practice for interviews using real questions on need-to-know topics and then gives you the opportunity to get matched with a hiring partner when you're ready for a new job. 103 | 104 | ![CodeFights](https://i.imgur.com/eKveVjN.png) 105 | 106 | ### Coderbyte 107 | 108 | [Coderbyte](http://coderbyte.com) is a web application that helps you practice your programming skills, prepare for coding bootcamps, and prepare for job interviews with our collection of interview questions, videos, and solutions. 109 | 110 | ![Coderbyte](https://i.imgur.com/1MMHhBd.png) 111 | 112 | ### Codewars 113 | 114 | [Codewars](https://www.codewars.com/) is where developers can achieve code mastery through kata challenges. 115 | 116 | ![Codewars](https://i.imgur.com/PdfjpNa.png) 117 | 118 | ### Exercism 119 | 120 | [Exercism](http://www.exercism.io/) allows you to download and solve practice problems in over 30 different languages. 121 | 122 | ![Exercism](https://i.imgur.com/D4arzaf.png) 123 | 124 | ### HackerRank 125 | 126 | [HackerRank](https://www.hackerrank.com) is a technology company that focuses on competitive programming challenges for both consumers and businesses, where developers compete by trying to program according to provided specifications. 127 | 128 | ![HackerRank](https://i.imgur.com/wawyKG9.png) 129 | 130 | ### Interview Cake 131 | 132 | [Interview Cake](http://www.interviewcake.com) helps you prep for interviews to land offers at companies like Google and Facebook by offering free practice programming interview questions. 133 | 134 | ![Interview Cake](https://i.imgur.com/1URJ3sh.png) 135 | 136 | ### InterviewBit 137 | 138 | [InterviewBit](http://www.interviewbit.coms) offers the abilit to learn and practice on almost all coding interview questions asked historically and get referred to the best tech companies. 139 | 140 | ![InterviewBit](https://i.imgur.com/8CG5cHK.png) 141 | 142 | ### Interviewing.io 143 | 144 | [Interviewing.io](http://interviewing.io) is a platform where engineers practice technical interviewing anonymously. If things go well, you can unlock the ability to participate in real, still anonymous, interviews with top companies like Twitch, Lyft and more. 145 | 146 | ![Interviewing.io](https://i.imgur.com/oFdM03O.png) 147 | 148 | ### LeetCode 149 | 150 | [LeetCode](https://leetcode.com) is a platform to help you enhance your skills, expand your knowledge and prepare for technical interviews. 151 | 152 | ![LeetCode](https://i.imgur.com/UFncE2a.png) 153 | 154 | ### Pramp 155 | 156 | With [Pramp](https://www.pramp.com/#/), you can practice coding interviews live for free. 157 | 158 | ![Pramp](https://i.imgur.com/6nIKydR.png) 159 | 160 | ## Further Resources 161 | 162 | - [Udacity Career Resource Center](https://career-resource-center.udacity.com/) 163 | -------------------------------------------------------------------------------- /docs/01-prepare/product-manager.md: -------------------------------------------------------------------------------- 1 | # Product Manager? {docsify-ignore} 2 | 3 | > Here are a few resources for those trying to prepare for a PM interview. 4 | 5 | - [Books](#books) 6 | - [Cracking the PM Interview](#cracking-the-pm-interview) 7 | - [Intercom on Product Management](#intercom-on-product-management) 8 | - [Email Newsletter](#email-newsletter) 9 | - [Product Management Exercises](#product-management-exercises) 10 | - [GitHub Repos](#github-repos) 11 | - [Open Product Management](#open-product-management) 12 | - [Websites](#websites) 13 | - [The PM Interview](#the-pm-interview) 14 | 15 | ## Books 16 | 17 | ### Cracking the PM Interview 18 | 19 | [Cracking the PM Interview](http://a.co/9VIoAj2) is a comprehensive book about landing a product management role in a startup or bigger tech company written by the famous [Gayle Laakmann McDowell](http://www.gayle.com/) who also wrote [Cracking the Coding Interview](http://a.co/9VsLUXA). 20 | 21 | ![Cracking the PM Interview](https://ebook4expert.com/wp-content/uploads/2016/11/Cracking-the-PM-Interview.jpg) 22 | 23 | ### Intercom on Product Management 24 | 25 | [Intercom on Product Management](https://www.intercom.com/books/product-management) is a collection of lessons that offers Intercom's guidance on the tough decisions you will face as a product manager. 26 | 27 | ![Intercom on Product Management](https://i.imgur.com/Te9cRSm.png) 28 | 29 | ## Email Newsletter 30 | 31 | Do you work best my getting a question in your inbox every week? Try out these newsletters! 32 | 33 | ### Product Management Exercises 34 | 35 | https://productmanagementexercises.com/ 36 | 37 | ## GitHub Repos 38 | 39 | ### Open Product Management 40 | 41 | [Open Product Management](https://github.com/tron1991/open-product-management) is a curated list of product management advice from frameworks, interviews, experts, resources, books, products, career preps, and much more. 42 | 43 | ![Open Product Management](https://raw.githubusercontent.com/tron1991/open-product-management/master/logo.png) 44 | 45 | ## Websites 46 | 47 | ### The PM Interview 48 | 49 | [The PM Interview](http://thepminterview.com/) allows you to practice typical PM questions online with a timer. 50 | 51 | ![The PM Interview](https://i.imgur.com/SqImpjt.png) 52 | -------------------------------------------------------------------------------- /docs/02-search/README.md: -------------------------------------------------------------------------------- 1 | # Step 2 - Search {docsify-ignore} 2 | 3 | > Searching for the ideal job position is tedious but here are a few resources to help you get started. 4 | 5 | 6 | 7 | - [Job Alerts](#job-alerts) 8 | - [Glassdoor](#glassdoor) 9 | - [LinkedIn](#linkedin) 10 | - [Job Boards](#job-boards) 11 | - [Job Tracking](#job-tracking) 12 | - [Airtable](#airtable) 13 | - [Huntr](#huntr) 14 | - [Indeed](#indeed) 15 | - [JobHero](#jobhero) 16 | - [Trello](#trello) 17 | 18 | 19 | 20 | ## Job Alerts 21 | 22 | I personally enjoyed using LinkedIn & Glassdoor since you can setup customized job alerts. 23 | 24 | ### Glassdoor 25 | 26 | ![Glassdoor Job Alerts](https://www.glassdoor.com/app/static/img/home/value-prop/email.tab.EN.png?v=d39b98end) 27 | 28 | ### LinkedIn 29 | 30 | ![LinkedIn Job Alerts](https://i.imgur.com/35X4Xoy.png) 31 | 32 | ## Job Boards 33 | 34 | Here are some websites you can use when looking for open positions. 35 | 36 | > Emoji Key (in progress) 37 | 38 | - design focused roles 🎨 39 | - job board for women 🚺️ 40 | - VC firms hiring pool 💸️ 41 | - targeted for current students or recent grads 🎓 42 | 43 | --- 44 | 45 | - [Angel.co Jobs](https://angel.co/jobs) 46 | - [BainCapital Ventures](http://jobs.baincapitalventures.com/) 💸️ 47 | - [Behance Jobs](https://www.behance.net/joblist) 🎨 48 | - [BetaList Jobs](https://betalist.com/jobs) 49 | - [Coding Internships](https://codinginternships.com/) 🎓 50 | - [CrunchBoard](http://www.crunchboard.com/) 51 | - [DesignerJobs](https://www.designerjobs.co/) 🎨 52 | - [Dev.to Listings](https://dev.to/listings) 53 | - [Digital.NYC](http://www.digital.nyc/jobs) 54 | - [DiversifyTech.co](https://www.diversifytech.co/job-board/) 55 | - [Dribbble Jobs](https://dribbble.com/jobs) 🎨 56 | - [GarysGuide](http://www.garysguide.com/jobs) 57 | - [GitHub Jobs](https://jobs.github.com/positions) 58 | - [Glassdoor Jobs](https://www.glassdoor.com/index.htm) 59 | - [Hiring Without Whiteboards - GitHub Repo](https://github.com/poteto/hiring-without-whiteboards) 60 | - [Indeed](https://www.indeed.com/) 61 | - [Landing.jobs](https://landing.jobs/) 62 | - [LinkedIn Jobs](https://www.linkedin.com/jobs) 63 | - [Mashable Job Board](http://jobs.mashable.com/jobs/search/results) 64 | - [MLH Career Lab](https://careerlab.mlh.io/) 🎓 65 | - [Outreachy](https://www.gnome.org/outreachy/) 66 | - [PandaJobs](http://panda.jobs/) 67 | - [PowerToFly](https://powertofly.com/jobs/) 68 | - [ProductHire](https://producthire.co/) 69 | - [Sequoia](https://www.sequoiacap.com/jobs) 💸️ 70 | - [SimplyHired](http://www.simplyhired.com/local-jobs/new-york-ny) 71 | - [Slack at Work](https://slackatwork.com/) 72 | - [StackOverflow Jobs](http://stackoverflow.com/jobs) 73 | - [SudoHoot Jobs](http://jobs.sudohoot.com/) 74 | - [Switch](http://www.switchapp.com/) 75 | - [The Muse](https://www.themuse.com/) 76 | - [Triblebyte](https://triplebyte.com) ️ 77 | - [We Work Remotely](https://weworkremotely.com/) 78 | - [Women Who Code Jobs](https://www.womenwhocode.com/jobs) 🚺️ 79 | - [YCombinator Jobs](https://news.ycombinator.com/jobs) 💸️ 80 | - [ZipRecruiter](https://www.ziprecruiter.com/) 81 | 82 | ## Job Tracking 83 | 84 | Keep track of all the jobs you apply to using a platform like the ones below. 85 | 86 | Airtable is my favorite option. 87 | 88 | ### Airtable 89 | 90 | Instead of going through the hassle of using Excel, I would recommending trying out [Airtable](http://airtable.com) instead which supports a Kanban like board and has a better user experience than Excel. 91 | 92 | ![Airtable - 2017](https://i.imgur.com/JNN772I.png?1) 93 | 94 | ### Huntr 95 | 96 | [Huntr](http://huntr.co/) keeps track of every detail about your job applications - notes, dates, tasks, job descriptions, salaries, locations, company data and more. 97 | 98 | ![Huntr](https://huntr.co/images/jumbo_header_board_2x.png) 99 | 100 | ### Indeed 101 | 102 | [Indeed's Chrome Extension](https://chrome.indeed.com/) is a free service that helps you manage the status of your job applications on Indeed and other sites across the web. 103 | 104 | It knows when to save your jobs, the jobs you applied to and even jobs that you interviewed and got hired for within one location. 105 | 106 | ### JobHero 107 | 108 | The [JobHero](https://gojobhero.com/app/) dashboard allows you to 109 | 110 | - save jobs from across the web and track your application progress, 111 | - set reminders for follow ups, deadlines, and due dates and 112 | - upload and tag documents, notes, and contact information. 113 | 114 | ![JobHero - 2017](https://i.imgur.com/1GUUZfP.png) 115 | 116 | ### Trello 117 | 118 | [Trello](https://trello.com/) keeps track of everything, from the big picture to the minute details. 119 | 120 | ![Trello](https://i.imgur.com/U3IMAlX.png) 121 | -------------------------------------------------------------------------------- /docs/02-search/research.md: -------------------------------------------------------------------------------- 1 | # Company Research {docsify-ignore} 2 | 3 | > Once you've decided on which companies you want to interview with, make sure to do your research to ensure yourself that it'd be a good fit. 4 | > 5 | > This is also a necessary step to take right before the actual interview itself. 6 | 7 | ## Google 8 | 9 | - Are they in the news? 10 | - What's the latest? 11 | - Any red flags? 12 | 13 | ## Company Website 14 | 15 | - Familiarize yourself with their tech stack. 16 | - Check out their company culture page. 17 | - Read their “About Us” page. 18 | - Familiarize yourself with their team page. 19 | - What are they wearing? Casual, business casual or formal? 20 | 21 | ## LinkedIn 22 | 23 | - Research existing people at these companies that have your desired role and check out their personal websites, GitHub, and LinkedIn profiles to get a feel of what their background is. 24 | - By checking the company's page on LinkedIn, you might find out you already know someone relevant that can provide a warm intro. 25 | - Check out the people who you will be interviewing with. 26 | - Look at the extra information posted on the company page. 27 | - Follow the company if you're so inclined. 28 | 29 | ## Glassdoor­ 30 | 31 | - Skim over company reviews. 32 | - Note if anything extremely positive or negative comes up consistently. 33 | - Read through the relevant interview experiences. 34 | - It's easy to filter by specific position and get a lot of potential interview questions the company will actually ask you. 35 | 36 | ## Crunchbase 37 | 38 | - How many rounds of funding has the company had so far? From who? 39 | - How many people work there? 40 | - Who's part of the leadership team (CEO, CTO, etc.)? 41 | - Do they have a good reputation? 42 | -------------------------------------------------------------------------------- /docs/03-apply/README.md: -------------------------------------------------------------------------------- 1 | # Step 3 - Apply {docsify-ignore} 2 | 3 | > It's time to apply for the position! 4 | > 5 | > Getting a warm intro first and then submitting a well crafted resume is essential in getting a call back after applying. 6 | 7 | ## Warm Intros 8 | 9 | Use your connections to find someone you may know at the company (1st to 3rd connections on LinkedIn) to get a warm intro whenever possible. 10 | 11 | In my experience, warm intros are by far the most effective way to get you an initial interview. 12 | 13 | If you put yourself in the recruiter's shoes, you'll quickly realize that it would be way nicer to have referrals sent to you instead of looking over hundreds (or thousands) of resumes. 14 | 15 | An easy way of figuring out if you know someone at the company is via LinkedIn and using their filtering options. 16 | 17 | As an example, here I'm trying to find a **1st connection** on LinkedIn that **lives in the US** and works for **Google**. 18 | 19 | Now I have a better idea of the folks I can reach out to if I ever want to try and get a job at Google. 20 | 21 | ![LinkedIn Filtering](https://i.imgur.com/dRLlTGY.png) 22 | 23 | ## Resume 24 | 25 | Consider your resume a living document that has continuous updates, tweaks, and versions. If your job search has been a lengthy one with many rejections, take time to evaluate your resume and see if it is best capturing you as a worthy candidate. Begin A/B testing resumes with different companies, to see if there's one version with a better response. This testing can work great when applying on [job boards](02-search/README.md). 26 | 27 | Always take time to edit and proofread your resume. When you've polished it to an approving status, have another person read it for feedback. Additionally, if you're working with a recruiter directly, they would be an excellent person to ask for feedback on how your resume stands. 28 | 29 | Lastly, print out your resume to see if the formatting is appropriate on both physically and digitally. There have been times I worked on an awesome resume, only to find my font prints out very small. 30 | 31 | ### Creddle 32 | 33 | I would recommend using an online platform like [Creddle](http://creddle.io/) to avoid the tedious process of making a resume from scratch. 34 | 35 | ![Creddle](https://i.imgur.com/8f18oDM.png) 36 | 37 | ### Canva 38 | 39 | [Canva](https://www.canva.com/create/resumes/) also offers a free way to create a compelling resume design that organizes all your credentials in an impressive run-through. 40 | 41 | ![Canva](https://i.imgur.com/HaiOjv1.png) 42 | -------------------------------------------------------------------------------- /docs/03-apply/cover-letters/README.md: -------------------------------------------------------------------------------- 1 | # Cover Letter {docsify-ignore} 2 | 3 | > Cover letters can be quite annoying since many recruiters tend to not read them but for the companies that **require** one, creating a relevant cover letter is vital could lead to a much better response. 4 | > 5 | > Also, cover letters can serve as ideal cold emails if you're trying to reach out to a recruiter you met in person. 6 | 7 | ## Template - Existing Connection 8 | 9 | It's always more ideal to reach out to recruiters where there's some kind of mutual connection. 10 | 11 | ```text 12 | Hi [recruiter you met], 13 | 14 | I’m [your name]. It was a real pleasure chatting with you at the rooftop mixer at [company name] last weekend. I found your contact info on LinkedIn, and it turns out we both know [mutual friend], a friend of mine from working at [past company] last summer. 15 | 16 | I am a huge fan of the [company] app and I especially love the [insert aspect of the app] and the culture there. I worked on similar projects before which you can check out here: [insert portfolio link]. Based off my previous experience, [talk about how previous experience relates to this role]. 17 | 18 | I've actually created this [project description] that uses [company tech stack] which ideally can showcase my relevant skill set. 19 | 20 | Would you be interested in meeting up to chat further? I am currently located in San Francisco, where your company is headquartered. 21 | 22 | Best, 23 | 24 | [your name] 25 | [contact info] 26 | ``` 27 | 28 | ## Template - No Connection 29 | 30 | If you have no connection with the company, it's up to you to present your best self and how you can best benefit the company. 31 | 32 | ```text 33 | Dear [company], 34 | 35 | This letter is to express my interest in your posting on [job board] for [position]. 36 | 37 | After looking through what [company] wants out of this position, I am confident I'm a great match. 38 | 39 | [Elaborate on academic qualifications and previous experience and how it ties to job requirements] 40 | 41 | I've actually created this [project description] that uses [company tech stack] which can more ideally showcase my relevant skill set. 42 | 43 | Attached is a copy of my resume that details my projects and experience in [position relevance]. 44 | 45 | Thanks for your time and I look forward to hearing back. 46 | 47 | Best, 48 | 49 | [your name] 50 | [contact info] 51 | ``` 52 | 53 | ## Tips 54 | 55 | - Don't regurgitate your resume 56 | - Mention a specific thing that appeals to you about working for that specific company 57 | - The first paragraph should directly state what position you're applying for 58 | - If you know someone at the company, now would be the time to mention them. 59 | - Share an idea you have that you think would be valuable for the company or even try to provide some help/criticism (I noticed a bug on your website...) 60 | - Make sure it's less than one page. 61 | - Share experiences that demonstrate how prepared you are for the job. 62 | - Provide relevant contact info (GitHub, LinkedIn, phone #, email, etc.) 63 | -------------------------------------------------------------------------------- /docs/03-apply/online-presence.md: -------------------------------------------------------------------------------- 1 | # Online Presence 2 | 3 | > Some companies ask for links to your projects or online profiles to verify you have relevant experience and to check whether or not you are active in your field. 4 | > 5 | > This means you should invest at least some time in [LinkedIn](http://linkedin.com), [GitHub](http://github.com), and other sites you feel are relevant to your skillset. 6 | 7 | ## Personal Website 8 | 9 | http://fvcproductions.com 10 | 11 | ## GitHub 12 | 13 | http://github.com/fvcproductions 14 | 15 | ## Behance 16 | 17 | http://behance.net/fvcproductions 18 | 19 | ## Speaker Deck 20 | 21 | http://speakerdeck.com/fvcproductions 22 | 23 | ## SlideShare 24 | 25 | http://slideshare.net/fvcproductions 26 | 27 | ## Scribd 28 | 29 | http://scribd.com/fvcproductions 30 | 31 | ## LinkedIn 32 | 33 | http://linkedin.com/in/fvcproductions 34 | 35 | ## Gravatar 36 | 37 | http://gravatar.com/fvcproductions 38 | -------------------------------------------------------------------------------- /docs/03-apply/replying.md: -------------------------------------------------------------------------------- 1 | # Replying to Recruiters 2 | 3 | > Okay, so you got a recruiter to reach out to you. That's great! 4 | > 5 | > Now you got to make sure to reply back to them in a timely manner. 6 | 7 | ## Scheduling 8 | 9 | One of the first questions you'll get from them of course is when you're available to talk/video chat/whatever. 10 | 11 | I personally use [Calendly](http://calendly.com) for this process and it works wonders. 12 | 13 | I'd recommend trying it out yourself since it's free. 14 | 15 | ![Calendly](https://i.imgur.com/Dht9Vda.png) 16 | 17 | ## Email Template 18 | 19 | Here's a reply template you can use to follow up. 20 | 21 | ```markdown 22 | Hi [Name of recruiter] 23 | 24 | Thanks for reaching out - I'm very excited to learn more about [Company Name] 25 | 26 | So in terms of setting up a time to chat, I actually have a Calendly where you're more than welcome to see when I'll be available this week or next. 27 | 28 | [Calendly link] 29 | 30 | Looking forward to hearing back! 31 | 32 | [Email Signature] 33 | ``` 34 | 35 | ## Has a recruiter ghosted you? 36 | 37 | It happens pretty often, unfortunately. A conversation begins with a recruiter and it sounds very promising, but then there's radio silence! 38 | 39 | Always keep in mind the value of what you're aiming to achieve out of speaking with a company. Is it a job? Is it for interview practice? Is it to get to know the company? Everyone has different needs, so be sure you understand yours. 40 | I recommend sending polite emails to recruiters to check up on the lead. 41 | - 5 days after last communication -- this helps to keep the process moving. One business week has passed. 42 | - > Hello Recruiter, Just following up on [role] at [Company name]. Are there any updates regarding the next steps? 43 | - 10 days after last communication -- Okay, two business weeks have passed, so hopefully, they respond to you now. 44 | - > Hello Recruiter, Checking back in to see if you have any updates on [role] at [Company name]. I'm still very interested in applying. Please let me know if any materials are needed to help with the process! 45 | - 15 days after last communication -- this may be a stale lead. 46 | - > Hello Recruiter, How are you doing today? It's been a few weeks since we last spoke, but I'm curious about if there are any updates with [role] at [Company name]. If this position has been filled, perhaps we can chat about other opportunities that have come down the pipeline! 47 | - 30 days after last communication -- this lead is done, and it's probably better to consider looking to other options. 48 | - > Hello Recruiter, We spoke last month about some promising openings as a [role]. Just checking in to see what new leads you have. 49 | - Alternatively, a lot of tech recruiting agencies have many employees working, so you could also try doing some LinkedIn sleuthing to find a coworker who you can contact for any new leads. 50 | -------------------------------------------------------------------------------- /docs/03-apply/skills.md: -------------------------------------------------------------------------------- 1 | # Listing Skills 2 | 3 | > Ensuring whoever looks through your profile has a good idea of what you have experience in is pretty important. 4 | 5 | ## LinkedIn - Featured Skills & Endorsements 6 | 7 | If you haven't already, add your relevant skills to your LinkedIn profile as well under the **Featured Skills & Endorsements** section and try and get endorsements from your peers. 8 | 9 | ![LinkedIn - Featured Skills & Endorsements](https://i.imgur.com/PsFw37t.png) 10 | 11 | ## Reference List 12 | 13 | Some of the more _vintage_ application platforms out there still require you to list out your skills. 14 | 15 | Unfortunately, this may actually be important since some platforms use this as a basis to decide/filter out whether an applicant knows the right technologies for the role. 16 | 17 | I would recommend keeping a list of skills in your note taking app for quick reference like this. 18 | 19 | ```text 20 | JavaScript 21 | Web Development 22 | Social Media 23 | Java 24 | C# 25 | AngularJS 26 | Public Speaking 27 | Node.js 28 | Python 29 | Teamwork 30 | MongoDB 31 | HTML5/CSS3 32 | OS X 33 | Sublime Text 34 | User Interface Design 35 | Project Management 36 | Express.js 37 | Leadership 38 | Creative Writing 39 | Social Media Marketing 40 | C 41 | Git 42 | jQuery 43 | Blogging 44 | iWork 45 | Markdown 46 | Bootstrap 47 | Icon Design 48 | Gulp 49 | Unity 50 | Mockups 51 | Rapid Prototyping 52 | Final Cut Pro X 53 | iBooks Author 54 | Cheerio 55 | Augmented Reality 56 | Presentation Design 57 | Content Management 58 | A/B Testing 59 | SEO 60 | Keynote 61 | Web Design 62 | SASS 63 | Wireframing 64 | Product Design 65 | Content Strategy 66 | Product Marketing 67 | Agile Methodologies 68 | Branding & Identity 69 | Product Management 70 | ``` 71 | -------------------------------------------------------------------------------- /docs/04-interview/README.md: -------------------------------------------------------------------------------- 1 | # 04 - The Interview {docsify-ignore} 2 | 3 | > So a recruiter reached out and wants to interview. Congrats! 🎉 4 | > 5 | > Here are some aspects I discuss in length when it comes to interviews... 6 | 7 | - preparing ahead of time for the interview 8 | - introducing yourself in an intriguing way 9 | - being prepared to answer the behavioral questions the interviewer may ask 10 | - **always always** asking questions 11 | - following up 12 | -------------------------------------------------------------------------------- /docs/04-interview/answering.md: -------------------------------------------------------------------------------- 1 | # Answering Questions 2 | 3 | > It's useful to keep some kind of question bank handy since a lot of interviewers tend to ask similar questions. 4 | 5 | Here are a few to think of answers to as you prepare for the interviewee or recruiter to ask you behavioral type questions. 6 | 7 | - Tell us about a time you built something awesome in code. How did you choose it? Why did you enjoy it? 8 | - Is there a particular technology or industry you're currently interested in? How come? Where do you see it heading in the future? 9 | - Name some of your favorite projects. 10 | - When you're not coding, what do you like to do? 11 | - What impact do you want to have on the world and why? 12 | - What are your key interests? 13 | - Where are your preferred locations to work? 14 | - In your past roles, what technologies did you work with? 15 | - What are the classes in computer science you've taken so far? 16 | - When did you first get interested in learning to code? Why? 17 | - Describe something you do for your community or the benefit of others. What inspires you to do this? 18 | - Provide some links to apps or websites you've created. 19 | - Provide a link to a piece of code that you wrote that you are particularly proud of. 20 | - What are your long-term plans? 21 | - Tell us about a challenging project that you worked on or a challenge in your life that you have overcome. 22 | - Anything else you would like to share? 23 | -------------------------------------------------------------------------------- /docs/04-interview/asking.md: -------------------------------------------------------------------------------- 1 | # Asking Questions 2 | 3 | > At the end of the intro calls, a recruiter will generally ask if you have any questions. 4 | > 5 | > If you have 0 questions, this looks TERRIBLE so try to ask at least 3. 6 | > 7 | > Having a question bank is useful if you want a reference of questions you can ask your interviewer. 8 | > 9 | > Asking at least one question from each aspect of the company is ideal so you can get a more holistic view. 10 | > 11 | > Here are a few sample questions you can ask your interviewer. 12 | 13 | ## Position Details 14 | 15 | - Are there metrics or goals set up for me the first week that I would be striving towards? 16 | - How do you know what to work on each day? 17 | - How much travel is expected? 18 | - How would you describe a typical day and week in this position? 19 | - How would you describe the responsibilities of the position? 20 | - If I were successful there, what would I have accomplished in 6 months? 21 | - Is this a new position? If not, what did the previous employee go on to do? 22 | - Let's say I'm doing really terribly or really great the first week. How am I going to be getting feedback as to whether I'm performing great or terribly? 23 | - What is the typical work week in terms of hours? Do a lot of folks work overtime? 24 | - What kind of feedback can I get during my first few months, and who will I be getting it from? 25 | - What's the most important thing I should accomplish in the first ninety days? 26 | - Who does this position report to? 27 | 28 | ### Interviewer - General 29 | 30 | > Depending on your interviewer, you can ask different kinds of questions. 31 | > 32 | > These questions can be asked of anyone on the team. 33 | 34 | - How did you get your job? 35 | - How long have you been with the company? 36 | - How often have you moved teams? What made you join the team you’re on right now? If you wanted to move teams, what would need to happen? 37 | - If you had an idea for something you thought would be great to work on, what would it take to make it happen? What is the process from having an idea to getting it out the door? 38 | - What are the biggest rewards of the job and working for this company? 39 | - What has your past experience been like working with [position applying for]? 40 | - What is it like working there? 41 | - What is one thing you love about working at [company] and one thing that really frustrates you? 42 | - What is something you wish were different about your job? 43 | - What is the biggest challenge facing [the company] right now? What worries you about this issue? And how is [the company] working on solving it? 44 | - What is the most fulfilling/exciting/technically complex project that you’ve worked on here so far? 45 | - What’s the last thing you shipped? What’s the last thing you launched that real people are now using? 46 | - When you were last interviewing, what were some of your other options, and what made you choose this company? 47 | 48 | ### Interviewer - Developer 49 | 50 | > These are tailored for developers on the team. 51 | 52 | - Are there stand-ups/sprints? 53 | - Did any of your senior engineers start out as junior engineers here? 54 | - Do senior engineers pair with junior engineers in the ramp-up process? 55 | - Do you tend to roll your own solutions more often or rely on third party tools? What’s the rationale in a specific case? 56 | - How do you prevent meetings from overwhelming an engineer’s schedule? 57 | - How does the code review process work? 58 | - How does the engineering culture differ from the overall company culture? 59 | - How does the team keep up to date with the latest and greatest technologies? 60 | - How often do you add new tools to the mix? 61 | - Technical capabilities aside, what soft skills would make someone successful in this role? 62 | - What are some of the internal tools used in the company and what role do they play? 63 | - What did your day look like yesterday? Was that pretty typical? If not, what was different about it? 64 | - What is the most costly technical decision made early on that the company is living with now? 65 | - What is the rationale for/story behind this specific stack? 66 | - What is used for version control? What tooling do you use for revision control? 67 | - What is your stack? 68 | - What kind of test coverage do you have? 69 | - What portion of your time is spent working on new stuff rather than iterating on existing stuff? 70 | - What's the overall tech stack I'd be working with? 71 | - What’s been the worst technical screw up that’s happened in the recent past? How did you guys deal with it? What changes were implemented afterwards to make sure it didn’t happen again? 72 | 73 | ### Interviewer - Engineering Manager 74 | 75 | > These questions are tailored for engineers managers on the team. 76 | 77 | - Do you do annual salary increases? 78 | - Do you do formal performance reviews? 79 | - Do you do regular team retrospectives? 80 | - Do you rank employees against one another? 81 | - How did you become a manager? 82 | - How do you measure individual performance? 83 | - How do your engineers know what to work on each day? 84 | - How long does the average engineer stay at the company? 85 | - What is your team’s biggest challenge right now 86 | - When was the last time you wrote code? 87 | - Why have the last few engineers left? 88 | 89 | ## Culture 90 | 91 | > Getting a vibe for the work environment. 92 | 93 | - Does diversity play a part in company culture? What kind of diversity programs are there at the company? How is diversity represented within the team or company? 94 | - How often do meetings, talks, or other events take place at lunch time? If you had to equate the lunch room into a high school cafeteria, what groups eat together? 95 | - If I had an idea for something I thought would be great to work on, would I be able to present it? 96 | - If you had an idea for something you thought would be great to work on, what would it take to make it happen? What is the process from having an idea to getting it out the door? 97 | - What is the company's management style? How do you prevent micro-management amongst managers and developers or designers? 98 | - What types of support would I receive as a new hire? 99 | - When’s the last time you interacted with a founder? What was it regarding? Generally how involved are the founders in the day-to-day? 100 | - Are there times of the month, quarter, or year when the team is most busy? 101 | - Are there weekly sprints or stand up meetings? 102 | - Can you talk a bit about communication within the team? Across teams? 103 | - Does anyone work remotely a lot - how distributed is the team? 104 | - How does this team plan projects and create deadline estimates? 105 | - How many people work in this office/department? 106 | - How often are meetings and how long? 107 | - How responsive are people to emails/Slack over the weekends and after 6pm? 108 | - What do you think contributes most to your team's camaraderie? 109 | - What was the most fun you’ve had at a team outing? 110 | 111 | ## Company 112 | 113 | > Getting more insight into logistical details of the company itself. 114 | 115 | - How do employees keep up to date with latest tech besides online training? Are there conferences - events - etc? 116 | - How do individual employees contribute to the creativity and innovation at [company]? 117 | - How does management deliver negative feedback to employees? 118 | - How has the company changed over the last few years? 119 | - How many people work in this office/department? 120 | - How would you describe this company's values? 121 | - What are the company's plans for growth and development? 122 | - What is the biggest challenge facing [the company] right now? 123 | - When’s the last time a founder or manager encouraged someone to go try something entirely new (whether it fit in well with the current core product or not)? 124 | - Who are the other major players in this space? What do we have that they don’t? 125 | - Who are your target consumers? 126 | - Who sets deadlines and what happens when people fail to meet them? 127 | 128 | ## Wrap Up 129 | 130 | > Understanding next steps is vital. 131 | 132 | - So now that I've exhausted my questions here, could you give me an overview of what the next steps in the process are or a time line for getting back to me? 133 | 134 | --- 135 | 136 | ## Other Resources 137 | 138 | - [A developer’s guide to interviewing](https://medium.freecodecamp.com/how-to-interview-as-a-developer-candidate-b666734f12dd) 139 | - [Culture Queries: questions to ask during an interview customized by your key values](https://www.keyvalues.com/culture-queries) 140 | - [How to interview your interviewers](https://medium.freecodecamp.org/how-to-interview-your-interviewers-f8f65ac57b80) 141 | -------------------------------------------------------------------------------- /docs/04-interview/checklist.md: -------------------------------------------------------------------------------- 1 | # Interview Checklist {docsify-ignore} 2 | 3 | > Your on-site interview has been scheduled. 4 | > 5 | > So what's the plan? 🤔️ 6 | 7 | ## Day Before 8 | 9 | - Review your resume. 10 | - Prepare and write down questions to ask the company. 11 | - I'd recommend having some kind of structure to how you do this since you may end up interviewing with a crap ton of companies. 12 | 13 | > For On Site Interviews 14 | 15 | - Check to make sure you're ready to go in terms of transportation and arriving on time. 16 | - Pick a decent outfit based off what you've learned on company culture. 17 | - Business casual is usually the safe option here. 18 | - Get some damn sleep. No one wants to interview a zombie. 19 | 20 | ## Day Of 21 | 22 | - Eat some food beforehand, you don't want your interviewers to hear your tummy growling. 23 | - Call someone you like a lot and talk to them so you're not as nervous beforehand and you remember what it's like to communicate with another human. 24 | - Pop a breath mint in. 25 | - Put your cell on "Do Not Disturb" mode. 26 | - Ask some damn good and relevant questions. 27 | - If you're that one person who says they don't have any questions, that's a huge turn-off to recruiters. 28 | - Eye contact and body language are important. Present yourself as open and confident. 29 | - No slouching. 30 | - Ask when you should expect to hear back. 31 | 32 | ## Day After 33 | 34 | - Send a thank you email to your recruiter and interviewers if possible. 35 | 36 | ## A Few Days After 37 | 38 | - Follow up if you haven't heard back. 39 | - The day of the interview, you should have asked when you should expect to hear back so if you haven't heard back from the recruiter, make sure to send a friendly email asking for an update. 40 | -------------------------------------------------------------------------------- /docs/04-interview/follow-up.md: -------------------------------------------------------------------------------- 1 | ## Following Up 2 | 3 | > It's good practice to send a quick follow-up email to your interviewer afterwards. 4 | > 5 | > It's not absolutely necessary of course but it does create a positive impression. 6 | 7 | ```text 8 | Dear [interviewer], 9 | 10 | It was great meeting you today and I appreciate you taking the time to interview me. 11 | 12 | I really enjoyed learning more about (insert what new tidbit you learned about the company). This only solidified my interest in [company]. 13 | 14 | I look forward to hearing back! 15 | 16 | Best, 17 | [email signature] 18 | ``` 19 | 20 | ## Did the company ghost you? 21 | 22 | Sometimes companies will show promising interest to you through any step of their hiring process, and then completely stop responding. It can be frustrating, especially for early-career developers who are craving a lot of feedback. The following is a guideline of how to check in with a company if it's been a bit since you've heard from them. 23 | 24 | Perhaps you have the email of the hiring manager or someone in human resources. You should reach out to them with the following guidelines: 25 | - 5 days after the last interview -- this helps to keep the process moving. One business week has passed. 26 | - > Hello [Name], Just following up on [role] at [Company name]. Are there any updates regarding the next steps? 27 | - 10 days after the last interview -- Okay, two business weeks have passed, so hopefully, they respond to you now. 28 | - > Hello [Name], Checking back in to see if you have any updates on [role] at [Company name]. My last interview with the company was on [date], and I was told I'd hear a response soon. [Restate your interest in the role]. I look forward to hearing back with updates. 29 | - 15 days after the last interview -- this may be a stale lead. 30 | - > Hello [Name], How are you doing today? It's been a few weeks since we last spoke, but I'm curious about if there are any updates with [role] at [Company name]. If this position has been filled, perhaps we can chat about other opportunities at [Company Name]. 31 | - 30 days after the last interview or line of communication -- this lead is done, and it's probably better to consider looking to other options. 32 | -------------------------------------------------------------------------------- /docs/04-interview/intros.md: -------------------------------------------------------------------------------- 1 | # Introducing Yourself 2 | 3 | > Whether it's for a cover letter or meeting in-person, you should practice introducing yourself. 4 | > 5 | > Every company at some point is going to ask you that question at some point so it's ideal to have a decent answer and know it cold. 6 | 7 | A bare bones guideline to how to introduce yourself includes covering the following talking points... 8 | 9 | - Present 10 | - What are you up to now? What does your job entail? What excites you about working there? 11 | - Past 12 | - How did you get to where you are now? What did you study? Have you taught yourself anything? 13 | - Future 14 | - What are you hoping to get from this company in this role? Where do you see yourself long-term? 15 | -------------------------------------------------------------------------------- /docs/05-accept/README.md: -------------------------------------------------------------------------------- 1 | ## Step 5 - Accept 🎉 {docsify-ignore} 2 | 3 | Create a minimum salary target for every company and change accordingly based on job type. 4 | 5 | I would recommend asking for a better salary from companies you feel you could get offers for but don't necessarily want to work for. 6 | 7 | Only focus on `base salary` when considering offers. Many companies like to offer the total package number first which includes bonuses and other benefits. 8 | 9 | Realize both your salary and bonuses offered are going to go through taxes, so take that into account. 💸 10 | -------------------------------------------------------------------------------- /docs/05-accept/salary.md: -------------------------------------------------------------------------------- 1 | # Negotiating Salary 2 | 3 | These are a few sentences I took from the book, [Fearless Salary Negotiation](http://fearlesssalarynegotiation.com/), on how to respond to a recruiter who tries to ask you what your previous salary was at your last gig. 4 | 5 | > I would prefer to focus on the value I can add to this company rather than what I’m paid at my current job. 6 | > 7 | > I don’t have a specific number in mind for a desired salary, and you know better than I do what value my skill set and experience could bring to your company. 8 | > 9 | > I want this move to be a big step forward for me in terms of both responsibility and compensation. 10 | 11 | ## Fearless Salary Negotiaton 12 | 13 | To really learn how to negotiate your salary, I would read that book [Fearless Salary Negotiation](http://fearlesssalarynegotiation.com/). 14 | 15 | Here's [a blog post covering some tips from the book](http://www.kalzumeus.com/2016/06/03/kalzumeus-podcast-episode-12-salary-negotiation-with-josh-doody/) if you don't want to buy it. 16 | 17 | ![Fearless Salary Negotiation](https://s-media-cache-ak0.pinimg.com/originals/69/6a/b2/696ab2e5c457087d0528a9104f73197a.jpg) 18 | -------------------------------------------------------------------------------- /docs/_coverpage.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | # hire-me 4 | 5 | > A path to getting an awesome tech gig. 6 | 7 | [GitHub](https://github.com/fvcproductions/hire-me) 8 | [Get Started](#hire-me) 9 | 10 | ![color](#f0f0f0) 11 | -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-114.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-114.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-120.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-120.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-144.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-144.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-152.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-152.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-180.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-180.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-192.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-192.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-32.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-32.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-36.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-36.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-48.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-48.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-57.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-57.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-60.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-60.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-72.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-72.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-76.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-76.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon-96.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon-96.png -------------------------------------------------------------------------------- /docs/_images/favicons/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/FrancesCoronel/hire-me/023b434916b1e8a7fe5f373bff68ba4c0c1a7151/docs/_images/favicons/favicon.ico -------------------------------------------------------------------------------- /docs/_images/icon.svg: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /docs/_sidebar.md: -------------------------------------------------------------------------------- 1 | - [Home 🏠](/README) 2 | - [Step 1 - Prepare 📚](/01-prepare/README) 3 | - [Product Manager?](/01-prepare/product-manager) 4 | - [Step 2 - Search 🔎](/02-search/README) 5 | - [Company Research](/02-search/research) 6 | - [Step 3 - Apply 📝](/03-apply/README) 7 | - [Online Presence](/03-apply/online-presence) 8 | - [Listing Skills](/03-apply/skills) 9 | - [Cover Letter](/03-apply/cover-letters/README) 10 | - [Replying to Recruiters](/03-apply/replying) 11 | - [Step 4 - Interview 🤝](/04-interview/README) 12 | - [Interview Checklist](/04-interview/checklist) 13 | - [Introducing Yourself](/04-interview/intros) 14 | - [Answering Questions](/04-interview/answering) 15 | - [Asking Questions](/04-interview/asking) 16 | - [Following Up](/04-interview/follow-up) 17 | - [Step 5 - Accept 🎉](/05-accept/README) 18 | - [Negotiating Salary](05-accept/salary) 19 | - [Contributing](https://github.com/fvcproductions/hire-me/blob/master/CONTRIBUTING.md) 20 | -------------------------------------------------------------------------------- /docs/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | hire-me 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 82 | 83 | 84 | 85 |
One sec... 😅
86 | 87 | 102 | 106 | 107 | 108 | 109 | 110 | 111 | --------------------------------------------------------------------------------