From 141d65ce5ba1455555b71c582266553f9df3b1d5 Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Tue, 14 May 2024 13:16:47 -0600
Subject: [PATCH 01/15] Remove HOME from nav bar

---
 _includes/navigation.html | 1 -
 1 file changed, 1 deletion(-)

diff --git a/_includes/navigation.html b/_includes/navigation.html
index fd641261..678904ef 100644
--- a/_includes/navigation.html
+++ b/_includes/navigation.html
@@ -6,7 +6,6 @@
          alt="Turing School of Software and Design logo">
       </a>
     </li>
-    <li class="uppercase"><a href="/">Home</a></li>
     <li class="uppercase"><a href="/module1">Module 1</a></li>
     <li class="uppercase"><a href="/module2">Module 2</a></li>
     <li class="uppercase"><a href="/module3">Module 3</a></li>

From 00d8f92efa773d0e8fd5b1d6420e1dd10bbe7edf Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Tue, 14 May 2024 13:17:38 -0600
Subject: [PATCH 02/15] Point logo click to home page

---
 _includes/navigation.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_includes/navigation.html b/_includes/navigation.html
index 678904ef..414cf0a1 100644
--- a/_includes/navigation.html
+++ b/_includes/navigation.html
@@ -1,7 +1,7 @@
 <nav role="navigation">
   <ul class="nav-links">
     <li>
-      <a href="https://turing.edu/" class="home-logo-link">
+      <a href="https://curriculum.turing.edu/" class="home-logo-link">
         <img src="/assets/icons/TuringSchool_LogoMark_Gray.png"
          alt="Turing School of Software and Design logo">
       </a>

From e1b56c9ccdb960492023bc84ca715a3940d23d97 Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Tue, 14 May 2024 13:20:07 -0600
Subject: [PATCH 03/15] Add GRADUATES tab for grad services info

---
 _includes/navigation.html | 3 ++-
 graduates/index.md        | 7 +++++++
 2 files changed, 9 insertions(+), 1 deletion(-)
 create mode 100644 graduates/index.md

diff --git a/_includes/navigation.html b/_includes/navigation.html
index 414cf0a1..44e95f7c 100644
--- a/_includes/navigation.html
+++ b/_includes/navigation.html
@@ -6,11 +6,12 @@
          alt="Turing School of Software and Design logo">
       </a>
     </li>
+    <li class="uppercase"><a href="/calendars/calendars.html">Calendar</a></li>
     <li class="uppercase"><a href="/module1">Module 1</a></li>
     <li class="uppercase"><a href="/module2">Module 2</a></li>
     <li class="uppercase"><a href="/module3">Module 3</a></li>
     <li class="uppercase"><a href="/module4">Module 4</a></li>
-    <li class="uppercase"><a href="/calendars/calendars.html">Calendar</a></li>
+    <li class="uppercase"><a href="/graduates">Graduates</a></li>
     <li class="search-bar">
       <label for="search">
         <!-- <img class="search-icon" src="../../../../assets/icons/search.svg" alt="Search Icon" /> -->
diff --git a/graduates/index.md b/graduates/index.md
new file mode 100644
index 00000000..389fbb98
--- /dev/null
+++ b/graduates/index.md
@@ -0,0 +1,7 @@
+---
+layout: page
+title: Graduates
+subheading: Turing Graduate Services
+---
+
+

From 8da5c8de88a8a877ebb841b6be01de96f92caece Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Tue, 14 May 2024 13:41:43 -0600
Subject: [PATCH 04/15] Add job seekers resource page

---
 _includes/navigation.html                     |   2 +-
 graduates/index.md                            |   7 -
 job_seekers/index.md                          | 133 +++++++++++++
 job_seekers/resources/branding_resources.md   | 187 ++++++++++++++++++
 job_seekers/resources/civic_tech_resources.md |  36 ++++
 job_seekers/resources/consulting_resources.md |  36 ++++
 .../resources/cover_letter_resources.md       |  63 ++++++
 job_seekers/resources/edtech_resources.md     |  29 +++
 .../resources/finding_opportunities.md        | 151 ++++++++++++++
 job_seekers/resources/fintech_resources.md    |  26 +++
 .../resources/health_tech_resources.md        |  18 ++
 .../resources/interview_prep_resources.md     | 149 ++++++++++++++
 .../resources/introversion_resources.md       |  20 ++
 job_seekers/resources/negotiations.md         |  45 +++++
 .../outreach_networking_resources.md          |  66 +++++++
 job_seekers/resources/readme_resources.md     |  14 ++
 job_seekers/resources/resume_resources.md     |  91 +++++++++
 job_seekers/resources/terminal_directions.md  |  99 ++++++++++
 job_seekers/resources/veteran_resources.md    |  18 ++
 19 files changed, 1182 insertions(+), 8 deletions(-)
 delete mode 100644 graduates/index.md
 create mode 100644 job_seekers/index.md
 create mode 100644 job_seekers/resources/branding_resources.md
 create mode 100644 job_seekers/resources/civic_tech_resources.md
 create mode 100644 job_seekers/resources/consulting_resources.md
 create mode 100644 job_seekers/resources/cover_letter_resources.md
 create mode 100644 job_seekers/resources/edtech_resources.md
 create mode 100644 job_seekers/resources/finding_opportunities.md
 create mode 100644 job_seekers/resources/fintech_resources.md
 create mode 100644 job_seekers/resources/health_tech_resources.md
 create mode 100644 job_seekers/resources/interview_prep_resources.md
 create mode 100644 job_seekers/resources/introversion_resources.md
 create mode 100644 job_seekers/resources/negotiations.md
 create mode 100644 job_seekers/resources/outreach_networking_resources.md
 create mode 100644 job_seekers/resources/readme_resources.md
 create mode 100644 job_seekers/resources/resume_resources.md
 create mode 100644 job_seekers/resources/terminal_directions.md
 create mode 100644 job_seekers/resources/veteran_resources.md

diff --git a/_includes/navigation.html b/_includes/navigation.html
index 44e95f7c..c9fb8ae4 100644
--- a/_includes/navigation.html
+++ b/_includes/navigation.html
@@ -11,7 +11,7 @@
     <li class="uppercase"><a href="/module2">Module 2</a></li>
     <li class="uppercase"><a href="/module3">Module 3</a></li>
     <li class="uppercase"><a href="/module4">Module 4</a></li>
-    <li class="uppercase"><a href="/graduates">Graduates</a></li>
+    <li class="uppercase"><a href="/job_seekers">Job Seekers</a></li>
     <li class="search-bar">
       <label for="search">
         <!-- <img class="search-icon" src="../../../../assets/icons/search.svg" alt="Search Icon" /> -->
diff --git a/graduates/index.md b/graduates/index.md
deleted file mode 100644
index 389fbb98..00000000
--- a/graduates/index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: page
-title: Graduates
-subheading: Turing Graduate Services
----
-
-
diff --git a/job_seekers/index.md b/job_seekers/index.md
new file mode 100644
index 00000000..8c7d3d67
--- /dev/null
+++ b/job_seekers/index.md
@@ -0,0 +1,133 @@
+---
+layout: page
+title: Job Seekers
+subheading: Job Seeker Support for Alumni in First Job Search
+---
+
+Students decide to start their job search at different times in the program. Once you've started job searching, this is the page for you! 
+
+## Communication
+
+### Slack
+Join  the following Slack communities:
+- `#employment-round-one`: A channel for folks looking for their first job out of Turing
+- `#employment-commons`: A channel for any alumni on the job search (could be their second, third, etc. job out of Turing)
+- `#employment-salaries`: A channel for alumni to share transparency around their job hunt and offers
+
+### Events & Calendar
+The Graduate Services Events Calendar provides information for upcoming group check-ins, guest speakers, and any additional events for job seekers. 
+
+<div class="responsive-iframe-container">
+  <div class='tablet'>
+    <iframe src="https://calendar.google.com/calendar/embed?src=casimircreative.com_1ljkgo2l95s8f2p1jpi6shq678%40group.calendar.google.com&ctz=America%2FDenver&amp;mode=week" style="border-width:0" frameborder="0" scrolling="no"></iframe>
+  </div>
+  <div class='desktop'>
+    <iframe src="https://calendar.google.com/calendar/embed?src=casimircreative.com_1ljkgo2l95s8f2p1jpi6shq678%40group.calendar.google.com&ctz=America%2FDenver&amp;mode=week" style="border-width:0" frameborder="0" scrolling="no"></iframe>
+  </div>
+</div>
+
+Events may also appear in the Turing Community Calendar.
+
+<div class="responsive-iframe-container">
+  <div class='tablet'>
+    <iframe src="https://calendar.google.com/calendar/embed?showTitle=0&amp;showPrint=0&amp;showCalendars=0&amp;mode=AGENDA&amp;height=400&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=casimircreative.com_ronr9dk92ndvlhsk03kf8jd2ro%40group.calendar.google.com&amp;color=%2323164E&amp;ctz=America%2FDenver"
+      style="border-width:0" frameborder="0" scrolling="no"></iframe>
+  </div>
+  <div class='desktop'>
+    <iframe src="https://calendar.google.com/calendar/embed?showTitle=0&amp;showNav=1&amp;showDate=0&amp;showPrint=0&amp;showTabs=0&amp;showCalendars=0&amp;showTz=0&amp;mode=WEEK&amp;height=400&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=casimircreative.com_ronr9dk92ndvlhsk03kf8jd2ro%40group.calendar.google.com&amp;color=%2323164E&amp;ctz=America%2FDenver"
+      style="border-width:0" frameborder="0" scrolling="no"></iframe>
+  </div>
+</div>
+
+### Recorded Events
+Many past events have been recorded and uploaded to [this YouTube Playlist](https://www.youtube.com/playlist?list=PL1Y67f0xPzdOmktyQlnqVEIRpbTx_apNm). 
+
+
+## Job Search Support
+
+### 1:1 Support
+Schedule some career coaching time with [Tracey Monteiro](https://go.oncehub.com/TraceyMonteiro1)!
+
+### Mock Interviews
+You can grab time with an alum to prepare for FE/BE technical and behavioral interviews and live coding challenges. You can grab a slot via OnceHub [here](https://go.oncehub.com/turingmockinterviews).
+
+### Receive an offer? 
+The Turing Staff happy to help you navigate the offer and negotiations process - reach out to whoever you feel comfortable to. You can also check out [these resources on negotiations](./resources/negotiations.md).
+
+## Signed an offer?
+Please submit the two surveys below - we want to celebrate your accomplishment, and continue improving our processes!
+* [Employment Survey](https://airtable.com/apppt3xpmBOn5AwVY/shrPoZOiVZuRH9wJf)
+* [Career Development Survey](https://airtable.com/apppt3xpmBOn5AwVY/shrCZs7Nbj043sbYE)  
+
+### Sending out a bunch of applications but not hearing anything back? 
+[Check out these Applicant Tracking System Tips!](https://www.jobscan.co/applicant-tracking-systems) and get insights on your resume by scanning it through [Jobscan.co](https://www.jobscan.co)
+
+### Terminal
+Turing provides a space for professional portfolios on our website. These portfolios can be used during your job hunt - you can send out links to your profile, and Turing staff may share your profile to employers who come to us asking for candidates.  See the [Terminal Directions Page](./resources/terminal_directions.md) for more information!
+
+## Resources
+
+### Networking 
+* [Outreach & Networking Resources](./resources/outreach_networking_resources.md)
+
+### Interviewing
+* [Compilation of Lots of Interview Prep Resources](./resources/interview_prep_resources.md)
+* Recommended Reading:
+   * [Cracking the Coding Interview](https://bookshop.org/books/cracking-the-coding-interview-189-programming-questions-and-solutions/9780984782857)
+
+### Materials
+* [Branding Resources for LinkedIn, GitHub, and Twitter](./resources/branding_resources.md)
+* [Resume Resources](./resources/resume_resources.md)
+* [Cover Letter Resources](./resources/cover_letter_resources)
+* [Terminal Portfolio Directions](./resources/terminal_directions)
+* [Resources for Writing READMEs](./resources/readme_resources)
+
+### Job Search Strategies
+* [Listing of tools to find jobs](./resources/finding_opportunities)
+* Recommended Reading:
+   * [Designing Your Life](https://bookshop.org/books/designing-your-life-how-to-build-a-well-lived-joyful-life/9781101875322)
+   * [Strategize to Win: The New Way to Start Out, Step Up, or Start Over in Your Career](https://bookshop.org/books/strategize-to-win-the-new-way-to-start-out-step-up-or-start-over-in-your-career/9781594633058)
+   * [Switchers: How Smart Professionals Change Careers -- And Seize Success](https://bookshop.org/books/switchers-how-smart-professionals-change-careers-and-seize-success/9780814439630)
+   * [What Color is Your Parachute?](https://bookshop.org/books/what-color-is-your-parachute-2020-a-practical-manual-for-job-hunters-and-career-changers-revised/9781984856562)
+
+### Negotiations
+* [List of resources to help you with negotiating your job offers](./resources/negotiations)
+* [Tips from 1906 BE grad Mack Halliday on Contracting](https://docs.google.com/document/d/1uq7N9DsqIEabHe19RGhKQ17yciKuZdZ7QYtOsLMqJiI/edit?usp=sharing)
+* Recommended Reading:
+   * [Never Split the Difference: Negotiating as if Your Life Depended on It](https://bookshop.org/books/never-split-the-difference-negotiating-as-if-your-life-depended-on-it/9780062407801)
+
+#### Specific Industry Interest
+* [EdTech](./resources/edtech_resources)
+* [Civic Tech](./resources/civic_tech_resources)
+* [Health Tech](./resources/health_tech_resources)
+* [FinTech](./resources/fintech_resources)
+* [Consulting](./resources/consulting_resources)
+
+### Resources for Specific Affinity Groups
+* [Resources for Veterans](./resources/veteran_resources)
+* [Resources for Introverts](./resources/introversion_resources)
+
+### Leveling Up Your Tech
+* [Directions on Open Source Contributions to DEV Community](https://github.com/forem/forem). DEV (Dev.to) is "a community of software developers who write articles, take part in discussions, and build their professional profiles. We value supportive and constructive dialogue in the pursuit of great code and career growth for all members. The ecosystem spans from beginner to advanced developers, and all are welcome to find their place within our community."
+* [Stackshare: Research Tech Stacks of Popular Companies](https://stackshare.io/stacks)
+* Contribute to Open Source projects using [this guide](https://opensource.guide/)
+* Check out courses on [Udemy](https://www.udemy.com/). You may also be able to get free access from your local library! 
+* Recommended Reading:
+   * [Refactoring: Improving the Design of Existing Code](https://bookshop.org/books/refactoring-improving-the-design-of-existing-code/9780134757599)
+   * [Radical Technologies: The Design of Everyday Life](https://www.versobooks.com/books/2742-radical-technologies)
+
+### Succeeding in the Workplace
+* [TEDx Talk from Carla Harris: How to Find the Person Who Will Help You Get Ahead at Work](https://www.leadingauthorities.com/speakers/video/carla-harris-how-find-person-who-will-help-you-get-ahead-work-tedx)
+
+### Other Recommended Reading
+Note: you can use apps like [Libby](https://www.overdrive.com/apps/libby/) and [Hoopla](https://www.hoopladigital.com/) to listen to audiobooks for free. Also be sure to check out your local library look for other free options. 
+
+* [Atomic Habits](https://bookshop.org/books/atomic-habits-an-easy-proven-way-to-build-good-habits-break-bad-ones/9780735211292)
+* [Go Put Your Strengths to Work: 6 Powerful Steps to Achieve Outstanding Performance](https://bookshop.org/books/go-put-your-strengths-to-work-6-powerful-steps-to-achieve-outstanding-performance/9780743261685)
+* [Grit: The Power of Passion and Perseverance](https://bookshop.org/books/grit-the-power-of-passion-and-perseverance/9781501111112)
+* [Mindset: The New Psychology of Success](https://bookshop.org/books/mindset-the-new-psychology-of-success/9780345472328)
+* [More Than Enough: Claiming Space for Who You Are (No Matter What They Say)](https://bookshop.org/books/more-than-enough-claiming-space-for-who-you-are-no-matter-what-they-say/9780525561583)
+* [Presence: Bringing Your Boldest Self to Your Biggest Challenges](https://bookshop.org/books/presence-bringing-your-boldest-self-to-your-biggest-challenges/9780316256582)
+* [The Checklist Manifesto](https://bookshop.org/books/the-checklist-manifesto-how-to-get-things-right/9780312430009)
+* [The Little Black Book of Success: Laws of Leadership for Black Women](https://bookshop.org/books/the-little-black-book-of-success-laws-of-leadership-for-black-women/9780345518484)
+* [The One Thing: The Surprisingly Simple Truth Behind Extraordinary Results](https://bookshop.org/books/the-one-thing-the-surprisingly-simple-truth-behind-extraordinary-results/9781885167774)
\ No newline at end of file
diff --git a/job_seekers/resources/branding_resources.md b/job_seekers/resources/branding_resources.md
new file mode 100644
index 00000000..19d412c7
--- /dev/null
+++ b/job_seekers/resources/branding_resources.md
@@ -0,0 +1,187 @@
+---
+layout: page
+title: Resources for Building Your Brand as a Software Developer
+---
+## Overview
+The following guidelines are specific to how you can approach your personal branding on the 3 most used branding sites for your job search:
+
+* [LinkedIn](#linkedin): make it easy for employers to find you and get to know your story
+* [GitHub](#github): add your personality to your profile
+* [Twitter](#twitter): show your brand through your engagement and discussion
+* [Miscellaneous](#misc): consider blog posts, open source contributions, or speaking at a meetup as a way to add to your brand
+
+### LinkedIn <a name="linkedin"></a>
+LinkedIn is specifically set up to utilize algorithms and context to help employers find potential candidates and vice versa. As we look at LinkedIn today, we'll talk about how you can passively use it for your job search -- how do people find you? How do they know who you are? It all has to do with how you tell your stories and the particular keywords that you're using. If you don't already have a LinkedIn profile, now is time to set one up [here](https://www.linkedin.com/).
+
+#### Dissecting the Profile
+**First Look:**
+The top of your profile is an opportunity to make a great first impression. When a recruiter or potential employer clicks on your profile, they see 4 initial things:
+
+* **Your picture:** Headshot of just you (not your friends, family, or pets!) and the same photo across your multiple profiles. Don't have a professional-looking headshot? Check out [this post](https://writing.turing.edu/how-to-take-your-own-linkedin-headshot/) with tips on how to take your own!
+* **Your headline:** What your expertise is
+* **Your location:** Where do you want to be? If you want to work in San Francisco, list San Francisco
+* **The first few sentences of your summary:** This is why it's so important. Make those first 100 words stand out.
+
+**Headline:**
+
+* This is your expertise
+   * What do you want your brand to be?
+   * When recruiters do a search, what keywords do you want to lead to you?
+	* Consider "Software Developer," "Back End Engineer," or "Front End Engineer"
+	* You can combine your past experiences with new skills like "Software Developer | Former Educator"
+	* Consider adding in languages/frameworks you specialize in
+   * Any keywords here should be consistently displayed throughout your profile
+
+**Summary:**
+This is the story that you're telling: who you are (as a developer, worker, teammate, individual, etc.), how you got here (why software development, why now), what's next (what are your longterm career goals/ambitions). Your story is one of the few places in the profile where you can introduce yourself as a whole person and should be told from a high level.
+
+Tips for an effective summary:
+
+* Keep it to 2-3 short paragraphs, 2-3 sentences per paragraph
+* Write it in first person
+* Provide a call to action -- what do you want people to do when they see your profile? Do you want them to look at your code, website, email you?
+	* Put your email address right there in the summary. Once you get a job, you can take it out, but don't create any blockers right now
+
+**Examples: What can a LinkedIn summary look like?**
+* Merge your past experience with your new career path:
+   * “Combining marketing experience with a love for data, I’m a software developer looking to…”
+* What are your motives?
+   * “My love for helping people led me to develop apps that focus on the user experience…”
+* What do you enjoy working with? Mention your specialities (aka keywords):
+   * “Along with my experience in client-side development, I have been learning and working with Node, Express, Knex, PostgreSQL and RESTful API creation to fill out my server-side experience.”
+
+Still need convincing that you need a summary?
+* The summary allows you to show up in search results
+* Remember: 82% of business decision makers said that presence in search results was an influential factor when vetting people online
+* A summary is an easy way for someone to learn specifically about you when searching for candidates
+
+**Work Experience:**
+As you list your past experiences, your accompanying description should not be bullet points. Why? It doesn't read as well on LinkedIn and interferes with keyword searches. LinkedIn is also built out to be a *storytelling platform*, so use it that way. Write in complete sentences and paragraphs. Think about how you read across a computer screen. You want your profile to be easy to scan since recruiters only have so much time to look at them.
+
+* Focus on applicable and transferable skills; Again, consider keyword searches
+* Instead of listing tasks, discuss value of your past work.
+   * What value did you bring to this company?
+* Link to the name of the company
+   * List Turing under experience but clearly state that you're a student in the description of the experience. 
+   * Avoid using the word "student" in any titles
+   * Describe your experience while at Turing; list technologies and value you’ve created through your project work
+
+**Education:**
+Under education, make sure to include Turing again as this ties you to the [Turing alumni page](https://www.linkedin.com/school/turingschool/people/), which allows our Turing network to grow so that future students can seek out where alumni work just like you are
+
+**Personalized URL:**
+Edit your URL with your name. Use just your first and last name, no numbers -- you don't want to open yourself up to any age discrimination.
+
+To edit your URL, click on "edit your public profile" on the righthand side of the screen. From there, you'll see an edit button for your URL. If your name is taken, use your middle name, etc. but it should be consistent across all social platforms. This is also easy to put on resumes and business cards.
+
+**Nice to haves:** *Don't spend a ton of time on these extras, but consider how they may add to your profile.*
+
+* Projects: any visuals are helpful. Recruiters aren't going to see this on their first look. They will see it on their second sweep
+* Skills: list all the technologies you use even if you haven't been endorsed for them, but they should be in the lower part
+* You can make your LinkedIn in multiple languages to address and attract different communities. This is effective if you'd like to work abroad
+
+**Career Interests Button:**
+Below your summary, on your personal dashboard, there is an option to update your career interests to let recruiters know if you're actively, passively, or not looking for opportunities. You can update this if you'd like to let recruiters know more specifically about your interests. Be warned -- you may open yourself up to lots of contacts if you click it on, and they may not always be helpful. But this would also increase your conversations with recruiters, which at the very least could be a good learning opportunity.
+
+**Add Connections**
+Your network & their relevance to the job you want DO matter -- start connecting with peers in the industry!
+* Aim for at least 100 connections
+* Quality over quantity
+* When adding Turing staff/alumni, please include an introductory message.                                          
+* Engage with your connections by liking, commenting on, and/or sharing their updates.
+* As you continue to grow in your development at Turing, share your own updates, whether they be blog posts or links to projects.
+
+**Examples of Effective Alumni LinkedIn Profiles**
+
+* [Smitha Hosmani](https://www.linkedin.com/in/smitha-hosmani/)
+* [Nick Nist](https://www.linkedin.com/in/nicknist/)
+* [Bekah Lundy](https://www.linkedin.com/in/bekah-lundy/)
+* [Matt Kaufman](https://www.linkedin.com/in/matthew-leo-kaufman/)
+
+### GitHub Overview <a name="github"></a>
+You already have a GitHub profile -- make sure it looks good!
+
+#### Profile
+Here are some tips to keep in mind:
+
+* Add a headshot photo rather than using the avatar to look more professional. It's also helpful for it to be the *same* photo you use on your LinkedIn or other branding sites to show continuity of your story and let employers know they're finding the same person. 
+
+* Complete your GitHub profile with:
+	- Your name (especially if it's different from your username)
+	- Location
+	- Link to personal site once you have one
+	- Twitter handle
+	* Include your email address so that anyone who sees your profile can immediately reach out to you
+
+* Create a ReadMe for your profile so that other developers can get to know you
+	* [Check out the overview here](https://docs.github.com/en/github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme)
+	* [Here's an easy tool to get you started](https://profilinator.rishav.dev/)
+
+* Pin your best projects to your profile page and keep it up-to-date
+* File issues on all your repos for things that need fixing up
+
+Here are some additional resources, but don’t feel pressure to make this too fancy. It's better to be tasteful and understated with answers to some basic questions than to look too busy. Check these out:
+
+* [Martin Heinz's Build a Stunning ReadMe for your GitHub profile](https://towardsdatascience.com/build-a-stunning-readme-for-your-github-profile-9b80434fe5d7). Note: be careful with the emojis. His are very subtle and tasteful. If you’re not 100% positive yours are as well, better to leave them out.
+* [Gapur Kasim's How to Create an Awesome GitHub Profile ReadMe](https://javascript.plainenglish.io/how-to-create-an-awesome-github-profile-readme-a474d5b45645). Note: some other interesting widgets that you could stretch for. Don’t go overboard, and if they don’t highlight what you want, tell the story you’d like, better to leave them out.
+* [Andres Villegas's Creating a Standout GitHub Profile ReadMe](https://medium.com/bigcommerce-developer-blog/creating-a-standout-github-profile-readme-ee87f4320585). Note: again, be careful with the custom images. Ask someone you trust to tell you if they look professional/add to the experience.
+
+#### Projects
+Make sure that all of your projects have a ReadMe. Think about the ReadMe as encompassing a few things:
+
+* It's an advertisement of your work. How can you highlight important accomplishments and challenges?
+* It's documentation. If someone else were going to use your project, what do they need to know?
+
+[Here are resources for writing excellent ReadMes](/resources/readme_resources)
+
+### Twitter Overview <a name="twitter"></a>
+You don't *have* to have a Twitter account. But a lot of software developers (aka the people you want to connect with) are using Twitter, so we would highly recommend that you create a profile if you don't have one already!
+
+Twitter allows you to:
+
+- Display your brand visually and through written content
+- Engage in conversations that reinforce your personal brand
+
+**Profile**
+- Include a headshot of **_you_**
+- Include your personal website link, email, and mini, high-level bio introduction
+- Consider what your profile says about you to someone that has never met you
+
+**Converse**
+- Search for topics interesting to you ("webdev", "edtech", "diversity in tech")
+- Consider how you would approach a conversation at a party. Listen, observe, then evaluate when is appropriate to interject with your opinion, perspective, knowledge.
+- Add to the conversation
+* Start your own conversations
+	* What's important to you?
+	* What content can you share?
+	* This isn't about self-promotion per se, it's about connection
+
+**Follow**
+From this post [15 Twitter Accounts Every Web Developer Should Follow](https://blog.planetargon.com/entries/15-twitter-accounts-every-web-developer-should-follow):
+
+**Front End Developers:**
+* Catt Small (@cattsmall)
+* Harry Roberts (@csswizardry)
+* CSS Tricks (@Real_CSS_Tricks)
+* Jen Simmons (@jensimmons)
+* Rachel Andrew (@rachelandrew)
+* Nathan Yau (@flowingdata)
+
+**Ruby on Rails Developers:**
+* DHH (@dhh)
+* Justin Searls (@searls)
+* Sarah Mei (@sarahmei)
+* Colin Jones (@trptcolin)
+* Thomas Fuchs (@thomasfuchs)
+
+**General Development:**
+* Trek Glowacki (@trek)
+* Egghead.io (@eggheadio)
+* Jason Fried (@jasonfried)
+* Free Code Camp (@freecodecamp)
+* The Practical Dev (@ThePracticalDev)
+
+### Miscellaneous <a name="misc"></a>
+* [Tips for Writing Technical Blog Posts](/module_four/blogging_tips)
+* [Open Source Guide](https://opensource.guide/)
+* [Tips for Speaking at a Meetup](/module_four/meetup_involvement_guidelines)
diff --git a/job_seekers/resources/civic_tech_resources.md b/job_seekers/resources/civic_tech_resources.md
new file mode 100644
index 00000000..9ee76c1e
--- /dev/null
+++ b/job_seekers/resources/civic_tech_resources.md
@@ -0,0 +1,36 @@
+---
+layout: page
+title: Civic Tech Resources
+---
+
+## What is Civic Tech?
+Civic Tech is a catch-all term for technology built for public or community good, and the industries that could fall under this term range from government, non-profit, or those focused on social issues. [This article gives more background into this field.](https://medium.com/tradecraft-traction/navigating-the-field-of-civic-tech-c1f9670c8f69)
+
+### Research & Learning
+More than probably any other industry, Civic Tech is designed to include others through open source and community projects. Here are some resources on how to learn more and get involved:
+
+* [Civic Tech Field Guide](https://civictech.guide/) has information on 4000+ civic tech projects. 
+* Check out the [Civic Tech Innovation Network](https://medium.com/civictech) news articles to learn more about what's happening in this organization. 
+
+### How to find Jobs in Civic Tech
+
+#### Network
+
+* [Code for America](https://www.codeforamerica.org/) is a great place to start to see what civic tech can look like in action and get involved.
+    * Depending on where you live, Code for America has 80+ local chapters in their [Brigade Network](https://brigade.codeforamerica.org/?_ga=2.135734833.1060532018.1621282426-127613670.1621282426)
+
+#### Companies
+
+* [Civic Tech Company Database](https://airtable.com/universe/exp8LkpapvedfTi6k/civic-tech-companies-and-organizations?explore=true)
+* [List of Tech Worker Cooperatives](https://github.com/hng/tech-coops#coops-namerica)
+* [Civic Tech Field Guide Company Page](https://civictech.guide/listing-category/social-impact-design-groups/)
+
+#### Job Boards & Search Tools
+
+* [Tech Jobs for Good](https://techjobsforgood.com/)
+* [Progressive Data Jobs](https://www.progressivedatajobs.org/)
+* [Code for America's Public Interest Tech job board](https://jobs.codeforamerica.org/). Note: this site is down for maintenance until July 1, 2021
+
+#### Other Resources
+
+* [Public Interest Technology Resources](https://public-interest-tech.com/)
diff --git a/job_seekers/resources/consulting_resources.md b/job_seekers/resources/consulting_resources.md
new file mode 100644
index 00000000..3e0a0204
--- /dev/null
+++ b/job_seekers/resources/consulting_resources.md
@@ -0,0 +1,36 @@
+---
+layout: page
+title: Consulting Resources
+---
+
+## What is Software Consulting?
+Consulting is all about helping companies solve their problems through software. No two consulting project looks alike. Here is an article from [BuiltIn on the Day in the Life of a Consultant](https://builtin.com/software-engineering-perspectives/software-consultant)
+
+### Consulting Companies
+
+* [BuiltIn's list of EdTech Companies](https://builtin.com/companies/type/consulting-companies)
+* Consulting companies who have hired from Turing:
+   * Slalom
+   * AbiEzzi Consulting
+   * Barbershop
+   * Biarri Networks
+   * BuildIt (wipro digital)
+   * Carbon Five
+   * DevIQ
+   * Formidable
+   * iTrellis LLC
+   * MagmaLabs
+   * McKinsey & Company
+   * Nebulab
+   * Nerdery
+   * Nexia
+   * Nzyme
+   * OneClickPolitics
+   * Perficient
+   * Physician's Computer Company
+   * Power Auctions LLC
+   * Publicis Sapient
+   * Qwinix
+   * Secret Stache
+   * Slalom
+   * Spantree Technology Group
diff --git a/job_seekers/resources/cover_letter_resources.md b/job_seekers/resources/cover_letter_resources.md
new file mode 100644
index 00000000..f1a4b34d
--- /dev/null
+++ b/job_seekers/resources/cover_letter_resources.md
@@ -0,0 +1,63 @@
+---
+layout: page
+title: Cover Letter Resources
+---
+
+## Overview
+If we were to sum up the cover letter and how it compares to your resume in one sentence, the resume is about you while the cover letter is about *them (the company.* 
+
+### Templates to Get You Started
+Below are Cover letter templates to help get you started, but make sure to *customize* your cover letter each time you write one:
+* [Guided Cover Letter Template](https://docs.google.com/document/d/1ctPSIEcZ5nrnfD4y0HlTUH9tdYRscbIjXhMQLjMPzPA/edit)
+* [JobScan General Cover Letter](https://docs.google.com/document/d/1_UhzVQAWHdLruR8zaxpy92mafX8phDwo2lOjuXpHL-w/edit#)
+* [JobScan General Cover Letter ](https://docs.google.com/document/d/1ctPSIEcZ5nrnfD4y0HlTUH9tdYRscbIjXhMQLjMPzPA/edit)
+
+### General Advice
+
+* [Ask a Manager: Examples of great cover letters](https://www.askamanager.org/category/cover-letters)
+* [The Muse: All-Time Best Tips for Writing Cover Letters](https://www.themuse.com/advice/how-to-write-a-cover-letter-31-tips-you-need-to-know)
+* [The Muse: Cover Letter Examples for Every Type of Job Seeker](https://www.themuse.com/advice/cover-letter-examples-every-type-job-seeker)
+* [The Muse: 12 Great Resources if Writing a Cover Letter Fills You With Dread](https://www.themuse.com/advice/12-great-resources-if-writing-a-cover-letter-fills-you-with-dread)
+* [How to Write the Ultimate Tech Cover Letter (with examples)](https://docs.google.com/document/d/1u0HDGdncaJF-Z41wvsisn5UEdhyr1-wI-Lu0c7RexBk/edit?usp=sharing)
+* [How to Start a Cover Letter](https://www.thebalancecareers.com/cover-letter-opening-sentences-examples-2061030)
+
+## General Checklist
+Use this checklist to make sure your cover letters have all the necessary components. 
+
+### Layout
+- [ ] Clean, easy-to-follow
+- [ ] No more than one page
+- [ ] Paragraphs spaced apart
+
+### Heading & Contact Info
+- [ ] Name: stand outs, easy to read
+- [ ] Title: "software developer/front end engineer/back end engineer," stand outs, easy to read, comparable in size to name (optional)
+- [ ] Email address
+- [ ] Phone number
+- [ ] GitHub link 
+- [ ] LinkedIn link 
+- [ ] Personal website (optional)
+
+### Opening & Closing
+- [ ] Opening: addressed to either a specific person or a specific team
+- [ ] Closing: Uses a closing phrase like "looking forward to hearing from you," etc. and name is included
+- [ ] Clear and concise
+- [ ] No grammatical or spelling errors
+
+### Paragraph #1 
+- [ ] Opening sentence makes it clear what position is being applied for
+- [ ] Provides a brief description of the job seeker's career trajectory and how it connects to the company's mission, product, user experience, customers, etc, 
+- [ ] If applicable: references a contact at the company that they've spoken with 
+- [ ] Clear and concise
+- [ ] No grammatical or spelling errors
+
+### Paragraph #2
+- [ ] Expands on why they're qualified (going in-depth on skills/experience)
+- [ ] Describes a project/experience in which they demonstrate how they can do the job
+- [ ] Clear and concise
+- [ ] No grammatical or spelling errors
+
+### Paragraph #3
+- [ ] Makes a connection back to the company: how the job seeker can bring value to the company, passion about the product, what they hope to help the company achieve, etc.
+- [ ] Clear and concise
+- [ ] No grammatical or spelling errors
diff --git a/job_seekers/resources/edtech_resources.md b/job_seekers/resources/edtech_resources.md
new file mode 100644
index 00000000..df06090f
--- /dev/null
+++ b/job_seekers/resources/edtech_resources.md
@@ -0,0 +1,29 @@
+---
+layout: page
+title: EdTech Resources
+---
+
+## What is EdTech?
+EdTech refers to technology in the education industry whether by creating software and technology for use in classrooms or software that drives education management or curriculum building. [BuiltIn has a comprehensive guide here](https://builtin.com/edtech).
+
+### How to find Jobs in EdTech
+
+#### Network
+
+* Here is a [comprehensive list](https://www.meetup.com/topics/edtech/) of Meetups centered around education and technology. 
+* [EdTech Womxn](http://edtechwomen.com/)
+* [EdTech Organizations](https://blog.neolms.com/8-ed-tech-organizations-every-teacher-should-know-about/) that are not necessarily specific to software developers but would create great networking opportunities.
+
+#### Companies
+
+* [BuiltIn's list of EdTech Companies](https://builtin.com/companies/type/edtech-companies)
+* Companies that have hired Turing grads:
+  * 2U
+  * Guild Education
+  * SchoolSafe Communications
+  * Year Up
+
+#### Job Boards & Search Tools
+
+* [EdSurge](https://www.edsurge.com/jobs) (filter by Engineering jobs)
+* [AngelList](https://angel.co/jobs) (filter by Education)
diff --git a/job_seekers/resources/finding_opportunities.md b/job_seekers/resources/finding_opportunities.md
new file mode 100644
index 00000000..1d6117d4
--- /dev/null
+++ b/job_seekers/resources/finding_opportunities.md
@@ -0,0 +1,151 @@
+---
+layout: page
+title: Resources for Finding Opportunities
+---
+
+Below are resources to help you find opportunities from job postings to networking groups:
+
+### Search by...company
+* [BuiltIn](http://builtin.com/)
+    * Provides lots of details about companies
+    * Located in Austin, Boston, Chicago, Colorado, LA, New York, and Seattle
+* [Otta](https://otta.com/) selects specific companies to showcase and provides a personalized approach to curating what listings show up for you when you make an account.
+* [Google](http://www.google.com/)
+    * Tips:  
+      * Search “top tech companies in [location]” / "top workplaces in [industry (edtech, fintech, etc.)]" and look for a journalist-generated list of companies that are recommended in that area
+      * Pick a couple companies to look into and walk through their website, including their careers page and team page
+      * Research these people on LinkedIn, Twitter, and look for a personal blog 
+    * Other Resources:
+      * [25 Killer Combos for Google's Site: Operator](https://moz.com/blog/25-killer-combos-for-googles-site-operator)
+      * [How to Use Google Search More Effectively](http://mashable.com/2011/11/24/google-search-infographic/)
+* [Owler](https://www.owler.com/) is a great way to conduct research on different companies.
+
+### Search by...culture
+* [Key Values](https://www.keyvalues.com/) allows you to search for companies that fit with your key values.
+* [Glassdoor](https://www.glassdoor.com/index.htm)
+* [CareerBliss](https://www.careerbliss.com/reviews/)
+* [The Muse](https://www.themuse.com/)
+* Tip: use Owler to track these companies and find out more about their culture
+
+* Start Ups:
+  * [Startupers](https://www.startupers.com/)
+  * [Techstars Listing of Companies](https://www.techstars.com/companies/)
+  
+* Learn about [freelance work here from Incluzion](https://learn.incluzion.co/) and [set up a profile here](https://app.incluzion.co/login/) to be notified about freelance opportunities
+  
+### Search by...language or skillset
+* [Ruby Weekly](http://rubyweekly.com/)
+* [Ruby Now](https://jobs.rubynow.com/)
+* [Ruby on Rails Jobs](https://www.rorjobs.com/)
+* [JavaScript Weekly](http://javascriptweekly.com/)
+* [React Job Board](https://www.reactjobboard.com/)
+* [Python Job Board](https://www.python.org/jobs/)
+* [Elixir Jobs](https://elixirjobs.net/)
+* [Hatchways](https://hatchways.io/#/) helps connect juniors with their first jobs in tech by identifying skill gaps and talking through goals for your job search.
+* [ZipRecruiter](https://www.ziprecruiter.com/) connects job seekers with recruiters based on specific languages/skills
+* [Stackshare](https://stackshare.io/stacks) allows you to search for tech stacks of popular companies
+
+### Search by...network
+* [LinkedIn](http://www.linkedin.com/)
+   * Tips: 
+      * Use the "Advanced Search" tool to find people based on skillset, location, and industry OR names of companies and select the "People who work at..." option
+      * In "Keywords" type in the skills or focus you want to be working in (i.e., JavaScript, Ruby, Python, EdTech, FinTech, etc.)
+      * In "Location" type in the area where you'd like to work
+      * In "Industry" select "computer software"
+      * Search: Of those profiles that return, look at their profiles to see the list of companies they've worked for. What companies do you want to continue to research? Who do you want to connect with? 
+      * You can also click on the company’s page and on the right side, view "Similar Companies" where your connections work
+* [Juniors in Tech](https://www.juniorsintech.com/) newsletter
+* [People of Color in Tech](https://www.pocitjobs.com/) is a job site specifically for People of Color in tech.
+* [Black Tech Pipeline](https://blacktechpipeline.com/) provides a job board and recruitment pipeline to connect Black developers with opportunities. 
+* [reacHire](http://www.reachire.com/women/jobs) is a job site specifically for connecting women with companies that value inclusion. 
+* [This Dot](https://www.thisdot.co/hirethefempire) hires women-presenting, frontend junior developers.
+* [Power to Fly](https://powertofly.com/jobs/) is a job site specifically for women.
+* [Diversify Tech](https://www.diversifytech.co/) is a job site built specifically for underrepresented groups in tech.
+* [Include.io](https://include.io/) is a job site built to connect underrepresented groups in tech with employers.
+* [Incluzion](https://incluzion.co/) is a community of Black and Latinx professionals working remotely and flexibly. They also operate as a connector between companies and diverse talent. 
+* [Jopwell](https://www.jopwell.com) is a community built specifically to advance careers for Black, Latinx, and Native American students and professionals. They post jobs as well as information on events and career advice. 
+* [Tech Ladies](https://www.hiretechladies.com/) is a community for women and non-binary folks. You have to apply to join, but once accepted, you'll have access to jobs from partnering companies.
+* [Black Career Network](https://www.blackcareernetwork.com/) connects Black professionals with job opportunities. 
+* [Chezie](https://www.chezie.co/) is a diversity career platform that allows you to search by both companies that value DEI and view job postings. 
+* [Elpha](https://elpha.com/talent-pool) is a community for women to discover career opportunities in tech and network with other women in the field. 
+* [Software Engineering Newsletter](https://swejobs.substack.com/) lists jobs, events, and more ways to build your professional network.
+
+### Search by...job listings
+* Turing's Terminal Job Board postings in #job-hunt on Slack
+* [BuiltIn](http://builtin.com/) is located in Austin, Boston, Chicago, Colorado, LA, New York, and Seattle
+* [Juione Engineering Job List](https://junior.engineer/) is built and maintained by a Turing alum to bring a one-stop shop approach to finding junior job listings.
+* [Link Up](https://www.linkup.com/job-seekers/) - an index of employer websites with job listings in order to avoid duplicates.
+* [GitHub’s Job Board](https://jobs.github.com/)
+* [Glassdoor](https://www.glassdoor.com/index.htm)
+* [Smashing Magazine’s Job Board](http://jobs.smashingmagazine.com/)
+* [Mashable's Job Board](http://jobs.mashable.com/jobs/search/results)
+* [Angel List](https://angel.co/jobs)
+* [Hired](https://hired.com/)
+* [Dice](https://www.dice.com/#)
+* [Stack Overflow Job Board](http://careers.stackoverflow.com/jobs)
+* [Product Hunt](https://www.producthunt.com/jobs)
+* [Hacker News](https://news.ycombinator.com/jobs)
+* [Authentic Jobs](https://authenticjobs.com/)
+* [Krop](https://www.krop.com/)
+* [Indeed](https://www.indeed.com/)
+* [The Muse](https://www.themuse.com/jobs)
+* [Craigslist](https://denver.craigslist.org/d/software-qa-dba-etc/search/sof) 
+* [gun.io](https://gun.io/)
+* [Ars Technica Job Board](http://arstechnica.com/jobs/)
+* And again, don't forget about the #job-hunt channel on Slack
+
+### Search by...remote opportunities
+* Remote listings:
+  * [Established Remote Companies](https://github.com/yanirs/established-remote)
+  * [List of Remote-Friendly Companies](https://github.com/remoteintech/remote-jobs)
+  * [List of Startups with Distributed Teams](https://docs.google.com/spreadsheets/d/1uDdDyheNY_-Z3MtuNoFdBYBooBnUTmlYCOZ3VhcN9Sw/edit?usp=sharing)
+  * [Another Remote Company List](https://docs.google.com/spreadsheets/d/1tETz3dWHkbzbXAMZ9XXdR0VKhhite-i_ON_Ei3TjFSc/edit?usp=sharing)
+  * [AngelList Remote Job Collection](https://angel.co/remote)
+  * [Authentic Jobs - Remote](https://authenticjobs.com/#onlyremote=1)
+  * [Flex Jobs](https://www.flexjobs.com/)
+  * [Incluzion Remote Jobs Board](https://incluzion.co/remote-jobs-info/)
+  * [NODESK](https://nodesk.co/remote-jobs/)
+  * [Remote4me](https://remote4me.com/)
+  * [RemoteBase](https://remotebase.io)
+  * [Remote.co](https://remote.co/remote-jobs/)
+  * [Remote OK](https://remoteok.io/remote-dev-jobs)
+  * [Remotive](https://remotive.io/)
+  * [StackOverflow Remote Job Listings](https://stackoverflow.com/jobs/remote-developer-jobs)
+  * [We Work Remotely Job Board](https://weworkremotely.com/)
+  * [Working Nomads](https://www.workingnomads.co/jobs?category=development)
+
+Also check out these [Remote Working Resources](https://github.com/lukasz-madon/awesome-remote-job)
+
+* [Remote Woman](https://remotewoman.com/) is a community for professional women who work remotely.
+
+## Search by...recruiter assistance
+* [Staffing Agencies Resources](https://www.clearlyrated.com/staffing/it-engineering-staffing/web-mobile-software-development-staffing)
+* [TripleByte](https://triplebyte.com/) allows you to showcase your skills to go straight to the tech interview at certain companies. 
+* [Hatchways](https://hatchways.io/#/) helps connect juniors with their first jobs in tech by identifying skill gaps and talking through goals for your job search.
+* [ZipRecruiter](https://www.ziprecruiter.com/) connects job seekers with recruiters based on specific languages/skills.
+
+### Search by...outreach & social media
+In addition to finding the right posting, remember that the next step is to find a face at the company to connect with. LinkedIn will be your go-to site for this, but a great way to continue the research into places you want to work that are aligned with your goals is by building your network. Below are some suggestions for groups to utilize for this purpose:
+
+* [Meetup](http://www.meetup.com/)
+   * Tips: Search for groups local to the area you’re interested in working and in topics that you're interested in pursuing (i.e. Ruby, JavaScript, etc.). Be sure to select "Groups" (not "Calendar"). On the group page, there are two things that will be very useful to your job search:
+      * Organizers list: who are they? Where do they work? What other meetups are they active in?
+      * Upcoming events: look at the RSVP list; Who else is going? What companies do they work for? 
+* [BeVisible](https://www.bevisible.soy/) is a career network for Latinx.
+* [Black Data Processing Associates](https://www.bdpa.org/default.aspx) is an international organization for Black professionals in tech. 
+* [CodeNewbie](https://www.codenewbie.org/) is a community for newcomers to code.
+* [Diversify Tech](https://www.diversifytech.co/) is a community built to share upcoming conference scholarships, events, education scholarships, job opportunities, and more for people who are underrepresented in tech. 
+* [Ladies Get Paid](https://www.ladiesgetpaid.com/join) allows you to connect with thousands of women from around the world to share advice, resources, and job opportunities.
+* [Lesbians Who Tech](https://lesbianswhotech.org/) is a career network for lesbians. 
+* [MAES](http://mymaes.org/) was founded in Los Angeles in 1974 to increase the number of Mexican Americans and other Hispanics in the technical and scientific fields. 
+* [National Society of Black Engineers](http://www.nsbe.org/home.aspx) is one of the largest student-governed organizations with the aim to increase the number of culturally responsible Black Engineers.
+* [Out in Tech](https://outintech.com/#welcome) is a community to connect LGBTQ+ in tech. 
+* [TechLatino](http://techlatino.org/) is an organization to empower Latino technological and scientific engagement.
+* [Trans Tech Social Enterprises](https://www.transtechsocial.org/) is an incubator for LGBTQ Talent with a focus on economically empowering transgender people. 
+
+### Social Media Resources for your Job Search:
+
+* [The Best Way to Use Social Media for Your Job Search](http://www.forbes.com/sites/trudysteinfeld/2012/09/28/the-best-ways-to-use-social-media-in-your-job-search/)
+* [Twitter 101: A Tutorial for the Timid](https://www.themuse.com/advice/twitter-101-a-tutorial-for-the-timid)
+* [How to Not Suck at Twitter](https://www.themuse.com/advice/how-not-to-suck-at-twitter)
+* [5 Better Ways to Network on Twitter and LinkedIn](https://www.themuse.com/advice/5-better-ways-to-network-on-twitter-linkedin)
diff --git a/job_seekers/resources/fintech_resources.md b/job_seekers/resources/fintech_resources.md
new file mode 100644
index 00000000..fdaf9ad0
--- /dev/null
+++ b/job_seekers/resources/fintech_resources.md
@@ -0,0 +1,26 @@
+---
+layout: page
+title: FinTech Resources
+---
+
+## What is FinTech?
+Fintech companies integrate technologies (like AI, blockchain and data science) into traditional financial sectors to make them safer, faster and more efficient. Fintech is one of the fastest-growing tech sectors, with companies innovating in almost every area of finance; from payments and loans to credit scoring and stock trading. [More in an overview from BuiltIn here](https://builtin.com/fintech).
+
+### How to find Jobs in FinTech
+
+#### Network
+
+* [FinTech Circle](https://fintechcircle.com/)
+* [FinTech Meetup](https://fintechmeetup.com/)
+* [WiFTN](https://www.wiftn.com/)
+* [FinTech Connector](https://www.fintechconnector.com/)
+* [Machine Learning Meetups](https://www.meetup.com/topics/machine-learning/)
+* [Artificial Intelligence Meetups](https://www.meetup.com/topics/ai/)
+* [Data Science Meetups](https://www.meetup.com/topics/data-science/)
+* [Blockchain Meetups](https://www.meetup.com/topics/blockchain/)
+* [Listing of FinTech Trade Associations](https://guides.loc.gov/fintech/trade-associations)
+
+
+#### Companies
+
+* [Listing of FinTech companies across the US](https://builtin.com/companies/type/fintech-companies)
diff --git a/job_seekers/resources/health_tech_resources.md b/job_seekers/resources/health_tech_resources.md
new file mode 100644
index 00000000..accc56fb
--- /dev/null
+++ b/job_seekers/resources/health_tech_resources.md
@@ -0,0 +1,18 @@
+---
+layout: page
+title: Health Tech Resources
+---
+
+## What is Health Tech?
+Health Tech refers to technology built to support health and wellness, whether for hospital settings, mental health support, or tracking fitness. [BuiltIn provides a great overview here.](https://builtin.com/healthcare-technology)
+
+### How to find Jobs in Health Tech
+
+#### Network
+
+* [Health Tech Meetups](https://www.meetup.com/topics/healthtech/)
+
+#### Companies
+
+* [Listing of Health Tech companies across the US from BuiltIn](https://builtin.com/companies/type/healthtech-companies)
+
diff --git a/job_seekers/resources/interview_prep_resources.md b/job_seekers/resources/interview_prep_resources.md
new file mode 100644
index 00000000..96b7b75c
--- /dev/null
+++ b/job_seekers/resources/interview_prep_resources.md
@@ -0,0 +1,149 @@
+---
+layout: page
+title: Interview Prep Resources
+---
+
+Your interview process with tech companies will comprise of two main components:
+
+* [The Technical Interview](#technical)
+* [The Behavioral Interview](#behavioral)
+
+Below you can find lots of resources to help you prepare for both components.
+
+## Technical Interview Prep Resources
+
+### Start Here <a name="technical"></a>
+* [Former instructor Ian Douglas' Guide to Technical Interview Prep](https://techinterview.guide)
+  * Ian also hosts live streams on Twitch [here](https://techinterview.guide/streaming/#live-on-twitchtv-httpstwitchtviandouglas736) on Thursdays and Sundays at 7pm MT to answer questions on interview prep
+  * View his [pre-recorded interview guide videos here](https://www.youtube.com/c/iandouglas)
+  * Join his mailing list at [his site](https://techinterview.guide/daily-email-series/) for interview prep emails
+  * Watch [this recording between Ian & Aline Lerner from interviewing.io](https://vimeo.com/535068814/6809689362)
+* [Tech Interview Handbook](https://yangshun.github.io/tech-interview-handbook/) by Yangshun Tay and Louie Tan
+  * [Preparing for a Coding Interview](https://yangshun.github.io/tech-interview-handbook/coding-round-overview/#!)
+  * [Interview Cheat Sheet](https://yangshun.github.io/tech-interview-handbook/cheatsheet/)
+* [Step-by-Step Guide to Answering a Technical Question in a Coding Interview](https://betterprogramming.pub/the-step-by-step-guide-to-answering-a-technical-question-in-a-coding-interview-37928490d4e2)
+
+### Practice
+* [Pramp](https://www.pramp.com/#/) is a free site to practice technical interviews with a peer. Use the promo code at [https://www.pramp.com/promo/iandouglas](https://www.pramp.com/promo/iandouglas) to get unlimited mock interview credits
+
+* [Interviewing.io](https://interviewing.io/) allows you to do anonymous mock interviews from top companies. You can also watch recordings of past interviews!
+
+* [TripleByte](https://triplebyte.com/) allows you to showcase your skills to go straight to the tech interview at certain companies.
+
+* [Leet Code](https://leetcode.com/) is a platform both practicing technical interview skills (there are over 1600 questions to practice!) and for helping companies identify top technical talent through sponsored events on the platform.
+
+* Coding challenges resources:
+   * [Turing challenges](https://github.com/turingschool/challenges)
+   * [Code Wars](https://www.codewars.com/)
+   * [Exercisms](http://exercism.io/languages/)
+   * [HackerRank](https://www.hackerrank.com/dashboard)
+   * [CodeSignal](https://codesignal.com/)
+   * [Interview Cake](https://www.interviewcake.com/)
+   * [Daily Coding Problem](https://www.dailycodingproblem.com/)
+
+### Other Resources
+
+* [Top 50 Programming Interview Questions](https://simpleprogrammer.com/programming-interview-questions/)
+* [Essential Ruby Interview Questions](https://www.toptal.com/ruby/interview-questions)
+* [List of Ruby on Rails questions](https://www.codementor.io/blog/ruby-on-rails-interview-questions-du107w0ss?icn=post-3ey8yl7epg&ici=post-du107w0ss)
+* [Front End Interview Handbook](https://github.com/yangshun/front-end-interview-handbook)
+* [Essential JavaScript questions](https://www.codementor.io/nihantanu/21-essential-javascript-tech-interview-practice-questions-answers-du107p62z?icn=post-3ey8yl7epg&ici=post-du107p62z)
+* [10 Interview Questions Every JavaScript Developer Should Know](https://medium.com/javascript-scene/10-interview-questions-every-javascript-developer-should-know-6fa6bdf5ad95)
+* [37 Essential JavaScript Interview Questions](https://www.toptal.com/javascript/interview-questions)
+* [Top 50 React Interview Prep Questions](https://www.edureka.co/blog/interview-questions/react-interview-questions/?utm_source=mybridge&utm_medium=blog&utm_campaign=read_more)
+* [Additional React Questions](https://www.codementor.io/blog/5-essential-reactjs-interview-questions-du1084ym1?icn=post-3ey8yl7epg&ici=post-du1084ym1)
+* [Essential Angular Questions](https://www.codementor.io/blog/angularjs-interview-questions-sample-answers-du1081n7p?icn=post-3ey8yl7epg&ici=post-du1081n7p)
+* [Essential Python Questions](https://www.codementor.io/sheena/essential-python-interview-questions-du107ozr6?icn=post-3ey8yl7epg&ici=post-du107ozr6)
+* [Essential Java Questions](https://www.codementor.io/blog/java-interview-sample-questions-answers-du107xs23?icn=post-3ey8yl7epg&ici=post-du107xs23)
+* Read about the [interview process at over 500 companies](https://airtable.com/shr3eGPDm3wGjT2gA/tbluCbToxQ2knSLhh/viwmFR062GOjG4cjs)
+* [Popular Tech Stacks](https://stackshare.io/stacks)
+* [Devetry's Engineer Interview Rubric](https://info.devetry.com/engineer-interview-rubric)
+
+## Behavioral Interview Prep Resources
+
+### Start Here <a name="behavioral"></a>
+* [How to Answer "Why Should I Hire You?"](https://blog.pramp.com/the-interviewers-perspective-how-to-answer-why-should-i-hire-you-ad070987c2cc)
+* [How to Ace Your Behavioral Interview](https://docs.google.com/document/d/1puRi85xZkeTIXSgCsMYdGVi0GXJ1ANUXEvgnnhVH9Cc/edit?usp=sharing)
+
+### Bank of Common Questions
+**Storytelling, Experience, and Career Goals Questions:**
+* Tell me about yourself. Why do you want to be a software developer?
+* Tell me about your journey into tech. How did you get interested in coding, and why was software development a good fit for you? How is that applicable to our _____ role or company goals?
+* What made you switch from your prior career into programming?
+* Describe your background. How did you get to where you are now? What was your previous career field? What did you like about it? What didn’t you like about it? Why coding?
+* Describe your coding experience and why you wish to continue.
+* What are you looking for in a company? Why would you want to work here?
+* Describe your time at Turing. How did it prepare you for this career?
+* What is your 100% ideal role for your first web development job?
+* Have you ever worked directly with clients or have been in a customer-facing role in the past? If not, would you like to?
+* Talk about your preferred development environment.
+* How are you keeping up with the latest developments in web development?
+* What is something that your hobbies or interests tell me about you that your resume cannot?
+
+**Project, Problem-Solving, & Team Contribution Questions:**
+* Describe a successful idea or project you worked on. What are some of the challenges you had to overcome? What made it a success?
+* Describe a project that failed, a project you had to give up on, or a time you worked really hard on a project and it just didn’t pan out as expected. What happened? How did you make the decisions that you made?
+* When have you solved a problem that didn’t involve you coding?
+* Please describe to me the difference between waterfall and agile approaches to software.
+* How have you implemented or adapted agile practices in your projects?
+* What is your approach to working on a team?
+* A lot of this job will be full-stack. Your experience is largely ____ (Back End, Front End). How do you feel like you’d be able to contribute to the team with only that experience? How comfortable are you with getting uncomfortable with a new language?
+* Describe an example of how you have handled a stressful situation.
+* In what types of environments/projects is it best to use pair programming? Why? In what cases would you not use pair programming? Why?
+* Describe your teamwork experience in a coding environment. How big of a team did you work with?
+* Have you ever had to switch gears in the middle of a project to get something fixed immediately? How did you react?
+* What project of yours are you most proud of and why?
+* You can’t work out how to solve a coding problem. What do you do to find the answer?
+* Tell me about a challenge or conflict you've faced at work and how you dealt with it.
+* How do you approach testing? And what do you think about this? How would you improve QA?
+* When have you exercised leadership and what was the result?
+* Describe a time when you took a risk that paid off for you. What was your process for pushing yourself further? How did you assess risk and try something new?
+* Tell me about a time you had competing priorities or worked on multiple projects at once. How did you manage to make or miss the deadlines? What did you learn from that experience?
+* Sometimes it’s just not possible to get everything on your to-do list done. Tell me about a time your responsibilities got a little overwhelming. What did you do?
+* Give me an example of a time you were able to be creative with your work. What was exciting or difficult about it?
+* Describe a long-term project that you managed. How did you keep everything moving along in a timely manner?
+* Describe a time when you saw a problem and took the initiative to correct it rather than waiting for someone else to do it.
+* Tell me about a time when you worked under close supervision or extremely loose supervision. How did you handle that?
+* When you’re working with a large number of customers, it’s tricky to deliver excellent service to them all. How do you go about prioritizing your customers’ needs?
+* Tell me about a time you were under a lot of pressure. What was going on, and how did you get through it?
+* Tell me about a time you had to be very strategic in order to meet all your top priorities.
+* Give me an example of a time when you had to think on your feet in order to delicately extricate yourself from a difficult or awkward situation.
+
+**Communication & Feedback Questions:**
+* Describe to me the steps you would take to build out a product.
+* Tell me how you solve a problem.
+* Explain one of the most difficult code problems you’ve had to solve, either on your own authored code, or in contributing to someone else’s.
+* Tell me about a time you had a disagreement with a colleague and how you resolved it.
+* Give me an example of a time you faced a conflict while working on a team. How did you handle that?
+* Describe a time when you received feedback that you were surprised by. What did you do with that feedback?
+* When you disagree with a decision your team makes, how do you handle it?
+* Tell me about a time when you had to rely on written communication to get your ideas across to your team.
+* Tell me about a successful presentation you gave and why you think it was a hit.
+* Tell me about a time you needed to get information from someone who wasn’t very responsive. What did you do?
+* Tell me about a time when you had to work closely with someone whose personality was very different from yours.
+* We all make mistakes we wish we could take back. Tell me about a time you wish you’d handled a situation differently with a colleague.
+* Describe a time when you had to interact with a difficult client. What was the situation, and how did you handle it?
+
+**Personal Growth & Self-Awareness Questions:**
+* What is an area of growth for you?
+* Tell me about a time you set a goal for yourself. How did you go about ensuring that you would meet your objective?
+* What’s hard about programming?
+* How do you deal with change?
+* What are some of your best professional/soft skills?
+* Describe your strengths. How have you seen these in practice as a developer?
+* Tell me about a time you failed. How did you deal with the situation?
+* What is your biggest weakness?
+* What is your greatest professional achievement so far? Why?
+* Where do you see yourself in 5 years?
+* How would your former boss/current classmates/instructors describe you?
+* When have you taken accountability for something even when it could have proven detrimental for you?
+* Describe a time when your team or company was undergoing some change. How did that impact you, and how did you adapt?
+* Tell me about the first job you’ve ever had. What did you do to learn the ropes?
+
+### Practice
+
+Reach out to a member of the Career Development Team if you'd like to set up a mock interview.
+
+### Questions to Ask the Interview & Other Resources
+* [Questions to Ask the Interviewer](https://yangshun.github.io/tech-interview-handbook/questions-to-ask/)
+* [Tool to Help You Come Up with Culture Questions](https://www.keyvalues.com/culture-queries)
diff --git a/job_seekers/resources/introversion_resources.md b/job_seekers/resources/introversion_resources.md
new file mode 100644
index 00000000..30508848
--- /dev/null
+++ b/job_seekers/resources/introversion_resources.md
@@ -0,0 +1,20 @@
+---
+layout: page
+title: Introversion Resources
+---
+
+Check back here often for updated resources for supporting job seekers who are higher on the introversion spectrum. 
+
+### Job Searching as an Introvert
+
+* [How Being an Introvert Helped Me in My First Job](https://www.quietrev.com/how-being-an-introvert-helped-me-in-my-first-job/)
+
+### Networking as an Introvert
+
+* Check out [LunchClub](https://lunchclub.com/), which is a social networking platform that uses artificial intelligence and machine learning to connect users with common interests and objectives.
+
+
+
+### Public Speaking Resources
+
+* [Toastmasters Tips & Resources](https://www.toastmasters.org/resources)
diff --git a/job_seekers/resources/negotiations.md b/job_seekers/resources/negotiations.md
new file mode 100644
index 00000000..2a11a9c4
--- /dev/null
+++ b/job_seekers/resources/negotiations.md
@@ -0,0 +1,45 @@
+---
+layout: page
+title: Negotiations Resources
+---
+
+## A Non-Exhaustive List of Resources to Support with Negotiations
+
+### Start Here
+[Review the PD lesson on Negotiations](/module_four/negotiations)
+
+### General Research on Salary
+
+* [Glassdoor](https://www.glassdoor.com/index.htm)
+* [Payscale](https://www.payscale.com/)
+* [Blind Salary Comparison](https://www.teamblind.com/salaryComparison)
+* [81cents](https://www.81cents.com/)
+* [Stack Overflow Salary Calculator](https://stackoverflow.com/jobs/salary)
+* [Levels.fyi](https://www.levels.fyi/comp.html?track=Software%20Engineer) lets you search by company, location, and position level to see market value for salaries.
+
+### Understanding the Breakdown of Tech Salaries & Defining Strategies
+
+* [This post describes both the breakdown of common tech salaries & tips for negotiating](https://candor.co/guides/salary-negotiation)
+* [How to Negotiate Tech Job Offers](https://www.breakinto.tech/how-to-negotiate-salary-and-tech-job-offers)
+* [Negotiating the First Job Offer after Coding Bootcamp](https://derzorngottes.com/2020/02/23/negotiating-offer-first-coding-job/)
+* [Discussing Salary at any step of the Hiring Process](https://www.themuse.com/advice/salary-negotiations-hiring-process)
+* [What to Consider Before Negotiating](https://www.themuse.com/advice/6-things-you-need-to-figure-out-before-you-negotiate-salary)
+* [4 Things to Keep in Mind when Approaching Negotiations](https://www.themuse.com/advice/4-secrets-to-negotiating-a-salary-that-will-make-your-bank-account-smile)
+* [A list to build strategy from before, during, and after salary discussions](https://www.themuse.com/advice/how-to-negotiate-salary-37-tips-you-need-to-know)
+
+### Tips
+* [Fearless Salary Negotiations](https://fearlesssalarynegotiation.com/) provides tips and strategies for negotiating software offers.
+* [Tips from Recruiters](https://zapier.com/blog/how-to-negotiate-salary/)
+* [Tips for Negotiating as a Woman](https://www.washingtonpost.com/graphics/business/womens-wages/salary-negotiation-guide-women/?utm_term=.cc721527f9ac)
+* [Tips for Negotiating as a Black Woman](https://www.cnbc.com/2020/03/31/what-its-like-to-negotiate-salary-as-a-black-woman-equal-pay-day.html)
+* [Multiple Articles on Approaching Negotiations](https://www.themuse.com/advice/8-important-articles-to-read-before-you-start-negotiating-your-salary)
+* [The Salary Chronicles](https://www.forbes.com/sites/ericagellerman/?sh=5a0ea83913dd)
+
+### When You Get an Offer
+
+* [Use this Worksheet to walk through the steps](https://docs.google.com/document/d/17s-KWuoPFECqIFbp64wlG3P9bUbrQRTXha7tLnXU788/edit?usp=sharing)
+
+### Turing Salary Data
+* [Find latest Quarterly Salary Outcomes for Turing grads](https://turing.edu/outcomes/) and [more qualitative data on outcomes here](https://writing.turing.edu/tag/outcomes/)
+* [Averages for Contracts/Hourly Work](https://docs.google.com/spreadsheets/d/19KidjxU_8ux-oEzTRmYVPxT-zsonbjLaQ3KAijfDuyw/edit?usp=sharing)
+* Follow the #salaries channel on Slack
diff --git a/job_seekers/resources/outreach_networking_resources.md b/job_seekers/resources/outreach_networking_resources.md
new file mode 100644
index 00000000..41da0cd3
--- /dev/null
+++ b/job_seekers/resources/outreach_networking_resources.md
@@ -0,0 +1,66 @@
+---
+layout: page
+title: Outreach & Networking
+---
+
+Below are both resources and outlined steps for taking on outreach and networking for your job search.
+
+### Using Networking in your Job Search
+Check out this video from Jeff - "Your Job Is Not Advertised"
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/AqbfYxBEQyY" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+### Research Your Contacts
+* Start with LinkedIn
+  * [Check out this write-up from Ian on asking for Turing staff introductions to LinkedIn connections](https://gist.github.com/iandouglas/40e5c634b259de8512446bf76d3199e7)
+* Then, look for personal sites, blogs, Twitter, etc. to find out additional information
+* Take time to read and understand who you're contacting and analyzing what your ask is
+  * HINT: You're not asking for a job
+
+### Craft a Message
+* Introduce Yourself
+* Why are you reaching out? Connect to research
+* Suggest meeting times
+
+### Finding Emails
+* Start by searching the person's GitHub!
+* [Email Hunter](https://emailhunter.co/)
+* [Find That Lead](https://findthatlead.com/)
+* [MatterMark](https://mattermark.com/)
+* [Skrapp.io](https://www.skrapp.io/)
+* [Quickmail.io](https://quickmail.io/)
+* [Snov.io](https://snov.io/)
+* [RocketReach Browswer Extension](https://rocketreach.co/browser_extension)
+* Check the person's GitHub profile or look for their personal website
+
+### Prepare for Coffee Meetings
+* Using your research, prepare some questions to ask your contact
+* Start here:
+   * [Research Converation Questions](/module_four/research_conversation_questions)
+   * [Culture Queries Generator](https://www.keyvalues.com/culture-queries)
+   * [LOTS of Additional Questions](https://yangshun.github.io/tech-interview-handbook/questions-to-ask)
+   * End the conversation by asking, "who else from your network could you introduce me to?"
+
+### Try it out at Turing
+* Check out the #lets_grab_donuts channel on Slack to network with other students and Turing community members
+
+### Join Communities
+* [Here's a list of Slack tech communities by region and interest](https://github.com/ladyleet/tech-community-slacks)
+
+### Networking Groups
+* [BeVisible](https://www.bevisible.soy/) is a career network for Latinx.
+* [Black Data Processing Associates](https://www.bdpa.org/default.aspx) is an international organization for Black professionals in tech.
+* [Chezie.co](https://www.chezie.co/) is an online community for diverse professionals and students to connect with inclusive employers
+* [CodeNewbie](https://www.codenewbie.org/) is a community for newcomers to code.
+* [Diversify Tech](https://www.diversifytech.co/) is a community built to share upcoming conference scholarships, events, education scholarships, job opportunities, and more for people who are underrepresented in tech.
+* [Ladies Get Paid](https://www.ladiesgetpaid.com/join) allows you to connect with thousands of women from around the world to share advice, resources, and job opportunities.
+* [Lesbians Who Tech](https://lesbianswhotech.org/) is a career network for lesbians.
+* [Lunchclub](https://lunchclub.com/): Social networking platform that uses artificial intelligence and machine learning to connect users with common interests and objectives.
+* [MAES](http://mymaes.org/) was founded in Los Angeles in 1974 to increase the number of Mexican Americans and other Hispanics in the technical and scientific fields.
+* [National Society of Black Engineers](http://www.nsbe.org/home.aspx) is one of the largest student-governed organizations with the aim to increase the number of culturally responsible Black Engineers.
+* [Out in Tech](https://outintech.com/#welcome) is a community to connect LGBTQ+ in tech.
+* [TechLatino](http://techlatino.org/) is an organization to empower Latino technological and scientific engagement.
+* [Tech Ladies](https://www.hiretechladies.com/) is a community for women and non-binary folks. You have to apply to join, but once accepted, you'll have access to jobs from partnering companies.
+* [The Mom Project](https://themomproject.com/) is a community and job board that connects moms with companies that value and respect families and parents.
+* [Trans Tech Social Enterprises](https://www.transtechsocial.org/) is an incubator for LGBTQ Talent with a focus on economically empowering transgender people.
+* [Women in Web Dev](https://womeninwebdev.com/) is a community of women developers. 
diff --git a/job_seekers/resources/readme_resources.md b/job_seekers/resources/readme_resources.md
new file mode 100644
index 00000000..f54474ea
--- /dev/null
+++ b/job_seekers/resources/readme_resources.md
@@ -0,0 +1,14 @@
+---
+layout: page
+title: Resources for Writing Great READMEs
+---
+
+Check out some of these resources our instructors recommend:
+
+* Having trouble figuring out how to outline your README? [Check out this template](https://readme.so/editor) or [this template](https://github.com/PurpleBooth/a-good-readme-template)
+* [BE Mod 2 Lesson on Writing a great README](https://backend.turing.edu/module2/lessons/how_to_write_a_great_readme)
+* [Thoughtbot Blog Post: How to Write a Great README](https://thoughtbot.com/blog/how-to-write-a-great-readme)
+* [Dan Bader: How to Write a Great Readme for Your GitHub Project](https://dbader.org/blog/write-a-great-readme-for-your-github-project). Note: you may have to click x on the ad to get to the page
+* [TPW’s README-Driven-Development](https://www.google.com/url?q=http://tom.preston-werner.com/2010/08/23/readme-driven-development.html&sa=D&source=calendar&ust=1623259373515000&usg=AOvVaw2vFiJ7n-4VoFJz9Bn60PdS)
+* [Ponyfoo on README Driven Development](https://ponyfoo.com/articles/readme-driven-development)
+* [Jesse Luoto's How to Write a good README and Why You Should Care](https://thejunkland.com/blog/how-to-write-good-readme.html)
diff --git a/job_seekers/resources/resume_resources.md b/job_seekers/resources/resume_resources.md
new file mode 100644
index 00000000..55214449
--- /dev/null
+++ b/job_seekers/resources/resume_resources.md
@@ -0,0 +1,91 @@
+---
+layout: page
+title: Resume Resources
+---
+
+## Start Here
+If you haven't yet, make sure to go through the [technical resume lesson](/module_two/mod2_week1) in order to have more context for these resources and when to use them. 
+
+## General Advice
+
+* [Advice for Writing a Technical Resume](https://css-tricks.com/advice-for-writing-a-technical-resume/)
+* [How to Make the Perfect Resume](https://www.themuse.com/advice/how-to-make-a-resume-examples)
+* [Use JobScan to upload your resume and a job posting to see how it compares](https://www.jobscan.co/)
+
+## Create an ATS-ready Resume
+An ATS, or applicant tracking system, is used by most companies to screen resumes. Each ATS system is different -- when creating your resume, think about your audience, both in terms of content and the process of submitting the resume. **It's always important to follow the directions for that specific company**, but here are a few key components to keep in mind when creating a resume that is optimized for ATS systems:
+
+* Use a Word doc or a Google Doc (which can be downloaded as a Word doc) to use as your main copy. Not all ATS systems can read PDFs.
+* Use a single column. 
+* Compare your resume to the job description and pull out key words to highlight in your skills and experience. **An ATS system will not assume you have a skill unless you list it. If it's in the job description, add it to your skills.** [Learn more about how to approach ATS systems here](https://www.jobscan.co/applicant-tracking-systems).
+* Need some inspiration? Check out these [free resume templates from JobScan](https://www.jobscan.co/resume-templates) or [from Job Hunt](https://www.job-hunt.org/resume-samples/sample-resumes.shtml)
+
+
+## Resume Checklist
+When creating your resume, check out this checklist to make sure you've included the right information:
+
+### Order of Content
+- [ ] Heading/Contact, Summary, Skills, Projects, Experience/Education
+
+### Heading & Contact Info
+- [ ] Name: stand outs, easy to read
+- [ ] Title: "software developer/front end engineer/back end engineer," stand outs, easy to read, comparable in size to name 
+- [ ] Email address
+- [ ] Phone number (optional)
+- [ ] GitHub link 
+- [ ] LinkedIn link 
+- [ ] Personal website (optional)
+
+#### Summary/Profile (Optional)
+We strongly recommend using a summary if you do not have a lot of previous work experience. 
+
+- [ ] Provides a brief description of the student's career change to software and how they will use their previous skillset with their new skillset
+- [ ] If for a specific position, the summary is tailored accordingly (instead of discussing general interest in software, summary addresses interest in specific job/company)
+- [ ] Clear and concise
+- [ ] No grammatical or spelling errors
+
+### Skills
+- [ ] Skills listed are technical. **Do not** include "soft skills" or professional skills here -- add them to your experience descriptions 
+- [ ] Skills are grouped logically by type
+- [ ] No grammatical or spelling errors
+- [ ] Section for skills learning/interested in (optional)
+- [ ] If for a specific position, skills are tailored accordingly
+- [ ] Skills do not include hobbies or other extraneous details
+
+### Projects
+- [ ] At least 3 projects are listed
+- [ ] All projects are presented in the same format
+- [ ] Title is included
+- [ ] Technologies, frameworks, testing suite, etc. are all listed as bullet points
+- [ ] 1-2 sentences of a brief description of the project is provided as a high level overview of what the project is and how it works
+- [ ] Active link to project repository with a visual cue that it's a link
+- [ ] Active link to deployed application with a visual cue that it's a link
+- [ ] Links should go to student's own version of repo and not their project partner's, if applicable
+- [ ] No grammatical or spelling errors
+
+### Experience
+- [ ] Turing can be listed here and under experience but only if you have limited work experience or gaps in employment. Otherwise, use that space to highlight professional experience from prior roles. The technical experience section will provide a good amount of techncial work for the reader. 
+- [ ] Amount of space "Experience" section takes up on the page is less than that of the "Projects" section
+- [ ] Formatted with job title followed by company name
+- [ ] Brief description of role and what value you brought to the company
+- [ ] Include any quantified or results-driven experience
+- [ ] No grammatical or spelling errors
+
+### Education
+- [ ] Turing is listed here as you can say you received a "Certificate of completion in [Back]/[Front]-End Engineering"
+- [ ] Brief description of area of study or skills that can relate to software development or specific job applying to
+- [ ] Add in any leadership or extracurricular activities you participated in (SLC, Student Circles, etc.)
+- [ ] No grammatical or spelling errors
+
+### Proofread
+- [ ] Clean, easy-to-follow
+- [ ] Fonts and text-sizing are consistent
+- [ ] If color is used, it is easy to read and distinguish all parts of the resume 
+- [ ] Printable or ATS-ready version
+- [ ] No photo
+- [ ] No extraneous details/sections (no personal interests, "looking for" sections, etc.)
+- [ ] Resume is only one page
+- [ ] Remove any first person pronouns (I, me)
+
+## Submitting Your Resume
+If submitting through an ATS system, submit a word doc. If submitting a resume through an email, attach a PDF. Again, every company is different. If you're unsure of how to approach an application, reach out to your Career Specialist. 
diff --git a/job_seekers/resources/terminal_directions.md b/job_seekers/resources/terminal_directions.md
new file mode 100644
index 00000000..49dfd002
--- /dev/null
+++ b/job_seekers/resources/terminal_directions.md
@@ -0,0 +1,99 @@
+---
+layout: page
+title: Terminal Portfolio Directions
+---
+
+## Overview
+Turing provides a space for professional portfolios on [our website](https://terminal.turing.edu/profiles). These portfolios can be used during your job hunt - you can send out links to your profile, and Turing staff may share your profile to employers who come to us asking for candidates.
+
+### How to Set It Up
+You will receive an email invitation from the Career Dev team inviting you to create a Terminal profile. If you have not received this invite, you can request an invite by reaching out to Megan McMahon - @megan on slack. 
+
+To set up your profile: 
+* Log into Terminal at [https://terminal.turing.edu/developers/sign_in](https://terminal.turing.edu/developers/sign_in)
+* Go to “Edit Profile” from account menu
+* Fill out profile until all sections are complete
+* A Career Specialist will review your profile and approve for publishing or request additional changes
+* For more info on how to set this up, [watch this demo](https://drive.google.com/file/d/1NqHrdkr0B5wEvEaH9Z8dJK56TcSJoV_t/view)
+
+### When your profile is complete:
+* Make sure you've met the [requirements for publication](https://careerdev.turing.edu/resources/terminal_directions).
+* Click “Request Review”  
+* A Career Specialist will review your profile and approve for publishing or request additional changes to be completed before it can be published.
+
+Once published, your profile will be visible on the main alumni directory at [terminal.turing.edu/profiles](https://terminal.turing.edu/profiles) as long as you are participating in job search support until you get your first job. While you are actively job searching, the Career Dev team will use your portfolio in referrals to companies. 
+
+### About Me Section
+What do you want your profile to say about you? Write out a rough draft of your professional story considering using this framework:
+
+* What is your career story about your past, present, and future that you want to share with employers? 
+* What prior experiences are relevant and transferrabe to the tech industry?
+* What impact you want to have in software development?
+* What kind of company and culture are you passionate about adding value for?
+
+In this section, make sure to answer the following questions:
+
+* Who am I? 
+* Why am I in this field? 
+* What's next for me? 
+
+Show readers who you are by telling a story of your journey into tech. Share enough for them to want to hear and learn more! 
+
+Your Terminal about me section, LinkedIn summary, and resume summary (if you chose to use one) should all be slightly different. 
+
+* First, you want the reader to learn something new with each profile
+* Second, each summary has a different purpose; think about the audience
+  * Resume summaries should tell why you are the best candidate for the role relevant to the job description. 
+  * LinkedIn summaries allows you to add a personal touch in addition to relevant skills and experiences that will attract recruiters and hiring managers.
+  * Terminal is similiar to the LinkedIn audience; employers want to know your backstory, your value proposition and what's next for you as a developer. 
+
+### Project Descriptions
+The main recommendation here is to remember that you are speaking to potential employers, not investors. These project descriptions should briefly describe the project, and then quickly pivot to describing your primary contributions and the things you learned. This is an advertisement for you, not the project.
+Be consistent in your project descriptions. Too often students use different formats and headings for each of their project descriptions. It can help your audience of potential employers to quickly digest this information if you are even consistent between projects in the order in which you provide information.
+
+For example:
+
+* **First sentence:** name of project, number of collaborators, primary technologies used, what it does.
+* **Second sentence:** main learning goals of the project/the things you were doing for the first time in this project (if you don’t know, ask your instructors).
+* **Third sentence:** any stretch goals you were able to achieve.
+* **Fourth sentence:** anything you specifically focused on in the project.
+
+[Find more specifics on how to approach your project descriptions here](https://docs.google.com/document/d/1zKePxhD-xQdLRPeLI21E71ET_U88ZZ-SKTQjRVzs8tM/edit?usp=sharing).
+
+### Getting Your Portfolio Published
+What needs to be included in order for your portfolio to be published? Here is what the team is looking for:
+
+- [ ] **Title**
+- [ ] **Professional-looking photo** 
+   - [ ] This should be a photo of just you (no kids or animals, sorry!)
+   - [ ] Use the same photo as your LinkedIn and GitHub profiles if possible
+   - [ ] Don't have a professional-looking photo? [Check out this post](https://writing.turing.io/how-to-take-your-own-linkedin-headshot/) for tips on how to take one at home  
+- [ ] **About Me Description**
+   - [ ] Tell your professional story
+   - [ ] Consider how this is consistent with your LinkedIn and overall brand
+   - [ ] If you’re struggling with writing this and need additional support, please contact your mentor and/or members of the career development team
+   - [ ] Check out your peers’ About Me sections to see what you like and don’t like on [Terminal](https://terminal.turing.edu)
+   - [ ] Make sure to have someone else review this section for clarity, spelling, and grammar  
+- [ ] **Email address**
+- [ ] **GitHub profile**
+- [ ] **LinkedIn profile**
+- [ ] **Polished draft of resume**
+- [ ] **Preferred Locations**
+- [ ] **Previous Industries**
+   - [ ] Limit to 5 previous industries. If you are concerned about this, please reach out to your Career Specialists.  
+- [ ] **Skills**
+- [ ] At least **2 projects** 
+   - [ ] Show variety: paired, team, individual 
+   - [ ] Include an estimation of project contribution hours
+   - [ ] Include screenshots
+   - [ ] Tools Used    
+   - [ ] Code Repository Link
+
+Nice to have but not required for initial publication:
+* Pronouns
+* Skills you are currently learning
+* Twitter profile
+* Project collaborators
+* Deployed Project link
+
+If you have any questions about this portfolio, please reach out to the Career Development team!
diff --git a/job_seekers/resources/veteran_resources.md b/job_seekers/resources/veteran_resources.md
new file mode 100644
index 00000000..48b1cfde
--- /dev/null
+++ b/job_seekers/resources/veteran_resources.md
@@ -0,0 +1,18 @@
+---
+layout: page
+title: Resources for Veterans
+---
+
+Find resources here specifically for veterans:
+
+### Networking
+* [Vets in Tech](https://vetsintech.co/) supports current and returning veterans with re-integration services and through connections to the national technology ecosystem.
+* [Free 1-year Premium subscription to LinkedIn](https://socialimpact.linkedin.com/programs/veterans/premiumform)
+* [1 hour mentorship resource for all veterans about any subject](https://www.veterati.com). How it works: You set up a profile, and then search for mentors you want to chat with - there’s an automated call feature that connects you at a pre-determined time. I’ve probably had over 30 calls with vets in the industry.
+
+### Training, Upskilling, & Career Counseling
+* [CSS Learning Academy](https://ccslearningacademy.com/veteran-training-career-resources) provides resources and training for veterans if you want to add to your technical skillset
+* [Vetd Talent Network](www.vetdtalentnetwork.co) is a platform that highlights our military's top talent, promotes professional development opportunities, and builds vital relationships in the business community. 
+* [American Corporate Partners](https://www.acp-usa.org/) provides corporate career counseling to support in the transition from the military to the civilian workforce. 
+* [VetSec](https://veteransec.com/) is a nonprofit helping verterans enter careers in cybersecurity
+* Check out a sponsorship or mentorship opportunities at [Operation Code](https://operationcode.org/)

From 0387a548fd8856e5215723657e6c0b405f47d3a0 Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Tue, 14 May 2024 16:13:11 -0600
Subject: [PATCH 05/15] Remove FE PD

---
 module1/pd/index.md | 4 ----
 module2/pd/index.md | 4 ----
 module3/pd/index.md | 4 ----
 3 files changed, 12 deletions(-)
 delete mode 100644 module1/pd/index.md
 delete mode 100644 module2/pd/index.md
 delete mode 100644 module3/pd/index.md

diff --git a/module1/pd/index.md b/module1/pd/index.md
deleted file mode 100644
index 5699b929..00000000
--- a/module1/pd/index.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-layout: page
-title: Module 1 - Professional Development
----
\ No newline at end of file
diff --git a/module2/pd/index.md b/module2/pd/index.md
deleted file mode 100644
index 3901b6c5..00000000
--- a/module2/pd/index.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-layout: page
-title: Module 2 - Professional Development
----
\ No newline at end of file
diff --git a/module3/pd/index.md b/module3/pd/index.md
deleted file mode 100644
index f88abdef..00000000
--- a/module3/pd/index.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-layout: page
-title: Module 3 - Professional Development
----

From 3566860d9e5668492fd09ac745dd53497a85d9de Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Thu, 16 May 2024 14:17:32 -0600
Subject: [PATCH 06/15] Remove separate PD pages

---
 module1/index.md    | 5 ++---
 module2/index.md    | 5 ++---
 module3/index.md    | 5 ++---
 module4/index.md    | 5 ++---
 module4/pd/index.md | 4 ----
 5 files changed, 8 insertions(+), 16 deletions(-)
 delete mode 100644 module4/pd/index.md

diff --git a/module1/index.md b/module1/index.md
index 706b53d2..922a7249 100644
--- a/module1/index.md
+++ b/module1/index.md
@@ -7,8 +7,7 @@ subheading: Fundamentals of Programming
 ## Overview
 
 ## Curriculum
-- [Technical Lessons](./lessons/index.md)
-- [Technical Projects](./projects/index.md)
-- [Professional Development](./pd/index.md)
+- [Lessons](./lessons/index.md)
+- [Projects](./projects/index.md)
 
 ## Other Resources
diff --git a/module2/index.md b/module2/index.md
index ce5e80f7..643cc47b 100644
--- a/module2/index.md
+++ b/module2/index.md
@@ -8,8 +8,7 @@ subheading: Web Applications with Ruby
 
 ## Curriculum
 - [Intermission Pre-Work](./intermission_work/index.md)
-- [Technical Lessons](./lessons/index.md)
-- [Technical Projects](./projects/index.md)
-- [Professional Development](./pd/index.md)
+- [Lessons](./lessons/index.md)
+- [Projects](./projects/index.md)
 
 ## Other Resources
\ No newline at end of file
diff --git a/module3/index.md b/module3/index.md
index f96f3957..a0c22ae2 100644
--- a/module3/index.md
+++ b/module3/index.md
@@ -8,8 +8,7 @@ subheading: Building and Consuming APIs
 
 ## Curriculum
 - [Intermission Pre-Work](./intermission_work/index.md)
-- [Technical Lessons](./lessons/index.md)
-- [Technical Projects](./projects/index.md)
-- [Professional Development](./pd/index.md)
+- [Lessons](./lessons/index.md)
+- [Projects](./projects/index.md)
 
 ## Other Resources
\ No newline at end of file
diff --git a/module4/index.md b/module4/index.md
index 0a1a6501..7bc3736c 100644
--- a/module4/index.md
+++ b/module4/index.md
@@ -8,8 +8,7 @@ subheading: Finding Your Specialty
 
 ## Curriculum
 - [Intermission Pre-Work](./intermission_work/index.md)
-- [Technical Lessons](./lessons/index.md)
-- [Technical Projects](./projects/index.md)
-- [Professional Development](./pd/index.md)
+- [Lessons](./lessons/index.md)
+- [Projects](./projects/index.md)
 
 ## Other Resources
\ No newline at end of file
diff --git a/module4/pd/index.md b/module4/pd/index.md
deleted file mode 100644
index cf3da20d..00000000
--- a/module4/pd/index.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-layout: page
-title: Module 4 - Professional Development
----

From b97924a1d74df3d7c5c7247cd9778856f0ca3fd9 Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Thu, 16 May 2024 14:21:16 -0600
Subject: [PATCH 07/15] Add M1 PD lessons

---
 module1/lessons/index.md               | 64 +++++++++++--------
 module1/lessons/learning_to_pair.md    | 85 ++++++++++++++++++++++++++
 module1/lessons/pd_overview.md         |  8 +++
 module1/lessons/productive_struggle.md | 40 ++++++++++++
 module1/lessons/writing_a_readme.md    | 44 +++++++++++++
 5 files changed, 214 insertions(+), 27 deletions(-)
 create mode 100644 module1/lessons/learning_to_pair.md
 create mode 100644 module1/lessons/pd_overview.md
 create mode 100644 module1/lessons/productive_struggle.md
 create mode 100644 module1/lessons/writing_a_readme.md

diff --git a/module1/lessons/index.md b/module1/lessons/index.md
index 60280cdc..5fb178c7 100644
--- a/module1/lessons/index.md
+++ b/module1/lessons/index.md
@@ -6,38 +6,48 @@ title: Module 1 - Lessons
 <!-- Comment the following lessons in as they are updated and deemed ready to go! -->
 
 ## Ruby Mechanics
-<!-- - [Methods & Return Values](./methods_and_return_values.md) -->
-<!-- - [Objects, Classes, & Instances](./objects_classes_instances.md) -->
-<!-- - [Arrays](./arrays.md) -->
-<!-- - [Scope](./scope.md) -->
-<!-- - [Flow Control](./flow_control.md) -->
-<!-- - [Beginner Enumerables](./beginner_enumerables.md) -->
-<!-- - [Hashes](./hashes.md) -->
-<!-- - [Boolean Logic](./boolean_logic.md) -->
-<!-- - [Nested Collections](./nested_collections.md) -->
-<!-- - [Reaching Through Objects](!needs lesson plan!) -->
-<!-- - [Intermediate Enumerables](./intermediate_enumerables.md) -->
-<!-- - [Nested Iteration Workshop](./nested_iteration_workshop.md) -->
-<!-- - [Class Methods](./class_methods.md) -->
-<!-- - [Modules](./modules.md) -->
-<!-- - [Inheritance](./inheritance.md) -->
-<!-- - [CSV Workshop](./csv_walkthrough.md) -->
-<!-- - [Ruby Object Model](./ruby_object_model.md) -->
+<!-- * [Methods & Return Values](./methods_and_return_values.md) -->
+<!-- * [Objects, Classes, & Instances](./objects_classes_instances.md) -->
+<!-- * [Arrays](./arrays.md) -->
+<!-- * [Scope](./scope.md) -->
+<!-- * [Flow Control](./flow_control.md) -->
+<!-- * [Beginner Enumerables](./beginner_enumerables.md) -->
+<!-- * [Hashes](./hashes.md) -->
+<!-- * [Boolean Logic](./boolean_logic.md) -->
+<!-- * [Nested Collections](./nested_collections.md) -->
+<!-- * [Reaching Through Objects](!needs lesson plan!) -->
+<!-- * [Intermediate Enumerables](./intermediate_enumerables.md) -->
+<!-- * [Nested Iteration Workshop](./nested_iteration_workshop.md) -->
+<!-- * [Class Methods](./class_methods.md) -->
+<!-- * [Modules](./modules.md) -->
+<!-- * [Inheritance](./inheritance.md) -->
+<!-- * [CSV Workshop](./csv_walkthrough.md) -->
+<!-- * [Ruby Object Model](./ruby_object_model.md) -->
 
 ## Design
-<!-- - [Design Principles](./design_principles.md) -->
-<!-- - [How the Web Works](./intro_to_how_the_web_works.md) -->
+<!-- * [Design Principles](./design_principles.md) -->
+<!-- * [How the Web Works](./intro_to_how_the_web_works.md) -->
 
 ## Testing
-<!-- - [Intro to Testing](./intro_to_testing.md) -->
-<!-- - [Mocks & Stubs](./mocks_stubs.md) -->
-<!-- - [Test Driven Development](./test_driven_development.md) -->
+<!-- * [Intro to Testing](./intro_to_testing.md) -->
+<!-- * [Mocks & Stubs](./mocks_stubs.md) -->
+<!-- * [Test Driven Development](./test_driven_development.md) -->
 
 ## Debugging
-<!-- - [Debugging Exercises](!needs lesson plan!) -->
-<!-- - [Debugging Techniques](./debugging_techniques.md) -->
+<!-- * [Debugging Exercises](!needs lesson plan!) -->
+<!-- * [Debugging Techniques](./debugging_techniques.md) -->
 
 ## Version Control
-<!-- - [Git Workflow](./git-collaboration.md) -->
-<!-- - [Git for Pairs](./git_for_pairs.md) -->
-<!-- - [Git Cheat Sheet](./git_cheatsheet.md) -->
+<!-- * [Git Workflow](./git-collaboration.md) -->
+<!-- * [Git for Pairs](./git_for_pairs.md) -->
+<!-- * [Git Cheat Sheet](./git_cheatsheet.md) -->
+
+## Professional Development
+* [Overview](./pd_overview)
+* [Asking Good Questions](https://docs.google.com/presentation/d/e/2PACX-1vQEDGBpYDQA6_hBHfWcjk4pUheFe2_bkYRPXF9b-YhNlua-oq4Y7WZCcIpOAuQfeaswRp414TIvIOXA/pub?start=false&loop=false&delayms=3000)
+* [Learning to Pair](./learning_to_pair)
+* [Giving and Receiving Feedback](https://docs.google.com/presentation/d/e/2PACX-1vQvHkaNO1HTKSrk7kCVhPftCu4vaBlWMEFVuej6LsAA7ICN2_QkO-GTAWNOwYDG0cepSSEBmHNcb8Ry/pub?start=false&loop=false&delayms=3000&slide=id.g1c505a3b55_0_0)
+* [Professional Storytelling](https://docs.google.com/presentation/d/e/2PACX-1vT6pK3pGHy9HrnvW4FCwRGJXqbuDM76LRcA-a26mOo5t7wi2WXLy4T8VE3R7fM3wYgxS4uLZ4f1RtXu/pub?start=false&loop=false&delayms=3000)
+* [Productive Struggle](./productive_struggle)
+* [Writing Mod 1 READMEs](./writing_a_readme)
+* [Project DTR](https://docs.google.com/document/d/1HFWSZExSWgGJdqLkEH4DXs-z1gZxMNkv4n1NO9U1eJU/edit?usp=sharing)
\ No newline at end of file
diff --git a/module1/lessons/learning_to_pair.md b/module1/lessons/learning_to_pair.md
new file mode 100644
index 00000000..39316d3a
--- /dev/null
+++ b/module1/lessons/learning_to_pair.md
@@ -0,0 +1,85 @@
+---
+title: Learning to Pair
+length: 60
+tags: pairing, driver navigator, paired programming
+---
+
+# Overview
+
+Paired Programming is a very common method of programming. Some companies pair 100% of the time! At other companies you may program solo, but pair 50% of the time when working on a particulary complex problem or if you're learning something new.
+
+Learning to pair is an essential skill of being a well-rounded developer. This guideline covers:
+- the advantages of pairing.
+- establishing a DTR.
+- different pairing strategies.
+
+# The Why
+Reasons why pairing is beneficial (to you and the team):
+- Knowledge share: more people on the team understand the code that is being written and why.
+- Less errors: with two pairs of eyes on the code, more errors and bugs will be caught quicker.
+- Learn from others: sharing ideas and hearing other perspectives on writing code will expand your toolset for how to problem solve. You may learn something new from your partner!
+- Team cohesion: pairing will allow you to get to know your team better.
+
+
+# DTR
+When forming a new paired team or group, it's important to start off by talking through expectations, limitations, and boundaries _before_ jumping into any code. At Turing, we do this with a DTR (Define the Relationship.)
+
+[DTR Template](https://docs.google.com/document/d/1HFWSZExSWgGJdqLkEH4DXs-z1gZxMNkv4n1NO9U1eJU/edit)
+
+Moving forward, all Turing paired and group projects will start with a DTR. 
+
+*Tips for best utilizing your DTR*
+- Keep DTR in a shared place that's easy to access by all team members.
+- Refer to and refine the DTR often throughout the project. 
+- If an issue arises within the group, refer to the DTR for how to handle the situation. If the DTR doesn't cover this situation, add guidelines for how you and your team will handle this type of situation moving forward. 
+
+The DTR is a fluid, living, breathing document designed to help mitigate problems before they happen.
+
+
+# Communication
+Another important component of pairing is communication. How well you communicate and work with other developers can be what sets you apart in a job interview. 
+
+**Stand Ups**
+
+We recommend having a "stand up" meeting every morning with your partner (or team) to discuss what you worked on yesterday, what you will be working on today, and any blockers you are having or forsee. 
+
+* Note: a "stand up" is called a "stand up" because you have this meeting while standing and if you get tired of standing, the meeting has gone too long! These stand ups should only last 5-10 minutes. If further discussion is required, you can schedule a time to meet and discuss the issue later in the day.
+
+**Retros**
+
+Make time to reflect on progress, group dynamics, and the DTR. A _retro_ (retrospective) is a time to meet as a team and reflect. We recommend doing a retro every 3 days to discuss: What is going well? Any issues (communication/working style/schedule) that need to be addressed? 
+Create a solution together and document this in the DTR.
+This is a great time to give feedback to your partner. Whenever giving feedback, make sure your it is specific, actionable, and kind.
+
+# Pairing Strategies
+
+**Driver/Navigator**
+- Working together at the same time, in the same "place" (zoom counts as a place)
+- Shared screen
+- **Driver:** the team member that is typing
+- **Navigator:** the team member guiding the code solution
+- BOTH members should be collaborating on how they are thinking about solving the problem/asking questions
+- Timebox so members can switch roles
+
+**Ping Pong**
+- Embraces the TDD (Test Driven Development) approach
+- **Ping:** team member 1 writes a test for intended functionality
+- **Pong:** team member 2 writes the implementation code to make the test pass
+- Switch Roles
+- Great for working together, but not at the same time or the same place.
+
+# Working Together via Github
+- Use a branching workflow
+- Use Pull Requests
+  - Do not merge your own PR
+  - Partner should review your code on the PR, discuss any questions or suggestions using github comments on the PR (hop on a call/zoom if further discussion is needed)
+  - After all questions have been resolved, your partner can merge the PR into the main branch
+
+
+# Summary
+- Communication is key throughout the entire process.
+- Working together helps improve both professional and technical skills.
+- Pairing takes practice. Figuring out how to work with others and understanding your own needs for how you work best is a process and may change due to circumstances. Use this time at Turing to practice and refine how you work best as a developer.
+- Remember everyone is here to learn. "If you want to go fast, go alone. If you want to go far, go together."
+- Do not limit your own learning or that of others by working alone.
+- We are all humans and individuals. Pairing will not go smoothly 100% of the time. Remember to ask questions before making assumptions.
\ No newline at end of file
diff --git a/module1/lessons/pd_overview.md b/module1/lessons/pd_overview.md
new file mode 100644
index 00000000..55bf07b2
--- /dev/null
+++ b/module1/lessons/pd_overview.md
@@ -0,0 +1,8 @@
+---
+layout: page
+title: PD Overview
+---
+
+Through engaging in and reflecting on a rigorous, collaborative, academic environment, students will inherently continue to develop their self-awareness in this space. Students will also organically use and develop communication and collaboration skills, which will be supported by live sessions (*Giving and Receiving Feedback* and *Learning to Pair*) and group projects which center around how students work together. Students will regularly reflect on their growing professional and technical skills in their *Project Reflections*. Students will engage in a live session on crafting a professional story, and then have a space to workshop their story with peers and staff.
+
+*Students will demonstrate professional readiness to move to Mod 2 by sharing their professional story and reflections on their growth in self-awareness, communication, and collaboration in their Final Portfolio Review.*
\ No newline at end of file
diff --git a/module1/lessons/productive_struggle.md b/module1/lessons/productive_struggle.md
new file mode 100644
index 00000000..509c5c25
--- /dev/null
+++ b/module1/lessons/productive_struggle.md
@@ -0,0 +1,40 @@
+---
+layout: page
+title: Productive Struggle
+length: 60
+tags: process
+---
+
+## Two Types of Struggle
+
+When working through a challenge - in programming or otherwise.  We often find ourselves struggling to understand the problem, or developing a solution.  This struggle isn't bad, its just part of the process!  But, there are different ways of struggling through a problem - some more productive than others.  We can generally group these behaviors under either **Productive Struggle** or **Unproductive Struggle**.  Productive struggle moves you closer to your goal, while unproductive struggle is stagnant, or can even move you further from your goal.
+
+### Identifying Productive Struggle
+
+With your breakout group, the tallest person will share their screen and take notes as you brainstorm. Create a chart listing out behaviors that indicate when you are in productive struggle, and when you are in unproductive struggle. Take 8 minutes to just list the behaviors for each form of struggle - we’ll work on strategies for avoiding unproductive struggle next.
+
+Once you have your list, take another 8 minutes to brainstorm ways to avoid unproductive struggle, and ways to move from unproductive to productive struggle. Create a separate chart listing out these strategies.
+
+## Strategies for Breaking out of Unproductive Struggle
+
+**Clarify the Problem**  
+Revisit the project spec, interaction pattern, or any supporting documents to clarify the problem you are working on.  Ask questions if necessary, and restate the problem to yourself and others to make sure you are working on the correct task.
+
+**Think Out Loud**  
+Sometimes referred to as *Rubber Ducking*. It can often help to talk through what you are trying to do out loud - either to yourself or to another person.  Just saying something out loud can help you identify where you have made a wrong move.
+
+**Take Notes**  
+Write done what you know and what you have tried.  Writing down what you know (what variables you have access to, what datatypes you are working with, what the return value of a method should be) helps focus you on the problem at hand, without getting caught up in other things.  Keeping track of what you have tried and the result of those attempts can help you keep moving forward without re-trying things that you have already seen didn't work.  It will also help others follow your logic if you need to ask for help!
+
+**Try a Different Method**  
+This might seem like common sense, but it is also a common trap that we can get into - we want so much to use a specific method, that we can tie ourselves to something that isn't going to work.  For example - if you are using `.map` and it isn't working, try `.each`.  Focus on getting it working, rather than on using the *right* method.
+
+**Nuke It**  
+CODE IS CHEAP. It's a tough lesson to learn, but a good one-- it costs nothing to delete and start over. All developers sometimes get stuck trying to force our code into a strategy, tool, or path that we're mentally stuck on and determined to make work. And sometimes, that just isn't the right direction.  It's okay (and sometimes, the best course of action) to delete what you've written, take a 5 minute pom, and start fresh when you get back as though it's the first time you've seen the problem. (Disclaimer: we're not talking about a whole project here-- don't delete your whole project the night before it's due).
+
+**Ask for Help**  
+Early! Don't spend too much time struggling before asking for help-- if you've spent more than 20 minutes on unproductive struggle, ask a fellow student, mentors, upper mod students and/or your instructors.
+
+
+### Remember
+Unproductive struggle is independent of how long it takes you to find a working solution.  It _is_, however, recognizing when you've stopped learning.
diff --git a/module1/lessons/writing_a_readme.md b/module1/lessons/writing_a_readme.md
new file mode 100644
index 00000000..ee4445c5
--- /dev/null
+++ b/module1/lessons/writing_a_readme.md
@@ -0,0 +1,44 @@
+---
+title: Understanding and Writing a README for Mod 1 Projects
+tags: projects, readme, technical writing, mod 1
+---
+
+## What is a README?
+
+A README is a file that contains the important information about a project. It is called a README because it should be the first file that is opened and should guide the reader in understanding how to use the project. Think of it as an instruction manual for the user. In this case our user is other developers.
+
+Your Mod 1 projects will include a README that is written in Markdown, which is why it has the `.md` extension. If you want to learn more about Markdown here are some resources to get you started:
+- [What is Markdown](https://www.ultraedit.com/company/blog/community/what-is-markdown-why-use-it.html)
+- [Mastering Markdown](https://guides.github.com/features/mastering-markdown/#:~:text=Markdown%20is%20a%20way%20to,in%2C%20like%20%23%20or%20*%20.)
+- [Markdown Cheat Sheet](https://www.markdownguide.org/cheat-sheet/)
+
+### Why should YOU write a README?
+Now that you understand the purpose behind the README, how does it more direclty relate to you. Writing READMEs is an opportunity for you to practice organizing information, writing technical documentation, and reflecting on your project and process. These skills will be essential for interviewing and on the job.
+
+### What to include in the README?
+For your project READMEs, you should oragnize the information so that it is clear and easy to follow. It should be broken into sections to help the reader more easily understand and find information. Let's break down what sections you should be including in your Mod 1 README.
+- __About__
+    - Should be a breif summary of what is the application. 
+- __Built With__
+    - Include the Ruby and RSpec version here.
+- __Getting Started__
+    - Breakdown the set-up instructions. Start with how to clone down the application and include all the steps necessary to run it locally. 
+    - _Not sure if you missed something? Ask a peer to follow your directions exactly to see if they can run the application._
+- __Testing__
+    - Give directions for how to run your tests. 
+    - Explain how your tests are organized.
+    - Provide a summary of the types of tests that you've written and why those tests are vaulable to the application.
+- __Challenges & Wins__
+    - Reflect on your process and what you have learned in the project. 
+    - What were the challenges you experienced? 
+    - How did you overcome them? 
+    - How will this experience benefit you in future projects?
+- __Authors__ (Optional)
+    - If you worked in a pair or group, give those partners recognition!
+    - Make their name a link to their GitHub Account.
+
+### What next?
+Now, it is time for you to go write an awesome README!
+
+####  _Feeling extra fancy?_ 
+Check out these resources for how to include [badges](https://shields.io/) and [visual recordings](https://asciinema.org/).
\ No newline at end of file

From 9e57d3021742fdaac5d067799fa998396c89640f Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Thu, 16 May 2024 14:24:12 -0600
Subject: [PATCH 08/15] Add M2 PD lessons

---
 module2/lessons/index.md       |   6 +
 module2/lessons/networking.md  | 295 +++++++++++++++++++++++++++++++++
 module2/lessons/pd_overview.md |   8 +
 3 files changed, 309 insertions(+)
 create mode 100644 module2/lessons/networking.md
 create mode 100644 module2/lessons/pd_overview.md

diff --git a/module2/lessons/index.md b/module2/lessons/index.md
index a0b34bea..1e9a5b2b 100644
--- a/module2/lessons/index.md
+++ b/module2/lessons/index.md
@@ -3,3 +3,9 @@ layout: page
 title: Module 2 - Lessons
 ---
 
+## Professional Development
+* [Overview](./pd_overview)
+* [Building Your Brand on LinkedIn](https://docs.google.com/presentation/d/e/2PACX-1vS8CZUjYkpnkTJrp2Ga8um-UUFUsJ-5JA85FF9x875J-l_eKy7IyL47sAt8kl_FOlg7rG5ntVxpk5he/pub?start=false&loop=false&delayms=3000)
+* [Networking, Outreach and Coffee Chats](./networking.md)
+* [Networking](https://docs.google.com/presentation/d/e/2PACX-1vQa672IV-XwWG9q-ujEJ0w72QCBzf4jVMNI-trwLuKt9kk_ewe0l6Mk6YSWoo9UYMETbJ5RZ3akKyux/pub?start=false&loop=false&delayms=3000)
+* [Getting Job Hunt Ready](https://docs.google.com/presentation/d/e/2PACX-1vTDlRAiXiR_PSsAFGQtP8je_pcUWmLdk1kYc4jO4hTyzxDuksNWUMdUITMNXp1pRFMM0gKDiAVyXL0c/pub?start=false&loop=false&delayms=3000)
\ No newline at end of file
diff --git a/module2/lessons/networking.md b/module2/lessons/networking.md
new file mode 100644
index 00000000..ecee5499
--- /dev/null
+++ b/module2/lessons/networking.md
@@ -0,0 +1,295 @@
+---
+layout: page
+title: Networking, Outreach and Coffee Chats
+---
+
+# Networking
+
+Networking is another word for building relationships. When you’re networking, you’re actively getting to know someone and they’re getting to know you. As you get to know each other, you’re finding ways to mutually benefit each other, which is something you do in all relationships. For example, mutual benefits in friendships often revolve around support, common interests, and social interaction.
+
+It’s important to recognize what you could gain through networking interactions while at Turing – these might include support and advice as well as reconnecting with those in your existing network. Every relationship has a giving and receiving quality to it, and networking is a little more blatant about it. While you’re receiving support and advice, you can benefit the relationship by spending time really getting to know the other person and their goals so that you can return the favor at a later time.
+
+## Assessing Your Comfort Level in Networking
+
+It can also be helpful to understand what types of interactions energize you and what drain you. Often we think that introverts are shy and extroverts are outgoing. But in reality, everyone exists on the spectrum of introversion and extroversion, and our place on that spectrum can change depending on our current circumstances.
+
+There are many ways to connect with people in networking situations. Which interactions listed here would energize you and which would drain you?
+
+* Online communication
+* Meeting people in person
+* 1:1 interactions
+* Casual group conversations
+* Seeking people out on your own
+* Getting introduced by someone else (an event buddy)
+
+Once you are able to identify what energizes you, lean into it! Find ways to capitalize on this energy. Here are some examples:
+
+### Example #1: Networking through social media
+
+If you feel energized by engaging in social networking over Twitter or LinkedIn, here are some tips to maximize the impact of the interactions:
+* Build a robust profile to allow others to get to know you. Note: here are some [resources for personal branding](https://careerdev.turing.edu/resources/branding_resources).
+* Seek out people who share your interests. Interested in artificial intelligence? Block chain? Diversity, equity, and inclusion in tech? Find your people. Check out hashtags, influential people or companies in your field, and other current conversation threads to join in.
+* Don’t leave one-off comments or “likes.” Take time to engage in conversation, listen to others, share helpful resources – just like you would in any conversation.
+
+### Example #2: Networking at organized events
+
+If you feel energized by meeting new people with shared interests at an event that brings you together, here are some tips to maximize the impact of the interactions:
+* Circulate the room. Make sure you don’t only talk to people you already know. Find people you haven’t met yet and introduce yourself.
+* Share your story. Having a concise pitch to describe who you are and what your goals are in this new career will be a helpful way to connect with others right away.
+* Ask questions and practice active listening. When you are able to get someone talking about something they are excited about, it can lead to deeper connections.
+* Follow up. Make sure to get contact information to have another conversation and reference what you talked about when you met.
+
+Even though you’ll lean into your comfort zone, you can also prepare for what to do when you leave them. If you were to engage in a networking activity that drains you, how could you recover? Take time to plan an activity beforehand and afterwards that works with your energy. If you’re an introvert, this might mean preparing for a large group networking event by having some alone time before and after the event, such as reading a book or taking a walk. Taking the time to prepare for this energy drain will help you be more fully yourself in the activity.
+
+## Types of Outreach
+When you think about outreach, you can think about both **warm** and **cold** outreach. 
+
+In short, warm outreach means reaching out to people who are already in your community and include people you know personally. Warm outreach includes:
+
+* Friends & family
+* Classmates & instructors (previous and current)
+* Your mentor 
+* Alumni
+* Student circles
+* Guest Speakers
+* Employer Partners who participate in activities at Turing
+
+Cold outreach refers to reaching out people in the software industry *who you haven't met yet.*
+
+As for Mod 2, we typically advise that students start with warm connections as it is generally easier to connect with those folks and it is great practice for tackling cold outreach.  If you are feeling ambitious and would like to connect with a cold contact, please feel free to do so! 
+
+Networking looks like:
+
+* Coffee chats/informational interviews 
+  * Most common form of networking 
+* Online engagement (i.e. commenting/posting, OpenSource contributions) 
+  * **[Read these](https://docs.google.com/document/d/1mLP6w2e0ZvyPH3BFlOl8NEwkUdBaFIzrgmRp4V8NRdY/edit)** tips on Twitter engagement from alumni 
+* Events/Meetups (follow your interests!) 
+* Student circles 
+* Jobs shadow
+
+## Create Networking Goals
+
+It’s important to remember while comfort zones are nice, you can’t make progress in your professional development if you stay in them. How to move forward without trying something that is too out-of-the-box for you? Create a compromise that allows you to strategically use your comfort zone and take a step outside of it.
+
+Here are some examples:
+
+### Example 1
+
+If you appreciate 1:1 time but wouldn’t normally reach out to someone you don’t know, try:
+* [LunchClub](https://lunchclub.com/), which is a social networking platform that uses artificial intelligence and machine learning to connect users with common interests and objectives.
+
+### Example 2
+
+If you appreciate larger groups but haven’t connected with people in the tech industry yet, try:
+* [Meetup.com](https://www.meetup.com/) to find tech-specific meetup groups, both in-person and remote
+* Check out this list of [Slack tech communities](https://github.com/ladyleet/tech-community-slacks) by region and interest
+
+### Suggested Goal: Meet Someone New at Turing
+
+Whether you join a student circle or the #lets_grab_donuts channel on Slack, commit to meeting someone new within the Turing community. The #lets_grab_donuts channel will automatically set you up with a partner, so you don’t need to send a message to connect. For anyone else though, here are some suggested steps for reaching out:
+* Send a message to this person. If you don’t know them personally, take the time to introduce yourself and explain very clearly both what you want to talk to them about and why you specifically want to talk to them about this (as opposed to someone else). Why are they the right person for your questions? Provide them with a couple of options for times to talk.
+* Come up with some questions to ask them during the call. It can be helpful to send them the questions ahead of time so they can prepare for the conversation.
+* Decide on one takeaway from the conversation that you can follow up on. This might mean doing a little research into something they mention or asking for an introduction to someone from their network.
+
+Depending on who you meet with, your questions may look different, but regardless, focus on asking questions that help you get to know each other:
+* What brought you to Turing?
+* What do you appreciate about the Turing community?
+* What advice do you have/what has been helpful for you in managing Turing life?
+* What are you working on that you are excited about?
+* What are y ou excited about contributing to in the tech industry?
+* What do you like to do in your free time outside of programming/work?
+
+### Suggested Goal: Network with a Contact You Already Know Outside of Turing
+Reach out to a contact from your existing network and ask to set up a call to discuss career advice. Who would be an ideal person for you to reach out? Consider reaching out to someone you don’t talk to day-to-day. It would be beneficial to reach out to your [“weak ties”](https://towardsdatascience.com/the-power-of-weak-ties-f1049c93f3a3) or [“dormant ties”](https://foundr.com/articles/leadership/personal-growth/why-dormant-connections-may-be-the-most-powerful-network-you-have) aka people whose knowledge and networks will be relatively new to you! These are people you may have worked with previously, people you know through friends/family/co-workers, or simply people you haven’t connected with in a while. They may or may not have a direct connection to the tech industry, but they may know someone who is in the tech industry or at a company you’re interested in or they may have professional advice that will be helpful for you. Take the following steps to reach out:
+* Send a message to this person and explain why you’d like to connect. Why are they the right person for your questions? Provide them with a couple of options for times to talk.
+* Come up with some questions to ask them during the call. It can be helpful to send them the questions ahead of time so they can prepare for the conversation.
+* Decide on one takeaway from the conversation that you can follow up on. This might mean doing a little research into something they mention or asking for an introduction to someone from their network.
+
+Depending on who you choose to reach out to, your questions will look different. Here are some suggested prompts to get you started:
+* Tell me about your background. How did you get to where you are now?
+* What does your company do? How does your role contribute to that?
+* What is the number one piece of advice you have for someone like me who is changing careers/starting something new?
+* I'm not sure what industry/companies I'm interested in. Do you have any advice on how I could start to figure that out?
+* I know I'm interested in ________ kind of work. Do you have any advice on how I could learn more about that?
+* How did you figure out where you wanted to start with your first job? How has that influenced your career?
+* Is there anyone you would recommend I talk to at your company or in the tech industry at large? Would you be able to make an introduction for me?
+
+### FAQs
+As you get started with networking at Turing, here are a couple of frequently asked questions and answers that might be helpful:
+* _What constitutes networking? Do I have to talk to someone in person/on a call?_ Networking is building a relationship. To do that, it involves having a conversation. The way that conversation takes place – on a call, through email or Slack messages, DMs on Twitter – is entirely up to you.
+* _How do I go about contacting someone if I don’t have their email?_ There are several [sites listed here](https://careerdev.turing.edu/resources/outreach_networking_resources) that can help you find people’s email addresses.
+* _Is this the only networking activity we’ll be doing?_ No, we’ll be exploring networking from multiple different angles and discuss how to approach it for both general research and for job applications. This activity is meant to get you started!
+
+## Networking Deliverable
+* Build a list of 4 warm contacts (people to get to know better)
+* Outline 1 Action step to take for networking during the mod (ex: attend an event, have a chat with someone, etc.)
+* Keep track of this list and action steps using a [networking tracker](https://docs.google.com/spreadsheets/d/1C-JY4qBv4Dxc7A1DLvkiJ8IDJJvGR_uMHKztXL16nk8/edit#gid=0).
+
+# Coffee Chats
+## What is a Coffee Chat?
+
+A `coffee chat`, also commonly referred to as an `informational interview`, is a casual and informative conversation between two individuals, usually in a relaxed setting like a coffee shop or over zoom and lasting roughly 30 minutes. The main goal of a coffee chat is for one person, often referred to as the "interviewer," to gather insights, advice, and information from the other person, known as the "interviewee," about their job or career.
+
+You will be the "interviewer" in your coffee chat, and you will be interviewing professional software developers about their day-to-day work and career.
+
+<section class="call-to-action" markdown="1">
+With your partner, brainstorm why a coffee chat might be useful for you and where you are in your software development career.
+</section>
+
+<section class="answer" markdown="1">
+### Some Benefits of Coffee Chats
+
+**Real-world Context**: Coffee chats help bridge the gap between theoretical knowledge gained in class and real-world applications. Interviewees will share real world examples that illustrate how coding skills are used in actual projects and workflows.
+
+**Networking**: Engaging in coffee chats allows you to expand your professional network. Building connections with experienced professionals can lead to mentorship opportunities, potential job referrals, and a broader understanding of the industry landscape. But it's key to note, the tone of the coffee chat should not be job seeking, even though there is a fair chance it might help lead to a job.
+
+**Interview Preparation**: While you are not the one interviewed in this context, coffee chats still develop your comfort level talking with an unknown professional and help the actual interviews feel less scary.
+</section>
+
+<section class="call-to-action" markdown="1">
+Let's do a slack waterfall. Right now, how nervous are you feeling about having a coffee chat? <br>
+
+From 1(Not nervous at all, only excited) to 10(Incredibly nervous, this is the most stressful class activity I can imagine).
+</section>
+
+❓What questions or fears do you have about having a coffee chat?
+
+## Before
+
+### Finding an Interviewee
+
+The first step to having a coffee chat is to find someone to chat with.
+
+There are many places to look!
+
+1. **Current Connection who Works as a Developer:** Maybe there is a "loose tie" or someone you're not close with, such as a high school acquaintance or past coworker who you could reach out to. Or, if you already talk to a developer regularly, such as if they are a sibling, you could ask them to introduce you to someone they know.
+
+2. **Someone You Share Something in Common With:** LinkedIn is excellent for finding folks you have something in common with. Maybe you both went to Turing or a coding school in general, or you both worked at the same library, or live in the same city, or you can see from LinkedIn you share a connection, or if you attended college you can look for fellow alumni.
+
+3. **Cold Outreach:** You'd be shocked how often strangers are happy to chat if you demonstrate your genuine interest in speaking with them in particular. You can think about your dream company or industry and find someone who works there on LinkedIn.
+
+4. **Networking Events:** Most cities have in-person tech meetups and those can be great places to meet developers and ask them if they would chat with you. You can also look into online networking options.
+
+Does the person you reach out to need to work in C# or .NET? No, you can still gain a lot of value from talking with any developer. However, if you do find someone working in C# or .NET I would definitely reach out to them. That chat has a higher likelihood of leading to a future job offer.
+
+### Asking for a Coffee Chat
+
+So you've found someone you want to interview, how do you go about making the ask?
+
+I'm a big fan of the message structure introduced in the Muse article [How to Ask for an Informational Interview (and Get a “Yes”)](https://www.themuse.com/advice/how-to-ask-for-an-informational-interview-and-get-a-yes) and making your message as personal as possible.
+
+
+1. **Start by Asking for Help**: It’s a proven fact that people love to feel like they are helping others. So, if you literally start by saying, “I’d love your help,” or “I hope you’ll be able to help me out...” your chances of getting a positive response go up significantly.
+
+2. **Be Clear**: Ask for something very specific, and make it as easy as possible for the person to say yes. Saying, “I’d love to know more about what you do and how you got your start” is okay, but doesn’t tell someone how much of their time you’re after or what you’re really suggesting. Instead, try something like, “Would you be available for a 20-30 minute zoom coffee chat to share your experiences working as a developer at ___company name here___ and any advice you may have?"
+
+3. **Have a Hook**: A great way to increase your chance of landing the interview is to demonstrate why you really want to meet with this person. Do you admire their career path? Do you think the work they’re currently doing at company X stands out as the best? Maybe you have a shared connection and think they would be a great voice of wisdom. Don’t be afraid to share why you are specifically reaching out to this person. The more personalized your ask feels, the greater chance of success you’ll have.
+
+4. **Introduce Yourself**: This is similar to having a hook, the person is much more likely to say yes to chatting if they know who you are! A one sentance bio is all it takes and be sure to mention anything you and the potential interviewee have in common. 
+
+5. **Be Very Considerate**: Remember that, in asking for an informational interview, you’re literally asking someone to put their work on hold to help you. Show your contact you understand this by saying, “I can only imagine how busy you must get, so even 15-20 minutes would be so appreciated.”
+
+6. **Make Sure You Don't Seem Like You’re Looking for a Job (Even if You Are)**: If you sound like you’re really just looking for a job, there’s a good chance this person will push you to HR or the company’s career page. So be sure to make it clear that you really want to talk to them, to learn about their career history and perspective on the job or industry. After you meet and make a great impression is when you can mention the job hunt.
+
+Ideally, you are able to get the person's email from their LinkedIn profile or another means. You can also put your message in a connection request on LinkedIn as long as it's under 300 characters. 
+
+It's tough to condense all five points to 300 characters, but something similar to the following should work:
+
+```
+Hi Zoe!
+
+I am currently a student at Turing, halfway through the Launch course. I see you also attended Turing and are working in Ruby on Rails! Would you be up for a 30-minute coffee chat to help me learn what it's like to work as a developer at Orchard? I would so appreciate it!
+```
+
+### Scheduling a Coffee Chat
+
+You've found someone who is happy to chat with you, congrats! Now you need to find a time. I recommend starting by asking something simmilar to "What are some times in the next week that you are free for a 30 minute video chat?". Make sure you two clarify timezones! If you are going to meet in person you can also ask if they have a coffee shop near them that they prefer, but most likely you will be meeting online. 
+
+Once you agree on a time, your interviewee may offer to create a video chat link. If they do not, a good option is to create a google calendar event with Google Meet. Zoom is also free for meetings under 40 minutes.
+
+### Researching the Person and Their Company
+
+You want to show up as a prepared interviewer and that means researching a bit about the company and your interviewee. 
+
+As the muse article [5 Tips for Non-Awkward Informational Interviews](https://www.themuse.com/advice/5-tips-for-nonawkward-informational-interviews) suggests:
+"Jot down a few key facts about the industry and her current or previous employer, see if you can find any articles she’s written or interviews she’s done, and try to find a few similarities between the two of you. If you’re well prepared, your interviewee will not only be impressed with the legwork you’ve put into the meeting, but will be flattered you took the time to learn so much about her. And that’s always a great way to start a conversation."
+
+### Preparing Your Questions
+
+Since you are the interviewer, you want to be prepared with a list of thoughtful questions.
+
+Remember your goal: To gather insights, advice, and information from the other person about their job or career, and to come across as someone they would want to work with.
+
+<section class="call-to-action" markdown="1">
+With your partner: Brainstorm/Research potential questions you might ask. When we come back together your instructor will call on each group to share.
+</section>
+
+
+<section class="answer" markdown="1">
+### Example Questions
+
+* At Turing we do a lot of peer code review and it has been incredibly valuable, what does the code review process look like on your team?
+* Technical capabilities aside, what soft skills do you see as important to be a great developer?
+* What's your typical day or week like?
+* What is your favorite part about your job?
+* What are the most challenging aspects of your job?
+* What advice would you give to someone in my position just starting out as a developer?
+* Can you walk me through your development process, from a ticket or task to code on production?
+* Do you usually only work with other developers or are there folks in other roles you work with regularly?
+
+Questions Specific to Your Interviewee
+* What's it like working for a company in the _______ industry?
+* I see that you've worked at a both the small company _____ and the much larger company _______ I'd love to hear more about how those two roles were different.
+* How did you choose to work at ______________?
+
+Follow Up Questions
+* You mentioned _____ can you say more about that?
+* You mentioned _____ what does that mean?
+* To make sure I'm following, is what you're saying _____________?
+
+Questions that start with "How" and "What" are great in general and will lead to better answers than yes/no questions.
+</section>
+
+## During
+
+### Starting the Conversation
+
+Often times the start of a conversation can be the most awkward and it's nice to prepare and practice what you might say to kick off a conversation.
+
+Here's what I like to start with:
+* Thank them for meeting with you
+* Say a couple of sentences about you and why you are excited to chat with them (keep this short!)
+* Pivot to the other person and ask an open-ended question that gets them talking
+
+Here is one example, but definitely make it your own!
+
+"Thank you so much for taking the time to chat with me! I'm currently 5 months into the Turing Launch program and I'm loving it and I've grown so much as a developer, but from class time alone it's hard to get a picture of what it's really like to work on a development team and I know each team is unique. So I'm eager to learn more about what your day-to-day is like and any advice you have for a budding developer like me. I see on your LinkedIn that you worked at `<enter company here>` then transitioned to `<enter company here>`, could you share more about how you came to work at `<enter company here>` and your journey as a developer so far?"
+
+### Taking Notes
+
+It's recommended to have a notebook open and take notes of key takeaways.
+
+### Watching the Time
+
+When you have about 5 minutes left before your meeting is scheduled to end, casually mention that you want to be “mindful of their time” and note the time you have left. This gives your interviewee the opportunity to either extend the interview, or transition to a graceful conclusion. Either way, they'll appreciate your respect for their time and your professionalism, which is a great way to conclude an interview.
+
+## After
+
+### Sending a Thank You Message
+
+As the above Muse article shares, "Always send a thank you note. Always. Your interviewee should never wonder how much you appreciated the time she took to share her hard-earned knowledge with you. Remember, you never know what doors she could open for you one day." The more personalized your message the better. It's best to include some detail from your coffee chat that you found particularly impactful.
+
+## Coffee Chat Deliverable
+We have gathered a list of Mentors that are excited to be your first coffee-chat opportunity.  Your instructor will DM you with your assigned mentor for outreach.  We would like you to practice these as warm-outreach opportunities, so don't ask for a coffee chat with - "my instructor gave me your name, and I'm supposed to have a coffee chat with you".  Use the strategies we outlined in this lesson!
+
+✅ Send the following in a message to @megan.
+
+1. The initial message you sent to your interviewee.
+1. Your answers to the following questions:
+    * What question that you asked led to the most valuable response? What was the question and what did your interviewee say?
+    * What do you want to do similarly in your next coffee chat?
+    * What do you want to do differently in your next coffee chat?
+1. The thank you email you sent to your interviewee.
+
+It will be helpful in this deliverable if you keep note of this communication as you go - the [Networking Tracker](https://docs.google.com/spreadsheets/d/1C-JY4qBv4Dxc7A1DLvkiJ8IDJJvGR_uMHKztXL16nk8/edit#gid=0) would be great for this 😉
diff --git a/module2/lessons/pd_overview.md b/module2/lessons/pd_overview.md
new file mode 100644
index 00000000..8af23464
--- /dev/null
+++ b/module2/lessons/pd_overview.md
@@ -0,0 +1,8 @@
+---
+title: PD Overview
+layout: page
+---
+
+Students will gain best practices and resources for setting up and having casual conversations with industry professionals. Through those conversations and some structured reflection spaces we will provide, students will gain clarity on what it means to be a developer and what matters most to them as they begin a new career. These experiences will allow students to continue refining their professional story and gain confidence with their ability to network. Since LinkedIn is a reflection of their professional story, students will be provided a space to further workshop their LinkedIn profiles and get feedback.
+
+*Students will demonstrate professional readiness to move to Mod 3 by sharing their LinkedIn profile that meets expectations, and thoughtful reflections on their conversations with industry professionals in their Final Portfolio Review.*
\ No newline at end of file

From ee3248c6eb8fd9593461326259a55a2b42e52be5 Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Thu, 16 May 2024 14:31:26 -0600
Subject: [PATCH 09/15] Add M3 PD lessons

---
 module3/lessons/index.md                      |   4 +
 module3/pd/index.md                           |  33 +++++
 .../behavioral_interview_preparation.md       |  76 ++++++++++
 module3/pd/lessons/coverletters_made_easy.md  |  90 ++++++++++++
 module3/pd/lessons/interview_preparation.md   | 138 ++++++++++++++++++
 module3/pd/lessons/pd_overview.md             |  20 +++
 module3/pd/lessons/terminal_portfolio.md      |  64 ++++++++
 7 files changed, 425 insertions(+)
 create mode 100644 module3/pd/index.md
 create mode 100644 module3/pd/lessons/behavioral_interview_preparation.md
 create mode 100644 module3/pd/lessons/coverletters_made_easy.md
 create mode 100644 module3/pd/lessons/interview_preparation.md
 create mode 100644 module3/pd/lessons/pd_overview.md
 create mode 100644 module3/pd/lessons/terminal_portfolio.md

diff --git a/module3/lessons/index.md b/module3/lessons/index.md
index cedfd2f4..5cb73a18 100644
--- a/module3/lessons/index.md
+++ b/module3/lessons/index.md
@@ -2,3 +2,7 @@
 layout: page
 title: Module 3 - Lessons
 ---
+
+## Professional Development
+
+* [Mod 3 PD Curriculum](../pd/)
\ No newline at end of file
diff --git a/module3/pd/index.md b/module3/pd/index.md
new file mode 100644
index 00000000..bdae37c8
--- /dev/null
+++ b/module3/pd/index.md
@@ -0,0 +1,33 @@
+---
+layout: page
+title: Module 3 - Professional Development
+---
+
+General resources:
+[Mod 3 PD Overview](./lessons/pd_overview.md)
+
+### Intermission Work: 
+  * [Crafting A Tech Resume](https://docs.google.com/presentation/d/e/2PACX-1vRDqx6yceiHWcOEiKjEp0Hr43o6yb4WtF60jJFRAOKCeTIbrYf0iA9bDMk1jumn1lMP0R-5MV-wfkMY/pub?start=false&loop=false&delayms=3000&slide=id.p1)
+
+### Week 1:
+  * [Intro to PD & Live Resume Session](https://docs.google.com/presentation/d/1hjEDTWnlnZSxC-1SoYqMIhWN7cYH-ObV54v7QU-5rtI/edit#slide=id.p3)
+    
+### Week 2:
+  * [Interview Preparation- Putting It All Together](./lessons/interview_preparation.md)
+  * [Resume Storytelling Workshop](https://docs.google.com/presentation/d/1TPvCPkxJhM_nFzAxbjlDqvSUxlHhrAfmcm4cgxqchgk/edit#slide=id.p)
+  * [ ] **Deliverable #1:** Submit [Exit Ticket](https://www.google.com/url?q=https://forms.gle/1WHVG6iiHX6bkfS97&sa=D&source=calendar&ust=1696369633966175&usg=AOvVaw1jc9wNuKyOBWJnI12aUW9u) by Wednesday
+  * [ ] **Deliverable #2:** Submit [Resume Draft](https://forms.gle/awwALTSFZKDhs33b8) by Friday.
+
+### Week 3: 
+  * [Cover Letters Made Easy](./lessons/coverletters_made_easy.md)
+  * [ ] **Deliverable #3:** Submit [Cover Letter Draft](https://forms.gle/nqNA3quvJ536juik9) by Friday.
+
+### Week 4: 
+  * [The Application Process](https://docs.google.com/presentation/d/e/2PACX-1vQQb_NqtACy5ea-EbE8KJX7QA62bpOC_YMB6tzsyL_dRuZqyVLKfAIZkFcLRj9MefGUuvT-WbRUzTQS/pub?start=false&loop=false&delayms=3000)
+  * [Behavioral Interview Preparation](./lessons/behavioral_interview_preparation.md) - paired with Front-end cohort
+ 
+### Week 5:
+  * [Terminal Portfolio](./lessons/terminal_portfolio.md)
+    * Use [this form](https://docs.google.com/forms/d/e/1FAIpQLSfKXVnpYdlwE4FpsAcG2tKfxTu4K4m7cpsgldbpIC03ZLCL6A/viewform) to submit your draft.
+  * Review Roundtable of Career Materials 
+    * Students can expect to receive feedback on their career materials (both resume & cover letter) from Turing staff by the end of week 5. 
\ No newline at end of file
diff --git a/module3/pd/lessons/behavioral_interview_preparation.md b/module3/pd/lessons/behavioral_interview_preparation.md
new file mode 100644
index 00000000..69bcb26f
--- /dev/null
+++ b/module3/pd/lessons/behavioral_interview_preparation.md
@@ -0,0 +1,76 @@
+---
+layout: page
+title: Behavioral Interview Preparation
+---
+
+### Behavioral Interview Preparation
+**Learning Goals**
+
+* Approach an interview by thinking like the interviewer
+* Consider the themes of questions and the top skills they are assessing
+* Begin categorizing your experiences so you’re ready to answer any question
+
+**Warm Up**
+
+* What do you think are the top 2 goals of an interviewer during the behavioral interview?
+* What are some ways that people can prepare for behavioral interviews?
+*Note: Behavioral interview refers to the non-technical interview.
+
+**Thinking Like an Interviewer**
+
+Note - your interviewer won’t always say it, but you can and should ask questions throughout the entire process. Given a code challenge in a language, you aren’t familiar with? Ask to complete it in Ruby or JS. Unclear about what they are looking for in the challenge? Ask them to clarify.
+
+Many people approach interviews with the mindset that they need to improvise their answers to every question they are asked. This approach can lead to lots of nerves going into the interviews because you’re thinking:
+What if I can’t think of a good answer on the spot?
+It can also lead to you leaving an interview thinking:
+Oh shoot, I should have said THAT when they asked me that question! Why didn’t I think of that earlier?
+
+Today we are going to talk about how you can prepare for a behavioral interview by thinking ahead and preparing your answers before the interview.
+
+You can’t possibly predict all of the questions that you may get asked in an interview. But you CAN predict some of the main ideas and themes that the interviewer may ask you about. For example, it’s safe to say that you’ll get asked about your professional background. You’ll also probably get asked about how you learn, how you collaborate, and how you overcome obstacles.
+
+You do not have to have a different answer prepared for every possible question you might get asked. Instead, should prepare answers that speak to the broad themes of what you may be asked about.
+
+Let’s consider an example. Take a moment to think about all of the different ways an interviewer might ask about your collaboration style. Make a list of at least 5 questions someone might ask you that would get you to talk about how you collaborate.
+
+**Some examples:**
+
+Notice that many of those questions are extremely similar, just worded differently. How many different stories would you need to have prepared to answer those questions? Two? Maybe three? That’s the point! Instead of preparing an answer for every question above, you might prepare a story that highlights your strengths as a teammate and another that demonstrates your skills in conflict resolution and empathy. Then, you’d be prepared to answer any question on the list!
+
+We are going to work through some activities to solidify this concept.
+
+**Activity 1: Categorizing Questions**
+First, take 15 minutes to complete part A of this activity in breakout rooms. Note that you will all want to have your own copy of this document.
+
+Next, take 15 minutes to complete part B of the same activity independently.
+
+### Activity 2: Mini Mock Interview
+**Solo Reflection**
+Consider the following questions about your group project from mod 2.
+
+* What about that project sticks out to you the most?
+* What was the most memorable moment from that project?
+* What is something you did well during that project?
+* What is something you wish you had done better?
+
+Now, think about the themes from the questions in the previous activity.
+
+Which theme do you think you could speak to best using that group project from mod 2 as your tangible example?
+
+**In Breakout Rooms**
+In pairs, you’ll practice answering one question by using that group project from mod 2. Determine who is person A and person B and follow these steps:
+
+* Person A will tell Person B what theme/category they’d like to focus on.
+* Person B will then choose a question from that category and ask person A.
+* Person A will answer that question and use the project experience to anchor their answer.
+* Person B will give feedback on their answer. (Your feedback should focus on person A’s ability to convey the skills the question is assessing and person A’s ability to 
+  anchor their answer in the tangible project example.)
+* Switch roles and repeat!
+
+You will have 20 minutes total, so be sure to watch the clock and switch roles after 10 minutes.
+
+**Wrap Up**
+Take some time to reflect on the following questions:
+
+* What theme do you feel the most prepared to discuss? The least?
+* How will you practice moving forward?
diff --git a/module3/pd/lessons/coverletters_made_easy.md b/module3/pd/lessons/coverletters_made_easy.md
new file mode 100644
index 00000000..1299eeb1
--- /dev/null
+++ b/module3/pd/lessons/coverletters_made_easy.md
@@ -0,0 +1,90 @@
+---
+layout: page
+page: Cover Letters Made Easy
+---
+
+## Overview
+
+In this lesson, you'll gain a clear understanding of the role that cover letters play in the job application process. We'll explore the key elements of crafting impactful cover letters that effectively showcase your qualifications and enthusiasm for the position.
+
+### Learning Goals
+
+* Understand the purpose of a cover letter
+* Reflect on what needs to be in a cover letter
+* Prepare a cover letter based on a job application 
+
+##### Why even write a cover letter?
+
+ <iframe width="560" height="315" src="https://www.youtube.com/embed/szbMDbKWIkU" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+Cover letters can seem daunting, but they don't have to be. It's important to understand their importance in order to know how to write them well. A common misconception is that a cover letter should be all about you as the candidate. However, your cover letter is actually a space to demonstrate your understanding of the company. Another common misconception is that a cover letter should regurgitate everything on your resume. It should actually complement your resume; your resume is a space to tell about you, your cover letter allows you to *show* much more.
+
+Start with this frame in your mind -- the cover letter is a love letter to the company. How? Again, start by demonstrating your understanding of the company.
+
+* What research have you done?
+* Who from the company have you talked to?
+* Go back to the job posting -- what are they looking for? What needs do they have based on this posting?
+* What problem is this company trying to solve?
+* What is exciting about this company?
+
+Then, talk about yourself, but remember -- this still isn't really about you. Talk about yourself in relation to the company. First, provide an introductory hook. Show what you know about the company and *why* you're interested in the position. Then, show why you're qualified for the job. A great way to template out your story is by a quick summary: "Merging my background in X and Y, I now help [industry] improve [these outcomes]." You can also break your story into parts:
+
+1. Here's what I did in the previous phase of my career + what I learned from that...
+2. And here's what I can do for you based on what I've learned...
+
+Now, create a connection between you and the company:
+
+* What can we do together?
+* It’s not about what you can *get* from them; it’s about what you can *give* to them
+
+#### But, how do I format the cover letter? 
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/lW0JbWwrj_0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+##### First paragraph: The hook 
+
+* Show why you’re interested in the position
+* Mention how you found out about the opening 
+* State the position you’re applying
+* Use the title from the job listing
+
+##### Middle paragraph: Why you? Why this company? 
+
+* Connect your accomplishments, skills, and knowledge to the position and company
+* Demonstrate the soft skills the role requires by using examples from your experience
+* Tie the company to your experiences
+
+
+##### Final paragraph: Now, bring the company + you together
+
+* Summarize what you would bring to the position and suggest next steps by requesting a meeting or a call (be specific) 
+* Thank them for reading your materials
+* Ask for an interview
+
+### Do's and Don'ts on Cover Letters
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/9qbQqpWfn1o" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+There is no one-size-fits-all way to write a cover letter; there are multiple ways to write an effective cover letter. However, there are some general rules to follow:
+
+* Any time you mention yourself **connect** it explicitly to the job/company
+* Keep it concise (no more than a page; half a page is ideal)
+* If you’ve met someone at the company, drop their name!
+* State the position you’re applying for in the first line
+
+If you find yourself with:
+
+* Very long/wordy cover letters, try reading it out loud to find extraneous details. Cut those to make easily skimmable, shorter paragraphs
+* A cover letter that is all about you, try reframing sentences about you by starting the sentence talking about the company and segue into how you can provide value to them based on your experiences and skills
+* Grammar and spelling errors, try [Grammarly](https://www.grammarly.com/) or the [Hemingway App](http://www.hemingwayapp.com/). Reading cover letters aloud or having a peer proofread will also help you catch a lot of those mistakes.
+
+### Cover Letter Next Steps & Resources
+**Deliverable for Cover Letter Lesson:** 
+1. Look for a job description that interests you.
+2. Create a cover letter based on a job description. 
+3. Format, structure, and create your cover letter using the [Cover letter guide and template](https://docs.google.com/document/d/1ctPSIEcZ5nrnfD4y0HlTUH9tdYRscbIjXhMQLjMPzPA/edit)
+4. It's optional to complete the [cover letter exit ticket](https://docs.google.com/forms/d/e/1FAIpQLSfPkAkTdqtehtWydhdTP8RwEm7t-huLwQs8U201r92rDuRsfw/viewform) but it is recommended as a check for understanding. 
+ 
+
+### Resources:
+* Here are [additional resources](https://careerdev.turing.edu/resources/cover_letter_resources) and a general checklist to guide your draft. 
diff --git a/module3/pd/lessons/interview_preparation.md b/module3/pd/lessons/interview_preparation.md
new file mode 100644
index 00000000..9651c4fc
--- /dev/null
+++ b/module3/pd/lessons/interview_preparation.md
@@ -0,0 +1,138 @@
+---
+layout: page
+title: Interview Preparation - Putting It All Together
+---
+
+## Interview Preparation
+  Putting It All Together
+
+### Overview
+You've done the groundwork to prepare for your job search: refining your story, crafting your resume, and building your portfolio. Now is the time to put all of these things into motion and talk about why you're the right person for the job.
+
+### Learning Goals
+* Identify how to prepare and research prior to an interview
+* Ideate and try out solutions to improve your current interviewing strategy
+* Understand how to answer interview questions through specific strategies
+
+[Slides for this lesson](https://docs.google.com/presentation/d/19v08-f77qv6HTMR3teiuv_SmXMHzpydHrdo144WYG_8/edit?usp=sharing)
+
+
+#### Starting off Strong: Tell me about Yourself
+This request for information is typically at the very beginning of an interview. It's an opportunity to provide the interviewer with insights into your qualifications and fit for the role.
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/4TL2YnGS9AQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+### Preparation Strategies
+There are many ways to prepare for interviews. The key to all interviews is **knowing who you are and how to talk about yourself.** Today, we'll go through 4 particular tips to help with this process:
+
+1. Answer the whole question
+2. Tell stories
+3. Know how to talk about your experience
+4. Research & prep
+
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/w1ncXtkOqOo" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+#### Strategy #1: Answer the whole question
+Pay attention to what the question is asking as well as any *subtext* inherent in the question. Let's look at an example:
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/exQySTPJ490" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+* How do you deal with failure?
+
+This question is asking you to:
+* **Acknowledge that you fail.** You're not perfect, you have experienced failure. It's okay to be transparent about that
+* **Describe what you do after you fail.** How do you pick yourself back up? What next steps do you take?
+* **Give specifics.** Providing specifics and responding to questions in the form of a story can help them understand and remember your response better.
+
+
+#### Strategy #2: Use the [STAR Method](https://www.indeed.com/career-advice/interviewing/how-to-use-the-star-interview-response-technique)
+<iframe width="560" height="315" src="https://www.youtube.com/embed/6jfHij9Kj-4" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+Use this as an opportunity to tell stories about your relevant experience. A great template to use to plan out your stories is the STAR method:
+
+* **Situation:** The interviewer wants you to present a recent challenge and situation in which you found yourself.
+* **Task:** What were you required to achieve? The interviewer will be looking to see what you were trying to achieve from the situation. Some performance development methods use “Target” rather than “Task”. Job interview candidates who describe a “Target” they set themselves instead of an externally imposed “Task” emphasize their own intrinsic motivation to perform and to develop their performance.
+* **Action:** What did you do? The interviewer will be looking for information on what you did, why you did it, and what the alternatives were.
+* **Results:** What was the outcome of your actions? What did you achieve through your actions and did you meet your objectives? What did you learn from this experience and have you used this learning since?
+
+Example:
+* Tell me about a successful project that you've worked on.
+
+In this example, focus on establishing the situation or scenario for the project. Set the stage for the listener -- how many people were involved in this project? What was the timeline? What were the main technologies used? 
+
+Then move into the task/target and discuss the objective of the project. What was the purpose? Who was the user? 
+
+Then, walk through all of the actionable steps you/your team took to meet the objective of the project. What successes did you have? What challenges did you run into? What steps did you take to overcome those challenges? 
+
+And finally, what were the results of this project? What were you able to accomplish? What would you have done differently? 
+
+
+#### Strategy #3: Know how to talk about your experience
+There are 2 elements to keep in mind here as you present your software and work experience: 
+
+* Discussing your Turing experience as professional experience
+* Your previous work experiences 
+
+When talking about Turing: 
+
+* Do:
+  * Give a high-level description
+  * Talk about Turing as *professional experience*
+  * Highlight the differences between Turing and other code schools
+
+* Don't assume your interviewer knows anything about Turing. That means not using Turing-specific jargon (module, inning, cohort, DTR, etc.)
+
+Example:
+
+Instead of saying “In Module 1, when I was working on my first paired project…” what could you say?
+
+Consider how you would respond to this question:
+
+"I’ve never heard of Turing. What did you focus on there? What’s the structure of the program? How did it prepare you for this career?"
+
+For your previous professional experiences and background, unpack the transferable skills you have that apply to the job. Consider how your specific experiences make you uniquely qualified compared to other candidates. For example, have you worked with customers before in any capacity? Talk about it. Have you ever had to deliver on tight deadlines? Yes, you're a Turing student -- talk about that. Have you had to communicate with different teams? Talk about it. 
+
+#### Strategy #4: [Research and Prep](https://www.glassdoor.com/blog/7-research-job-interview/)
+<iframe width="560" height="315" src="https://www.youtube.com/embed/Hfybq4a-2E8" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+1. Make sure to start by researching your company (you should do this before you submit your application anyway). Know what their tech stack is
+
+2. Keep a running doc where you can keep track of common interview questions and specifics that you can draw from to answer these questions. Outline your stories here about projects, team situations, successes, and failures. Make sure to review these before each of your interviews.  
+
+### [Do you have any questions for me?](https://www.keyvalues.com/culture-queries)
+<iframe width="560" height="315" src="https://www.youtube.com/embed/qP0Sl7qs6Jc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+At the end of almost every interview, you'll be given an opportunity to ask questions. Use this time to get a better understanding of the company, what it would be like to work there, and gauge whether this role is a good fit for you. 
+
+### Putting it into Practice
+1. To continue preparing for interviews, create an interview prep document or story bank to write out answers by telling stories about various experiences.
+2. Review this [Story bank doc](https://docs.google.com/spreadsheets/d/16aempR55Tej8pPr-l9qq6vBnL4bax9kbGEXA9nO7oVo/edit#gid=882531233) that includes templates, project examples, and interview tips.
+3. Next, use the prompts below or from the story bank doc and write about at least one behavioral and one project question using the STAR method:  
+
+ *  Pick a successful project(What was the situation/scenario of the project? What was the task/target of the project? What action 
+    steps did you take? What were the results?):
+  * Write about a time you failed and what you learned from that experience:
+  * Write about how you've approached working with a team using a specific example:
+  * What other stories will you prepare to share?
+  * Do some research into your top companies' tech stacks; what do you already know? What can you compare to your own learning? What do you need to learn more about?
+  * Using this [interview prep resource guide](https://careerdev.turing.edu/resources/interview_prep_resources), pick out at least 3 resources you will use to prepare for interviews as well as 3     
+    behavioral questions you could practice.
+
+**Other Tips:**
+* In your interview pre doc keep track of technical concepts you're practicing, behavioral answers, and feedback.
+* Review:
+  * Your professional story
+  * Feedback you've received
+  * Your projects; Go through your projects to reflect on:
+    * One specific bug
+    * Something that was really hard
+    * Something that was rewarding
+    * Any interesting struggles/insights about the collaboration process
+  * Your Flower Exercise
+  * Your strengths
+  * Your areas of growth
+  * DTR Memos
+  * Retro notes
+  * Eval notes
+
+## Check for Understanding
+After you've completed this lesson, submit this [exit ticket](https://forms.gle/1WHVG6iiHX6bkfS97), due by Wednesday of Week 2 EOD.
diff --git a/module3/pd/lessons/pd_overview.md b/module3/pd/lessons/pd_overview.md
new file mode 100644
index 00000000..500b5c23
--- /dev/null
+++ b/module3/pd/lessons/pd_overview.md
@@ -0,0 +1,20 @@
+---
+layout: page
+title: PD Overview 
+---
+During Mod 3, students will develop employer-ready application materials and interview skills based on networking conversations, guided reflections, and feedback from earlier modules. Students will learn how to effectively communicate accomplishments, transferrable skills, and technical expertise using portfolios, resumes, cover letters, and behavioral interview lessons. 
+
+By the end of Mod 3, students will have developed the following:
+* Crafted a technical-focused and ATS-friendly resume: Students will learn how to create a resume that highlights their technical skills and is optimized for Applicant Tracking Systems (ATS) used by companies during the hiring process.
+
+* Developed a working cover letter: Students can write a cover letter that effectively communicates their unique value, genuine interest in the company, and alignment with the specific roles they are applying for.
+
+* Learned effective interview techniques: Students will learn to navigate interviews and confidently answer common interview questions. They will develop strategies for showcasing their skills and experiences in a compelling and concise manner.
+
+* Refined their career goals: Throughout Mod 3, students will continue to develop a blueprint for their job search. They will focus on identifying what they want from their new career, building on their professional story. They will leverage their professional experiences to shape their narrative and evaluate how their unique strengths align with finding a rewarding and fulfilling career trajectory.
+
+* Students may also start building their Terminal Portfolio. 
+
+Students will demonstrate professional readiness to move to Mod 4 with the submission of  an ATS-friendly resume,  a master cover letter draft that meets expectations, and thoughtful reflections on their job search blueprint during their Final Portfolio Review. 
+
+
diff --git a/module3/pd/lessons/terminal_portfolio.md b/module3/pd/lessons/terminal_portfolio.md
new file mode 100644
index 00000000..90e1a9b4
--- /dev/null
+++ b/module3/pd/lessons/terminal_portfolio.md
@@ -0,0 +1,64 @@
+---
+layout: page
+title: PD Overview 
+---
+
+## Turing Alumni Portfolio 
+What it is:
+* Terminal is our joint job board and graduate portfolio site
+* How we showcase our job-seeking graduates and soon-to-be graduates
+* How it’s used:
+  * Employers come here to look for candidates
+  * We also send these to employers
+
+### Getting Started! 
+1. You will receive an email invitation from Tracey at the beginning of Mod 3.
+2. Use [this form](https://docs.google.com/forms/d/e/1FAIpQLSfKXVnpYdlwE4FpsAcG2tKfxTu4K4m7cpsgldbpIC03ZLCL6A/viewform) to submit your draft.
+
+###  How to set up your profile:
+[Log into Terminal at](https://terminal.turing.edu/developers/sign_in)
+
+* Go to Edit Profile from the account menu
+* Fill out the profile until all sections are complete. Here is a [checklist](https://careerdev.turing.edu/resources/terminal_directions)of what needs to be completed before we publish a terminal account.
+* Only click "Request Review" when your portfolio is fully set up with projects. Until then, staff members can see your updates.
+* Staff members will review your profile and approve it for publishing or request additional changes.
+* For more info on how to set this up, [Watch this Terminal profiles walkthrough with Tanner!](https://drive.google.com/file/d/1NqHrdkr0B5wEvEaH9Z8dJK56TcSJoV_t/view)
+
+### If you have set your terminal profile now it's time to customize it.
+What needs to be included in order for your portfolio to be published? Here is what the team is looking for:
+Title
+* Professional-looking photo
+  *  This should be a photo of just you (no kids or animals, sorry!)
+  * Use the same photo as your LinkedIn and GitHub profiles if possible
+  * Dont have a professional-looking photo? [Check out this post](https://writing.turing.edu/how-to-take-your-own-linkedin-headshot/) for tips on how to take one at home
+
+About Me Description
+
+* Tell your professional story- What is your story about your past, present, and future that you want to share with employers? Make sure to answer these questions: who am I? Why am 
+  I in this field? What next for me?
+    * Email address
+    * GitHub profile
+    * LinkedIn profile
+    * Polished draft of resume
+    * Preferred Locations
+
+ Previous Industries
+    * Limit to 5 previous industries. If you are concerned about this, please reach out to your Career Specialists.
+    * At least 2 projects
+    * Show variety: paired, team, individual
+    * Include an estimation of project contribution hours
+    * Include screenshots
+    * Tools Used
+    * Code Repository Link
+
+Nice to have but not required for initial publication:
+   * Pronouns
+   * Skills you are currently learning
+   * Twitter profile
+   * Project collaborators
+   * Deployed Project link
+
+### Important Resources
+* [Discover more detailed information on how to effectively write your project descriptions](https://docs.google.com/document/d/1zKePxhD-xQdLRPeLI21E71ET_U88ZZ-SKTQjRVzs8tM/edit)
+
+If you have questions about the information on this page, please contact an instructor. 

From 1ec480cd906da0551ac7dd0d315a116de5a8a1fc Mon Sep 17 00:00:00 2001
From: Kayla Wood <kaylaewood@gmail.com>
Date: Thu, 16 May 2024 14:44:52 -0600
Subject: [PATCH 10/15] Add M4 PD lessons

---
 module3/pd/index.md                           |   4 +-
 module4/pd/index.md                           |  19 ++++
 module4/pd/lessons/interview_simulation.md    |  55 +++++++++
 .../pd/lessons/terminal_portfolio.md          |   0
 .../employer_case_study/evaluation.md         |  23 ++++
 .../employer_case_study/expectations.md       |  87 +++++++++++++++
 .../employer_case_study/final_presentation.md |  54 +++++++++
 module4/projects/employer_case_study/index.md |  32 ++++++
 .../interview_simulation.md                   |  55 +++++++++
 .../interview_simulation_rubric.md            |  29 +++++
 .../employer_case_study/swot_analysis.md      | 104 ++++++++++++++++++
 11 files changed, 459 insertions(+), 3 deletions(-)
 create mode 100644 module4/pd/index.md
 create mode 100644 module4/pd/lessons/interview_simulation.md
 rename {module3 => module4}/pd/lessons/terminal_portfolio.md (100%)
 create mode 100644 module4/projects/employer_case_study/evaluation.md
 create mode 100644 module4/projects/employer_case_study/expectations.md
 create mode 100644 module4/projects/employer_case_study/final_presentation.md
 create mode 100644 module4/projects/employer_case_study/index.md
 create mode 100644 module4/projects/employer_case_study/interview_simulation.md
 create mode 100644 module4/projects/employer_case_study/interview_simulation_rubric.md
 create mode 100644 module4/projects/employer_case_study/swot_analysis.md

diff --git a/module3/pd/index.md b/module3/pd/index.md
index bdae37c8..cb1dc53d 100644
--- a/module3/pd/index.md
+++ b/module3/pd/index.md
@@ -3,7 +3,7 @@ layout: page
 title: Module 3 - Professional Development
 ---
 
-General resources:
+## General resources:
 [Mod 3 PD Overview](./lessons/pd_overview.md)
 
 ### Intermission Work: 
@@ -27,7 +27,5 @@ General resources:
   * [Behavioral Interview Preparation](./lessons/behavioral_interview_preparation.md) - paired with Front-end cohort
  
 ### Week 5:
-  * [Terminal Portfolio](./lessons/terminal_portfolio.md)
-    * Use [this form](https://docs.google.com/forms/d/e/1FAIpQLSfKXVnpYdlwE4FpsAcG2tKfxTu4K4m7cpsgldbpIC03ZLCL6A/viewform) to submit your draft.
   * Review Roundtable of Career Materials 
     * Students can expect to receive feedback on their career materials (both resume & cover letter) from Turing staff by the end of week 5. 
\ No newline at end of file
diff --git a/module4/pd/index.md b/module4/pd/index.md
new file mode 100644
index 00000000..682ea0b8
--- /dev/null
+++ b/module4/pd/index.md
@@ -0,0 +1,19 @@
+---
+layout: page
+title: Module 4 - Professional Development
+---
+
+### Deliverable 1: Complete Terminal or Personal portfolio
+  * Students may choose to build a personal portfolio OR build a portfolio using Terminal
+    * Follow [these directions](../../job_seekers/resources/terminal_directions.md) to update and submit your portfolio.
+        * If you build your own portfolio, you should start with the "About Me Section" in the link above to guide the content you put on your portfolio.
+    * Add at least 2 projects and use [these guidelines](https://docs.google.com/document/d/1zKePxhD-xQdLRPeLI21E71ET_U88ZZ-SKTQjRVzs8tM/edit) to help you create the descriptions
+    * Upload your polished and targeted resume
+    * Include the link to your LinkedIn that is updated and optimized for job search
+    * **Due date #1: Friday of Week 4.** Make sure to "request review" by this date.
+      * For Terminal portfolios, we will review and send follow-up on anything to be completed before it can be published.  Note: you must select "request review" on your Terminal portfolio and then we will review and publish it; it isn't fully complete until we publish it.
+      * If you create a personal portfolio, you should DM a link to the Mod 4 instructors when it's ready for review.  
+    * **Final due date: EOD Friday of Week 5.**  All updates to the portfolio must be made by this time to fulfill this deliverable. 
+
+### Deliverable 2: Employer Case Study & Full Interview Simulation 
+  * [Instructions here](../projects/employer_case_study/)
\ No newline at end of file
diff --git a/module4/pd/lessons/interview_simulation.md b/module4/pd/lessons/interview_simulation.md
new file mode 100644
index 00000000..efb5bf4c
--- /dev/null
+++ b/module4/pd/lessons/interview_simulation.md
@@ -0,0 +1,55 @@
+---
+title: Employer Case Study Interview Simulation
+layout: page
+---
+
+[Back to Employer Case Study Overview](./index.html)
+
+[Back to Employer Case Study Expectations](./expectations.html)
+
+
+## Overview 
+The primary goal of the interview simulation, based on a selected job description (JD), is to provide students with realistic and practical experience of a job interview process.
+
+
+### Learning Goals
+1. Enhance Interview Skills: Help students develop and refine their interview skills, including answering questions, presenting their qualifications, and showcasing their suitability for the role.
+
+2. Apply Knowledge: Enable students to apply the knowledge and insights gained from their research, such as the SWOT analysis and understanding of the role's requirements, to effectively communicate their alignment with the position.
+
+3. Build Confidence: Boost students' confidence in handling interviews by simulating real-world scenarios. This practice helps reduce anxiety and improve their ability to perform well in actual job interviews.
+
+4. Prepare for Real Interviews: Equip students with the ability to navigate the job market effectively, with a focus on matching their skills and interests to actual job openings. This, in turn, will enhance their chances of securing job opportunities that align with their career goals.
+
+5. Receive Constructive Feedback: Provide students with constructive feedback from instructors and peers. This feedback can help them identify areas for improvement and make necessary adjustments before real job interviews.
+
+By using a job description as the basis for the interview simulation, students can better connect their academic learning with practical career preparation and develop the skills necessary to succeed in their job search endeavors.
+
+## Student Steps for Interview Preparation
+Before the Interview Simulation in Week 5:
+
+* Complete Parts 1 and 2 of the Case Study project:
+    * Find one job role that aligns with your career interests and goals. This role will be the focus of your interview simulation.
+    * Complete the Employer Persona research
+
+
+* Submit Mock Interview Documents
+    * Submit via the form on the calendar ([also linked here](https://docs.google.com/forms/d/e/1FAIpQLScmIo-SF8uxj9obkBEtxOSfPxQgycIYnL_kMBJBBZg23pbMFQ/viewform))
+      * A copy of the Job Description that you've selected for the simulation
+        * IMPORTANT: The job description should be copied into a google doc. Do not just send a link to the website with the posting. If the job posting is taken down, there is no record of the job description for you to reference.
+      * A resume and cover letter tailored to the chosen role
+    * This allows the instructor to prepare relevant interview questions based on the job description and your qualifications, ensuring a realistic and valuable interview experience.
+
+* Create an Interview Preparation Document
+    * Develop an interview preparation document that includes a list of common interview questions and space for your answers.
+    * Also, include a section for questions you intend to ask during the interview. Research the company and the role to formulate insightful questions that demonstrate your genuine interest.
+    * Use this document to practice your responses, ensuring you are well-prepared for the interview and able to showcase your qualifications effectively.
+    * Take a look at these Interview Story Banks to use or get ideas for creating your own.
+
+[Interview Simulation Rubric](./interview_simulation_rubric.html)
+
+## Resources
+* [Interview Story Bank - Make a copy](https://docs.google.com/spreadsheets/d/16aempR55Tej8pPr-l9qq6vBnL4bax9kbGEXA9nO7oVo/edit#gid=882531233)
+* [Interview Story Bank in Notion](https://perpetual-seeker-acf.notion.site/Behavioral-Interviews-Creating-Your-Story-Bank-1-42398184f39b4947a79c9468272c2955)
+* [Technical Interview Questions](../../lessons/technical-interview-questions.html)
+* [Behavioral Interview Questions](../../lessons/behavioral-interview-questions.html)
\ No newline at end of file
diff --git a/module3/pd/lessons/terminal_portfolio.md b/module4/pd/lessons/terminal_portfolio.md
similarity index 100%
rename from module3/pd/lessons/terminal_portfolio.md
rename to module4/pd/lessons/terminal_portfolio.md
diff --git a/module4/projects/employer_case_study/evaluation.md b/module4/projects/employer_case_study/evaluation.md
new file mode 100644
index 00000000..01ff8fda
--- /dev/null
+++ b/module4/projects/employer_case_study/evaluation.md
@@ -0,0 +1,23 @@
+---
+title: Employer Case Study Rubric
+layout: page
+---
+
+[Back to Employer Case Study Overview](./index.html)
+
+## Overview
+The Employer Case Study Project will be assessed at 2 different points throughout the project. A passing score is required for both parts.
+
+### 1. Interview Simulation
+[Interview Simulation Rubric](./interview_simulation_rubric.html)
+
+### 2. Final Presentation
+[Final Presentation](./final_presentation.html)
+
+## Summary of ALL Deliverables
+* Submit pre-interview documents via [this form](https://docs.google.com/forms/d/e/1FAIpQLScmIo-SF8uxj9obkBEtxOSfPxQgycIYnL_kMBJBBZg23pbMFQ/viewform) at least 24 hours before your interview time:
+  * A copy of job description
+  * A resume tailored to chosen job description
+  * A cover letter tailored to chosen job description
+* Complete a mock interview with an instructor and score a passing grade in week 5
+* Deliver a Final Presentation summarizing your research (as described above) in week 6
\ No newline at end of file
diff --git a/module4/projects/employer_case_study/expectations.md b/module4/projects/employer_case_study/expectations.md
new file mode 100644
index 00000000..5f091880
--- /dev/null
+++ b/module4/projects/employer_case_study/expectations.md
@@ -0,0 +1,87 @@
+---
+title: Employer Case Study Project Expectations
+layout: page
+---
+
+[Back to Employer Case Study Overview](./index.html)
+
+The Employer Case Study project has 5 primary components, described below.
+
+## Part 1: Find the Opportunity
+- Students identify a  job opportunity that aligns with their career goals and interests.
+- They search for roles on job boards, company websites, and through networking.
+
+### Part 1 Deliverables
+* Send a copy of the job description to the instructor who will be leading your mock interview at least 24 hours before your scheduled interview time.
+
+## Part 2: Employer Persona and Case Study Outline
+ You will research the company of your chosen job opportunity from Part 1. You will articulate your genuine interest in the company ("Why Us"), understand the company's needs for the specific role ("Why this Role"), and demonstrate why you are the right fit for the position ("Why You"). 
+
+Step 1: Define "Why this Company" - Demonstrating Genuine Interest
+- Introduce the concept of "Why this Company."
+- Research to understand and answer the question, "Why Us?" for your ideal company.
+- Demonstrate a genuine interest in the organization.
+
+Step 2: Components of "Why this Company" - Company Research
+- Break down the elements of "Why this Company."
+- Research and provide insights into the company's business model or competitive advantage that sets it apart in its industry.
+- Explore the company's tech stack, addressing its technological aspects.
+- Investigate the cultural fit by describing the company's impact and mission.
+
+Step 3: Answer "Why this Role Exploration" - Understanding Hiring Manager Needs
+- Discuss the importance of understanding the hiring manager's perspective.
+- Apply from the hiring manager's viewpoint, explaining why the role is crucial for the company.
+- Perform a [SWOT analysis](./swot_analysis.html) of the role, considering its strengths, weaknesses, opportunities, and threats.
+  - [SWOT Analysis Example](https://docs.google.com/document/d/15PN2HVvTryslJun2Myp6WVtz4-Z6EgLRk-zc2lAGOO4/edit#heading=h.fqtw9c99wqu4)
+
+Step 4: "Why You?" - Personal Motivation and Skill Match
+- Explore the "Why You?" aspect by focusing on personal motivation.
+- Identify what genuinely motivates you in the role.
+- Explain how your skills and experiences align with the role.
+- Address potential skills gaps and discuss how you plan to bridge them.
+
+### Part 2 Deliverables
+* Submit a resume and cover letter tailored to the role and company to the instructor who will be leading your mock interview at least 24 hours before your scheduled interview time.
+  * A strong cover letter will include your answers to the the "why" questions above.
+  * A strong resume will identify and extract relevant keywords, qualifications, responsibilities, and industry-specific details from the job description and use these extracted details to tailor the resume, ensuring it highlights your skills and experiences that match the requirements of the role.
+
+
+## Part 3: Interview Simulation - Week 5
+The primary goal of the interview simulation, based on your selected job description, is to provide you with realistic and practical experience of a job interview process.
+
+[Interview Simulation Details](./interview_simulation.html)
+
+## Part 4: Job Application Process
+The next step of the employer case study, following the completion of the employer persona, is to apply to your chosen job opportunity using the 3-step application process. 
+
+**IMPORTANT: You do NOT need to wait until after your interview simulation to complete these steps or apply to the job.**
+
+### Application Process:
+
+**Outreach to Someone at the Company**
+- Draft effective outreach messages, which could be emails, LinkedIn messages, or other suitable platforms.
+- Apply strategies to capture the recipient's attention, showcase their genuine interest in the company, and encourage a positive response.
+
+**Prepare for the Meeting**
+- If the outreach leads to a response and a meeting is scheduled, prepare for it by doing things like:
+  * Developing a list of questions and topics to discuss
+  * Researching the person you'll meet with
+  * Considering your own value proposition.
+
+**Complete Application**
+- After networking and meeting with someone from the company, complete the job application process. You can further tailor your resume and cover letter to reflect the insights gained during your research and discussions.
+  - **NOTE:** If you were unable to connect with someone at the company, you should still tailor your resume and cover letter with the details you learned during the Employer Persona Research Phase.
+- Follow through with the application, considering any additional materials or follow-up steps as needed.
+
+
+This comprehensive job search process allows you to take the knowledge and skills you've acquired through the employer persona research and apply them to real-world job applications. It ensures that you approach their job search strategically and professionally, increasing your chances of success in securing roles that align with your career goals and values.
+
+<!-- For additional information and resources on how to find job opportunities and contacts, see the [4-Step Job Application Process Document](https://docs.google.com/document/d/1B39ViRamGHNVLzelnlEIhzLWNwsrPvf1J8MjtxDKgsc/edit#heading=h.ncblao9s0orb). -->
+### Part 4 Deliverables
+* Outline your application process, network efforts, and the outcomes for each step in your [final presentation](./final_presentation.html).
+
+
+
+## Evaluation and Final Presenation
+* [Evaluation Details](./evaluation.html)
+* [Final Presentation Details](./final_presentation.html)
\ No newline at end of file
diff --git a/module4/projects/employer_case_study/final_presentation.md b/module4/projects/employer_case_study/final_presentation.md
new file mode 100644
index 00000000..fe342f52
--- /dev/null
+++ b/module4/projects/employer_case_study/final_presentation.md
@@ -0,0 +1,54 @@
+---
+title: Employer Case Study Final Presentation
+layout: page
+---
+
+[Back to Employer Case Study Overview](./index.html)
+
+
+## Purpose
+
+Your presentation will not only showcase your research and networking efforts but also provide insights into your adaptability and problem-solving skills. It's an opportunity to reflect on your experiences and demonstrate how you've grown and learned throughout the process.
+
+## Structure
+
+- Student-directed presentation (~10-15 minutes)
+    * Develop an organized slide deck or Google document to present your research and job search steps.
+    * Include visual aids, such as charts or graphs, to enhance your presentation.
+- Instructor feedback (~5 minutes)
+
+## Potential Outcomes
+
+- If everything goes according to plan: good luck in the future!
+- If a student fails to present (due to illness, etc), please arrange an alternate time to present to instructors.
+- If a student delivers an exceptionally poor presentation: instructors will determine the next steps.
+
+## Format
+
+Each student will deliver a slide presentation in front of your instructors. The presentation will include the following sections:
+
+1. Summarize Employer Persona Research:
+    * Summarize your employer persona research, emphasizing "Why Us," "Why this Role," and "Why You."
+    * Outline the key findings about the company's culture, mission, and the specific role you're targeting.
+    * Highlight the steps you've taken in the job search process.
+2.  Share Networking Efforts:
+    * Explain how you've networked within the company, whether through LinkedIn, professional events, or other platforms.
+    * Describe your interactions and connections within the organization.
+3. Discuss Outreach Strategies:
+    * Share your outreach messages and strategies for contacting professionals at the company.
+    * Discuss the methods you used to capture their attention and encourage a response.
+4.  Explain Meeting Preparation:
+    * Detail how you prepared for meetings with company representatives, including the questions and topics you planned to discuss.
+    * Address any research conducted on the individuals you interacted with.
+    * Even if a meeting hasn't yet occurred, you should still have some notes prepped so you're ready to go if/when someone gets back to you.
+5. Interview Simulation Preparation
+    * Discuss steps you took to prepare for your interview simulation as a result of your research and networking.
+6. Outcome and Reflection:
+    * Discuss the outcomes of your outreach, networking, and meetings.
+    * Share key learnings, including what went well and what challenges you faced.
+    * Address how you plan to deal with these challenges in future job search efforts.
+7. Technical Roadmap
+    * A summary of your technical roadmap to be carried out in the 6 weeks post-mod 4
+        * **This should include at least 4 stories/issues that you plan to work on for continuing work on your capstone project**
+    * A detailed schedule for the first week after graduation
+    * Here is a link to the [Technical Roadmap template](https://docs.google.com/document/d/1_zKFkT1Ipd0gQn5WSUb_TdCiQhcFXMsRA3vKO72ALi4/edit?usp=sharing). Make a copy of the document and fill in the template.
\ No newline at end of file
diff --git a/module4/projects/employer_case_study/index.md b/module4/projects/employer_case_study/index.md
new file mode 100644
index 00000000..bb41c115
--- /dev/null
+++ b/module4/projects/employer_case_study/index.md
@@ -0,0 +1,32 @@
+---
+title: Employer Case Study
+layout: page
+---
+
+## Learning Goals
+1. Research Skills: Students will learn how to gather comprehensive information about a chosen company, including its history, culture, mission, and values.
+
+2. Alignment with Personal Goals: Students will gain insights into how to assess the alignment between their personal career goals and values with those of a chosen company.
+
+3. Articulating Career Choices: Students will be able to clearly articulate why a chosen company stands out to them and what it represents, as well as define the role title they are targeting within that company.
+
+4. Job Opportunities: Students will learn how to leverage their knowledge about a company to identify specific job opportunities within that organization, considering roles that complement their skills and career aspirations.
+
+5. Communication and Networking: Students will develop skills in obtaining contact information and initiating conversations or networking with representatives from the chosen company.
+
+## Overview
+The employer case study is a comprehensive project where students create a detailed profile for a company they would like to pursue in their job search, including key information about the company's technology stack, features, and business model. They will evaluate the company's strengths, culture, and strategic direction, while also formulating critical questions that are vital to ask during the job application and interview process. 
+
+Additionally, students will present their findings, draft essential essay prompts for future applications and interviews, including "Why us?" to demonstrate their understanding of the company, "Why this role?" to emphasize their alignment with the specific position they are pursuing, and "Why you?" to highlight their qualifications.
+ 
+This project will equip students with the tools and knowledge needed to make informed career decisions and effectively communicate their value to potential employers.
+
+## Expectations
+There are three parts to this project:
+
+* [Employer Research](./expectations.html)
+* [Interview Simulation](./interview_simulation.html)
+* [Final Presenation](./final_presentation.html)
+
+## Evaluation Details
+* [Evaluation](./evaluation.html)
diff --git a/module4/projects/employer_case_study/interview_simulation.md b/module4/projects/employer_case_study/interview_simulation.md
new file mode 100644
index 00000000..efb5bf4c
--- /dev/null
+++ b/module4/projects/employer_case_study/interview_simulation.md
@@ -0,0 +1,55 @@
+---
+title: Employer Case Study Interview Simulation
+layout: page
+---
+
+[Back to Employer Case Study Overview](./index.html)
+
+[Back to Employer Case Study Expectations](./expectations.html)
+
+
+## Overview 
+The primary goal of the interview simulation, based on a selected job description (JD), is to provide students with realistic and practical experience of a job interview process.
+
+
+### Learning Goals
+1. Enhance Interview Skills: Help students develop and refine their interview skills, including answering questions, presenting their qualifications, and showcasing their suitability for the role.
+
+2. Apply Knowledge: Enable students to apply the knowledge and insights gained from their research, such as the SWOT analysis and understanding of the role's requirements, to effectively communicate their alignment with the position.
+
+3. Build Confidence: Boost students' confidence in handling interviews by simulating real-world scenarios. This practice helps reduce anxiety and improve their ability to perform well in actual job interviews.
+
+4. Prepare for Real Interviews: Equip students with the ability to navigate the job market effectively, with a focus on matching their skills and interests to actual job openings. This, in turn, will enhance their chances of securing job opportunities that align with their career goals.
+
+5. Receive Constructive Feedback: Provide students with constructive feedback from instructors and peers. This feedback can help them identify areas for improvement and make necessary adjustments before real job interviews.
+
+By using a job description as the basis for the interview simulation, students can better connect their academic learning with practical career preparation and develop the skills necessary to succeed in their job search endeavors.
+
+## Student Steps for Interview Preparation
+Before the Interview Simulation in Week 5:
+
+* Complete Parts 1 and 2 of the Case Study project:
+    * Find one job role that aligns with your career interests and goals. This role will be the focus of your interview simulation.
+    * Complete the Employer Persona research
+
+
+* Submit Mock Interview Documents
+    * Submit via the form on the calendar ([also linked here](https://docs.google.com/forms/d/e/1FAIpQLScmIo-SF8uxj9obkBEtxOSfPxQgycIYnL_kMBJBBZg23pbMFQ/viewform))
+      * A copy of the Job Description that you've selected for the simulation
+        * IMPORTANT: The job description should be copied into a google doc. Do not just send a link to the website with the posting. If the job posting is taken down, there is no record of the job description for you to reference.
+      * A resume and cover letter tailored to the chosen role
+    * This allows the instructor to prepare relevant interview questions based on the job description and your qualifications, ensuring a realistic and valuable interview experience.
+
+* Create an Interview Preparation Document
+    * Develop an interview preparation document that includes a list of common interview questions and space for your answers.
+    * Also, include a section for questions you intend to ask during the interview. Research the company and the role to formulate insightful questions that demonstrate your genuine interest.
+    * Use this document to practice your responses, ensuring you are well-prepared for the interview and able to showcase your qualifications effectively.
+    * Take a look at these Interview Story Banks to use or get ideas for creating your own.
+
+[Interview Simulation Rubric](./interview_simulation_rubric.html)
+
+## Resources
+* [Interview Story Bank - Make a copy](https://docs.google.com/spreadsheets/d/16aempR55Tej8pPr-l9qq6vBnL4bax9kbGEXA9nO7oVo/edit#gid=882531233)
+* [Interview Story Bank in Notion](https://perpetual-seeker-acf.notion.site/Behavioral-Interviews-Creating-Your-Story-Bank-1-42398184f39b4947a79c9468272c2955)
+* [Technical Interview Questions](../../lessons/technical-interview-questions.html)
+* [Behavioral Interview Questions](../../lessons/behavioral-interview-questions.html)
\ No newline at end of file
diff --git a/module4/projects/employer_case_study/interview_simulation_rubric.md b/module4/projects/employer_case_study/interview_simulation_rubric.md
new file mode 100644
index 00000000..8f552055
--- /dev/null
+++ b/module4/projects/employer_case_study/interview_simulation_rubric.md
@@ -0,0 +1,29 @@
+---
+title: Employer Case Study Interview Simulation Rubric
+layout: page
+---
+
+[Back to Employer Case Study Overview](./index.html)
+
+[Back to Interview Simulation Expectations](./interview_simulation.html)
+
+Students are expected to score primarily in the "Meets Expectations" category. If any score is "Below Expectations", student will be asked to do a second interview simulation.
+
+**Research and Preparation**
+- **Exceeds Expectations:** Student provides a job description to the instructor in advance, all application materials are tailored to the specific role, and student makes strong connections between their work history and values to the needs of the company and the role for which they are interviewing.
+- **Meets Expectations:** Student provides a job description to the instructor in advance and all application materials are tailored to the specific role. Student is able to loosely relate their experience back to the role or company when answering questions.
+- **Approaching Expectations:** Student provides a job description to the instructor but resume and cover letter are not tailored to the company or role.
+- **Below Expectations:** Student fails to provide a job description to the instructor in advance of their interview simulation. Job hunt documents like resume and cover letter are incomplete or missing.
+
+**Behavioral Interview**
+- **Exceeds Expectations:** Student gives strong and specific examples following a STAR-like pattern when answering questions. Details exemplify the student's strengths and opportunities. Student is able to make strong connections from their experience to the company or job description.
+- **Meets Expectations:** Student gives strong examples when answering questions. Enough detail is given to satisfy what is being asked without unrelated information. Student is able to relate their experience to the company or job description.
+- **Approaching Expectations:** Student is able to answer questions, but answers may lack clarity or uncertainty, or lack relevant examples. 
+- **Below Expectations:** Student is unable to answer questions effectively. This could look like not answering at all, answering a significantly different question than was asked, or lacking cohesion in storytelling (rambling or jumping around).
+
+
+**Technical Interview**
+- **Exceeds Expectations:** Student gives strong and specific examples with accurate technical terminology when answering questions. Student is able to relate their technical experience or interests to the company or job description.
+- **Meets Expectations:** Student uses accurate technical terminology when answering questions. Enough detail is given to satisfy what is being asked. Student effectively uses Graceful Exit strategies when faced with questions they do not know the answers to, including behaviors like note taking, asking for clarification, or offering later follow-up.
+- **Approaching Expectations:** Student gives short answers with few specific details or examples. Answers may lack technical clarity. 
+- **Below Expectations:** Student is unable to answer questions effectively. This could look like not answering at all ("I don't know"), answering a significantly different question than was asked, or using little or incorrect technical terminology.
\ No newline at end of file
diff --git a/module4/projects/employer_case_study/swot_analysis.md b/module4/projects/employer_case_study/swot_analysis.md
new file mode 100644
index 00000000..f7f0dae9
--- /dev/null
+++ b/module4/projects/employer_case_study/swot_analysis.md
@@ -0,0 +1,104 @@
+---
+title: SWOT Analysis of a Job Description
+layout: page
+---
+
+[Back to Employer Case Study Overview](./index.html)
+
+[Back to Employer Case Study Expectations](./expectations.html)
+
+## Overview
+
+Creating a SWOT analysis for a job description can be a helpful tool for customizing your job application materials and preparing for interviews. By preparing examples and proactively addressing gaps, you will show your understanding of the role, meet the requirements, and demonstrate your unique value.
+
+## Conduct A SWOT Analysis of the Job Description
+**NOTE**
+  * A best practice is to copy the Job Description (JD) into a Google doc in case the link expires. 
+
+### Strengths:
+- List/Highlight your strengths that match the job requirements.
+  - Proficient in programming languages (Java, Python)
+  - Strong leadership skills with a track record of managing teams
+  - Exceptional customer service skills
+  - Experienced in working collaboratively in a team
+  - Familiarity with the location
+
+### Weaknesses:
+- List/highlight areas where you fall short of the job requirements.
+  - Limited experience with a specific technology or software
+  - No formal education in a required field
+  - Limited years of experience in a relevant role
+  - Lack of certification or specific skillset
+
+### Opportunities:
+- Prepare examples of how you can overcome your weaknesses.
+  - Willingness and ability to quickly learn new technologies (provide specific examples)
+  - Relevant life experiences or volunteer work that demonstrate transferable skills (connect to the job)
+  - Courses or certifications in progress or planned to acquire required skills
+  - Successful projects or initiatives that showcase adaptability and quick learning
+
+### Threats:
+- External factors that are beyond your control. Be prepared to acknowledge and address potential concerns. See potential ways to address common concerns for career switchers and new developers below.
+  - Competition from candidates with more education and experience
+  - Economic or industry-related challenges
+  - Changes in company structure or industry trends
+
+
+### Customization and Application:
+- List keywords and statements to include in your resume and cover letter.
+  - Highlight relevant strengths and accomplishments that match job requirements
+  - Tailor your application materials to address opportunities and demonstrate your unique value
+  - Prepare for interviews with specific examples and strategies based on your analysis
+
+### Application Stage:
+- Record the status of your application.
+  - Application submitted on [Date]
+  - Contacted [Contact Person] at the company
+
+Remember to maintain this document as a reference for each job you apply for and update it as needed. It will help you stay organized and effectively customize your applications.
+
+
+## ADDRESSING PERCEIVED WEAKNESSES AND GAPS
+
+Know your Differentiators. Some examples might be that you:
+  - Are multilingual
+  - Have a rare combination of industry skills (MBA and Lawyer)
+  - Have a special talent that is relevant to your field such as a published author.
+  - Completed an expat assignment or have extensive global or “in-country” experience
+  - Possess deep industry or product expertise
+  - Have a unique approach to your work or knack for something.
+
+Show the following:
+  - Be honest about your background
+  - Show that you understand why the skill is important to the role
+  - Illustrate how you’re proactively working to learn the skills right now. 
+
+Demonstrate Willingness to Learn:
+  - Emphasize your eagerness and ability to learn and adapt. - Share examples from your past experiences where you quickly acquired new skills or knowledge.
+
+Highlight Transferable Skills:
+  - If you lack specific qualifications, focus on transferable skills. Explain how skills from previous roles or experiences can be applied to the new position.
+
+Showcase Relevant Experience:
+  - If you lack direct experience, emphasize any relevant experience or projects you've worked on that demonstrate your ability to handle similar tasks.
+
+Mention Ongoing Learning Initiatives:
+  - Discuss any courses, certifications, or training you are currently taking or plan to pursue to bridge your skill gaps.
+
+Address Weaknesses in a Positive Light:
+  - Frame your weaknesses as areas for growth and development, not as insurmountable obstacles. Show how you're eager to grow in these areas.
+
+Ask Smart Questions:
+  - During the interview, ask questions about how the company supports employee growth and development. This can indicate your interest in addressing your weaknesses.
+
+Showcase Soft Skills:
+  - Soft skills like communication, adaptability, problem-solving, and teamwork can often compensate for technical weaknesses. Highlight these skills.
+
+Prepare for Behavioral Questions:
+  - Be ready to answer behavioral interview questions that demonstrate your ability to handle challenging situations and adapt to change.
+
+Focus on Fit and Values:
+  - Emphasize your alignment with the company's culture and values, as this can offset certain skill gaps.
+  - If you feel the interviewer has concerns about your weaknesses, directly address these concerns and provide additional examples of your potential and commitment to growth.
+
+Remember that employers often appreciate candidates who are self-aware and proactive about addressing their weaknesses. It's about demonstrating your ability to recognize your limitations and your dedication to personal and professional development.
\ No newline at end of file

From 0005f351974871b44edcb3cff97aa58bfe2b0134 Mon Sep 17 00:00:00 2001
From: Chris Simmons <chris@turing.edu>
Date: Fri, 17 May 2024 12:17:47 -0400
Subject: [PATCH 11/15] Fixing job seekers calendar not displaying (indenting
 in MD)

---
 job_seekers/index.md | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/job_seekers/index.md b/job_seekers/index.md
index 8c7d3d67..1bb4c8e4 100644
--- a/job_seekers/index.md
+++ b/job_seekers/index.md
@@ -18,25 +18,25 @@ Join  the following Slack communities:
 The Graduate Services Events Calendar provides information for upcoming group check-ins, guest speakers, and any additional events for job seekers. 
 
 <div class="responsive-iframe-container">
-  <div class='tablet'>
-    <iframe src="https://calendar.google.com/calendar/embed?src=casimircreative.com_1ljkgo2l95s8f2p1jpi6shq678%40group.calendar.google.com&ctz=America%2FDenver&amp;mode=week" style="border-width:0" frameborder="0" scrolling="no"></iframe>
-  </div>
-  <div class='desktop'>
-    <iframe src="https://calendar.google.com/calendar/embed?src=casimircreative.com_1ljkgo2l95s8f2p1jpi6shq678%40group.calendar.google.com&ctz=America%2FDenver&amp;mode=week" style="border-width:0" frameborder="0" scrolling="no"></iframe>
-  </div>
+<div class='tablet'>
+<iframe src="https://calendar.google.com/calendar/embed?src=casimircreative.com_1ljkgo2l95s8f2p1jpi6shq678%40group.calendar.google.com&ctz=America%2FDenver&amp;mode=week" style="border-width:0" frameborder="0" scrolling="no"></iframe>
+</div>
+<div class='desktop'>
+<iframe src="https://calendar.google.com/calendar/embed?src=casimircreative.com_1ljkgo2l95s8f2p1jpi6shq678%40group.calendar.google.com&ctz=America%2FDenver&amp;mode=week" style="border-width:0" frameborder="0" scrolling="no"></iframe>
+</div>
 </div>
 
 Events may also appear in the Turing Community Calendar.
 
 <div class="responsive-iframe-container">
-  <div class='tablet'>
-    <iframe src="https://calendar.google.com/calendar/embed?showTitle=0&amp;showPrint=0&amp;showCalendars=0&amp;mode=AGENDA&amp;height=400&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=casimircreative.com_ronr9dk92ndvlhsk03kf8jd2ro%40group.calendar.google.com&amp;color=%2323164E&amp;ctz=America%2FDenver"
-      style="border-width:0" frameborder="0" scrolling="no"></iframe>
-  </div>
-  <div class='desktop'>
-    <iframe src="https://calendar.google.com/calendar/embed?showTitle=0&amp;showNav=1&amp;showDate=0&amp;showPrint=0&amp;showTabs=0&amp;showCalendars=0&amp;showTz=0&amp;mode=WEEK&amp;height=400&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=casimircreative.com_ronr9dk92ndvlhsk03kf8jd2ro%40group.calendar.google.com&amp;color=%2323164E&amp;ctz=America%2FDenver"
-      style="border-width:0" frameborder="0" scrolling="no"></iframe>
-  </div>
+<div class='tablet'>
+<iframe src="https://calendar.google.com/calendar/embed?showTitle=0&amp;showPrint=0&amp;showCalendars=0&amp;mode=AGENDA&amp;height=400&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=casimircreative.com_ronr9dk92ndvlhsk03kf8jd2ro%40group.calendar.google.com&amp;color=%2323164E&amp;ctz=America%2FDenver"
+  style="border-width:0" frameborder="0" scrolling="no"></iframe>
+</div>
+<div class='desktop'>
+<iframe src="https://calendar.google.com/calendar/embed?showTitle=0&amp;showNav=1&amp;showDate=0&amp;showPrint=0&amp;showTabs=0&amp;showCalendars=0&amp;showTz=0&amp;mode=WEEK&amp;height=400&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=casimircreative.com_ronr9dk92ndvlhsk03kf8jd2ro%40group.calendar.google.com&amp;color=%2323164E&amp;ctz=America%2FDenver"
+  style="border-width:0" frameborder="0" scrolling="no"></iframe>
+</div>
 </div>
 
 ### Recorded Events

From ff2cf1b0c466fd9e1b15c845e22f812b3c9d91b0 Mon Sep 17 00:00:00 2001
From: Chris Simmons <chris@turing.edu>
Date: Fri, 17 May 2024 12:19:12 -0400
Subject: [PATCH 12/15] Fixing job seekers nav link formatting

---
 _sass/sidebar.scss | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_sass/sidebar.scss b/_sass/sidebar.scss
index 84738220..78ffc7b2 100644
--- a/_sass/sidebar.scss
+++ b/_sass/sidebar.scss
@@ -8,7 +8,7 @@ nav {
 
 .nav-links {
   display: grid;
-  grid-template-columns: auto 100px 100px 100px 100px 100px 100px 225px;
+  grid-template-columns: auto 100px 100px 100px 100px 100px 125px 225px;
   grid-template-rows: 120px;
   align-items: center;
   justify-items: center;

From 385c9bb483b5df2d576b8eedb9f5efe0abf58cd4 Mon Sep 17 00:00:00 2001
From: Chris Simmons <chris@turing.edu>
Date: Fri, 17 May 2024 12:20:50 -0400
Subject: [PATCH 13/15] Adds cursor to button hover

---
 _sass/buttons.scss | 1 +
 1 file changed, 1 insertion(+)

diff --git a/_sass/buttons.scss b/_sass/buttons.scss
index e489201f..590ad177 100644
--- a/_sass/buttons.scss
+++ b/_sass/buttons.scss
@@ -9,6 +9,7 @@
   text-transform: uppercase;
   padding: 16px 30px 16px;
   margin: 5px;
+  cursor: pointer;
 }
 
 .btn-dark {

From fb2e38ba53fb4b0abf373ddc1ba17cb3b91bc145 Mon Sep 17 00:00:00 2001
From: Chris Simmons <chris@turing.edu>
Date: Fri, 17 May 2024 12:32:30 -0400
Subject: [PATCH 14/15] Fixing absolute links

---
 job_seekers/index.md                        | 12 ++++++------
 job_seekers/resources/branding_resources.md |  2 +-
 job_seekers/resources/readme_resources.md   |  2 +-
 module1/index.md                            |  4 ++--
 module2/index.md                            |  6 +++---
 module3/index.md                            |  6 +++---
 module4/index.md                            |  6 +++---
 7 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/job_seekers/index.md b/job_seekers/index.md
index 1bb4c8e4..4230a163 100644
--- a/job_seekers/index.md
+++ b/job_seekers/index.md
@@ -52,7 +52,7 @@ Schedule some career coaching time with [Tracey Monteiro](https://go.oncehub.com
 You can grab time with an alum to prepare for FE/BE technical and behavioral interviews and live coding challenges. You can grab a slot via OnceHub [here](https://go.oncehub.com/turingmockinterviews).
 
 ### Receive an offer? 
-The Turing Staff happy to help you navigate the offer and negotiations process - reach out to whoever you feel comfortable to. You can also check out [these resources on negotiations](./resources/negotiations.md).
+The Turing Staff happy to help you navigate the offer and negotiations process - reach out to whoever you feel comfortable to. You can also check out [these resources on negotiations](./resources/negotiations).
 
 ## Signed an offer?
 Please submit the two surveys below - we want to celebrate your accomplishment, and continue improving our processes!
@@ -63,21 +63,21 @@ Please submit the two surveys below - we want to celebrate your accomplishment,
 [Check out these Applicant Tracking System Tips!](https://www.jobscan.co/applicant-tracking-systems) and get insights on your resume by scanning it through [Jobscan.co](https://www.jobscan.co)
 
 ### Terminal
-Turing provides a space for professional portfolios on our website. These portfolios can be used during your job hunt - you can send out links to your profile, and Turing staff may share your profile to employers who come to us asking for candidates.  See the [Terminal Directions Page](./resources/terminal_directions.md) for more information!
+Turing provides a space for professional portfolios on our website. These portfolios can be used during your job hunt - you can send out links to your profile, and Turing staff may share your profile to employers who come to us asking for candidates.  See the [Terminal Directions Page](./resources/terminal_directions) for more information!
 
 ## Resources
 
 ### Networking 
-* [Outreach & Networking Resources](./resources/outreach_networking_resources.md)
+* [Outreach & Networking Resources](./resources/outreach_networking_resources)
 
 ### Interviewing
-* [Compilation of Lots of Interview Prep Resources](./resources/interview_prep_resources.md)
+* [Compilation of Lots of Interview Prep Resources](./resources/interview_prep_resources)
 * Recommended Reading:
    * [Cracking the Coding Interview](https://bookshop.org/books/cracking-the-coding-interview-189-programming-questions-and-solutions/9780984782857)
 
 ### Materials
-* [Branding Resources for LinkedIn, GitHub, and Twitter](./resources/branding_resources.md)
-* [Resume Resources](./resources/resume_resources.md)
+* [Branding Resources for LinkedIn, GitHub, and Twitter](./resources/branding_resources)
+* [Resume Resources](./resources/resume_resources)
 * [Cover Letter Resources](./resources/cover_letter_resources)
 * [Terminal Portfolio Directions](./resources/terminal_directions)
 * [Resources for Writing READMEs](./resources/readme_resources)
diff --git a/job_seekers/resources/branding_resources.md b/job_seekers/resources/branding_resources.md
index 19d412c7..2184f311 100644
--- a/job_seekers/resources/branding_resources.md
+++ b/job_seekers/resources/branding_resources.md
@@ -132,7 +132,7 @@ Make sure that all of your projects have a ReadMe. Think about the ReadMe as enc
 * It's an advertisement of your work. How can you highlight important accomplishments and challenges?
 * It's documentation. If someone else were going to use your project, what do they need to know?
 
-[Here are resources for writing excellent ReadMes](/resources/readme_resources)
+[Here are resources for writing excellent ReadMes](readme_resources)
 
 ### Twitter Overview <a name="twitter"></a>
 You don't *have* to have a Twitter account. But a lot of software developers (aka the people you want to connect with) are using Twitter, so we would highly recommend that you create a profile if you don't have one already!
diff --git a/job_seekers/resources/readme_resources.md b/job_seekers/resources/readme_resources.md
index f54474ea..947bf6f8 100644
--- a/job_seekers/resources/readme_resources.md
+++ b/job_seekers/resources/readme_resources.md
@@ -6,7 +6,7 @@ title: Resources for Writing Great READMEs
 Check out some of these resources our instructors recommend:
 
 * Having trouble figuring out how to outline your README? [Check out this template](https://readme.so/editor) or [this template](https://github.com/PurpleBooth/a-good-readme-template)
-* [BE Mod 2 Lesson on Writing a great README](https://backend.turing.edu/module2/lessons/how_to_write_a_great_readme)
+* Mod 2 Lesson on Writing a great README (TBA)
 * [Thoughtbot Blog Post: How to Write a Great README](https://thoughtbot.com/blog/how-to-write-a-great-readme)
 * [Dan Bader: How to Write a Great Readme for Your GitHub Project](https://dbader.org/blog/write-a-great-readme-for-your-github-project). Note: you may have to click x on the ad to get to the page
 * [TPW’s README-Driven-Development](https://www.google.com/url?q=http://tom.preston-werner.com/2010/08/23/readme-driven-development.html&sa=D&source=calendar&ust=1623259373515000&usg=AOvVaw2vFiJ7n-4VoFJz9Bn60PdS)
diff --git a/module1/index.md b/module1/index.md
index 922a7249..445de3fc 100644
--- a/module1/index.md
+++ b/module1/index.md
@@ -7,7 +7,7 @@ subheading: Fundamentals of Programming
 ## Overview
 
 ## Curriculum
-- [Lessons](./lessons/index.md)
-- [Projects](./projects/index.md)
+- [Lessons](./lessons)
+- [Projects](./projects)
 
 ## Other Resources
diff --git a/module2/index.md b/module2/index.md
index 643cc47b..8e32a6e7 100644
--- a/module2/index.md
+++ b/module2/index.md
@@ -7,8 +7,8 @@ subheading: Web Applications with Ruby
 ## Overview
 
 ## Curriculum
-- [Intermission Pre-Work](./intermission_work/index.md)
-- [Lessons](./lessons/index.md)
-- [Projects](./projects/index.md)
+- [Intermission Pre-Work](./intermission_work)
+- [Lessons](./lessons)
+- [Projects](./projects)
 
 ## Other Resources
\ No newline at end of file
diff --git a/module3/index.md b/module3/index.md
index a0c22ae2..9d7e1e35 100644
--- a/module3/index.md
+++ b/module3/index.md
@@ -7,8 +7,8 @@ subheading: Building and Consuming APIs
 ## Overview
 
 ## Curriculum
-- [Intermission Pre-Work](./intermission_work/index.md)
-- [Lessons](./lessons/index.md)
-- [Projects](./projects/index.md)
+- [Intermission Pre-Work](./intermission_work)
+- [Lessons](./lessons)
+- [Projects](./projects)
 
 ## Other Resources
\ No newline at end of file
diff --git a/module4/index.md b/module4/index.md
index 7bc3736c..c7dd2b43 100644
--- a/module4/index.md
+++ b/module4/index.md
@@ -7,8 +7,8 @@ subheading: Finding Your Specialty
 ## Overview
 
 ## Curriculum
-- [Intermission Pre-Work](./intermission_work/index.md)
-- [Lessons](./lessons/index.md)
-- [Projects](./projects/index.md)
+- [Intermission Pre-Work](./intermission_work)
+- [Lessons](./lessons)
+- [Projects](./projects)
 
 ## Other Resources
\ No newline at end of file

From 72f8854c2615161ab271d13481ed6e4a6cb5ea45 Mon Sep 17 00:00:00 2001
From: Chris Simmons <chris@turing.edu>
Date: Fri, 17 May 2024 12:37:04 -0400
Subject: [PATCH 15/15] Fixing absolute links, fixing broken links

---
 .../resources/cover_letter_resources.md       |  2 +-
 module1/lessons/index.md                      | 50 +++++++++----------
 module2/lessons/index.md                      |  2 +-
 module3/pd/index.md                           |  8 +--
 module4/pd/index.md                           |  2 +-
 5 files changed, 32 insertions(+), 32 deletions(-)

diff --git a/job_seekers/resources/cover_letter_resources.md b/job_seekers/resources/cover_letter_resources.md
index f1a4b34d..8a2467c0 100644
--- a/job_seekers/resources/cover_letter_resources.md
+++ b/job_seekers/resources/cover_letter_resources.md
@@ -4,7 +4,7 @@ title: Cover Letter Resources
 ---
 
 ## Overview
-If we were to sum up the cover letter and how it compares to your resume in one sentence, the resume is about you while the cover letter is about *them (the company.* 
+If we were to sum up the cover letter and how it compares to your resume in one sentence, the resume is about you while the cover letter is about *them (the company).* 
 
 ### Templates to Get You Started
 Below are Cover letter templates to help get you started, but make sure to *customize* your cover letter each time you write one:
diff --git a/module1/lessons/index.md b/module1/lessons/index.md
index 5fb178c7..0a1d9ed0 100644
--- a/module1/lessons/index.md
+++ b/module1/lessons/index.md
@@ -6,41 +6,41 @@ title: Module 1 - Lessons
 <!-- Comment the following lessons in as they are updated and deemed ready to go! -->
 
 ## Ruby Mechanics
-<!-- * [Methods & Return Values](./methods_and_return_values.md) -->
-<!-- * [Objects, Classes, & Instances](./objects_classes_instances.md) -->
-<!-- * [Arrays](./arrays.md) -->
-<!-- * [Scope](./scope.md) -->
-<!-- * [Flow Control](./flow_control.md) -->
-<!-- * [Beginner Enumerables](./beginner_enumerables.md) -->
-<!-- * [Hashes](./hashes.md) -->
-<!-- * [Boolean Logic](./boolean_logic.md) -->
-<!-- * [Nested Collections](./nested_collections.md) -->
+<!-- * [Methods & Return Values](./methods_and_return_values) -->
+<!-- * [Objects, Classes, & Instances](./objects_classes_instances) -->
+<!-- * [Arrays](./arrays) -->
+<!-- * [Scope](./scope) -->
+<!-- * [Flow Control](./flow_control) -->
+<!-- * [Beginner Enumerables](./beginner_enumerables) -->
+<!-- * [Hashes](./hashes) -->
+<!-- * [Boolean Logic](./boolean_logic) -->
+<!-- * [Nested Collections](./nested_collections) -->
 <!-- * [Reaching Through Objects](!needs lesson plan!) -->
-<!-- * [Intermediate Enumerables](./intermediate_enumerables.md) -->
-<!-- * [Nested Iteration Workshop](./nested_iteration_workshop.md) -->
-<!-- * [Class Methods](./class_methods.md) -->
-<!-- * [Modules](./modules.md) -->
-<!-- * [Inheritance](./inheritance.md) -->
-<!-- * [CSV Workshop](./csv_walkthrough.md) -->
-<!-- * [Ruby Object Model](./ruby_object_model.md) -->
+<!-- * [Intermediate Enumerables](./intermediate_enumerables) -->
+<!-- * [Nested Iteration Workshop](./nested_iteration_workshop) -->
+<!-- * [Class Methods](./class_methods) -->
+<!-- * [Modules](./modules) -->
+<!-- * [Inheritance](./inheritance) -->
+<!-- * [CSV Workshop](./csv_walkthrough) -->
+<!-- * [Ruby Object Model](./ruby_object_model) -->
 
 ## Design
-<!-- * [Design Principles](./design_principles.md) -->
-<!-- * [How the Web Works](./intro_to_how_the_web_works.md) -->
+<!-- * [Design Principles](./design_principles) -->
+<!-- * [How the Web Works](./intro_to_how_the_web_works) -->
 
 ## Testing
-<!-- * [Intro to Testing](./intro_to_testing.md) -->
-<!-- * [Mocks & Stubs](./mocks_stubs.md) -->
-<!-- * [Test Driven Development](./test_driven_development.md) -->
+<!-- * [Intro to Testing](./intro_to_testing) -->
+<!-- * [Mocks & Stubs](./mocks_stubs) -->
+<!-- * [Test Driven Development](./test_driven_development) -->
 
 ## Debugging
 <!-- * [Debugging Exercises](!needs lesson plan!) -->
-<!-- * [Debugging Techniques](./debugging_techniques.md) -->
+<!-- * [Debugging Techniques](./debugging_techniques) -->
 
 ## Version Control
-<!-- * [Git Workflow](./git-collaboration.md) -->
-<!-- * [Git for Pairs](./git_for_pairs.md) -->
-<!-- * [Git Cheat Sheet](./git_cheatsheet.md) -->
+<!-- * [Git Workflow](./git-collaboration) -->
+<!-- * [Git for Pairs](./git_for_pairs) -->
+<!-- * [Git Cheat Sheet](./git_cheatsheet) -->
 
 ## Professional Development
 * [Overview](./pd_overview)
diff --git a/module2/lessons/index.md b/module2/lessons/index.md
index 1e9a5b2b..1294e842 100644
--- a/module2/lessons/index.md
+++ b/module2/lessons/index.md
@@ -6,6 +6,6 @@ title: Module 2 - Lessons
 ## Professional Development
 * [Overview](./pd_overview)
 * [Building Your Brand on LinkedIn](https://docs.google.com/presentation/d/e/2PACX-1vS8CZUjYkpnkTJrp2Ga8um-UUFUsJ-5JA85FF9x875J-l_eKy7IyL47sAt8kl_FOlg7rG5ntVxpk5he/pub?start=false&loop=false&delayms=3000)
-* [Networking, Outreach and Coffee Chats](./networking.md)
+* [Networking, Outreach and Coffee Chats](./networking)
 * [Networking](https://docs.google.com/presentation/d/e/2PACX-1vQa672IV-XwWG9q-ujEJ0w72QCBzf4jVMNI-trwLuKt9kk_ewe0l6Mk6YSWoo9UYMETbJ5RZ3akKyux/pub?start=false&loop=false&delayms=3000)
 * [Getting Job Hunt Ready](https://docs.google.com/presentation/d/e/2PACX-1vTDlRAiXiR_PSsAFGQtP8je_pcUWmLdk1kYc4jO4hTyzxDuksNWUMdUITMNXp1pRFMM0gKDiAVyXL0c/pub?start=false&loop=false&delayms=3000)
\ No newline at end of file
diff --git a/module3/pd/index.md b/module3/pd/index.md
index cb1dc53d..90613eb6 100644
--- a/module3/pd/index.md
+++ b/module3/pd/index.md
@@ -4,7 +4,7 @@ title: Module 3 - Professional Development
 ---
 
 ## General resources:
-[Mod 3 PD Overview](./lessons/pd_overview.md)
+[Mod 3 PD Overview](./lessons/pd_overview)
 
 ### Intermission Work: 
   * [Crafting A Tech Resume](https://docs.google.com/presentation/d/e/2PACX-1vRDqx6yceiHWcOEiKjEp0Hr43o6yb4WtF60jJFRAOKCeTIbrYf0iA9bDMk1jumn1lMP0R-5MV-wfkMY/pub?start=false&loop=false&delayms=3000&slide=id.p1)
@@ -13,18 +13,18 @@ title: Module 3 - Professional Development
   * [Intro to PD & Live Resume Session](https://docs.google.com/presentation/d/1hjEDTWnlnZSxC-1SoYqMIhWN7cYH-ObV54v7QU-5rtI/edit#slide=id.p3)
     
 ### Week 2:
-  * [Interview Preparation- Putting It All Together](./lessons/interview_preparation.md)
+  * [Interview Preparation- Putting It All Together](./lessons/interview_preparation)
   * [Resume Storytelling Workshop](https://docs.google.com/presentation/d/1TPvCPkxJhM_nFzAxbjlDqvSUxlHhrAfmcm4cgxqchgk/edit#slide=id.p)
   * [ ] **Deliverable #1:** Submit [Exit Ticket](https://www.google.com/url?q=https://forms.gle/1WHVG6iiHX6bkfS97&sa=D&source=calendar&ust=1696369633966175&usg=AOvVaw1jc9wNuKyOBWJnI12aUW9u) by Wednesday
   * [ ] **Deliverable #2:** Submit [Resume Draft](https://forms.gle/awwALTSFZKDhs33b8) by Friday.
 
 ### Week 3: 
-  * [Cover Letters Made Easy](./lessons/coverletters_made_easy.md)
+  * [Cover Letters Made Easy](./lessons/coverletters_made_easy)
   * [ ] **Deliverable #3:** Submit [Cover Letter Draft](https://forms.gle/nqNA3quvJ536juik9) by Friday.
 
 ### Week 4: 
   * [The Application Process](https://docs.google.com/presentation/d/e/2PACX-1vQQb_NqtACy5ea-EbE8KJX7QA62bpOC_YMB6tzsyL_dRuZqyVLKfAIZkFcLRj9MefGUuvT-WbRUzTQS/pub?start=false&loop=false&delayms=3000)
-  * [Behavioral Interview Preparation](./lessons/behavioral_interview_preparation.md) - paired with Front-end cohort
+  * [Behavioral Interview Preparation](./lessons/behavioral_interview_preparation) - paired with Front-end cohort
  
 ### Week 5:
   * Review Roundtable of Career Materials 
diff --git a/module4/pd/index.md b/module4/pd/index.md
index 682ea0b8..f6e6d4b6 100644
--- a/module4/pd/index.md
+++ b/module4/pd/index.md
@@ -5,7 +5,7 @@ title: Module 4 - Professional Development
 
 ### Deliverable 1: Complete Terminal or Personal portfolio
   * Students may choose to build a personal portfolio OR build a portfolio using Terminal
-    * Follow [these directions](../../job_seekers/resources/terminal_directions.md) to update and submit your portfolio.
+    * Follow [these directions](../../job_seekers/resources/terminal_directions) to update and submit your portfolio.
         * If you build your own portfolio, you should start with the "About Me Section" in the link above to guide the content you put on your portfolio.
     * Add at least 2 projects and use [these guidelines](https://docs.google.com/document/d/1zKePxhD-xQdLRPeLI21E71ET_U88ZZ-SKTQjRVzs8tM/edit) to help you create the descriptions
     * Upload your polished and targeted resume