Day 11:

Date: 2024-09-16

Morning Pregame and Introduction

introduction summary

Dave

personal context

Will

Good morning Dave and readers! I'm feeling so amazing today. I think it's time to tell a secret, I have a call with a company today! It's the first call and likely more of a screening call. I was referred by a friend to a startup company he works at, funnily enough founded by the founder of Sunday Hustle group himself. It's an incredibly interesting company working on a radical new approach to databases on the frontend of applications. Very excited for this opportunity!

daily goals

Will

First and foremost, I need to prepare for my call. I need to mentally prepare myself and get locked in. I really need to focus on doing some more inital research about the company and their technology. I've already done extensive research, but I need to take some time to collect my thoughts. I want to come up with some interesting questions to ask during the interview, both because that's good signal in an interview and fuck I'm curious! I also need to spend time going back to re-document a lot of my old projects. That means actually going on github and writing project readmes, and then adding these projects onto my website under the projects tab.

learning focus

Will

Lots to think about today. My soft skills during a recruiter screen are going to be tested today. My communication will be a large point of work today. How well can I communicate my technical abilities, as well as give great signal to an interviewer. On a more technical note, I need to really learn how to better document projects.

challenges

Will

I'm nervous for the phone interview. 100%. Nervous and excited. I'm worried that for reworking my projects, I may be slow in writing and don't really know how to write good high level documentation.

plan of action

Will

So without further ado, let's get going. It's 9:33 AM right now and my phone screen is at 11:00 AM. I'm going to split this up into 3 segments, pre interview, interview, and post interview:

Pre Interview:

  1. I need to spend maybe 45 minutes compiling a list of projects. Since I want to be able to refer to projects during the interview, quality is going to be more important than quality.
  2. I need to write BASIC documentation for all projects I want to show off.
  3. I need to take my documentation from github and transfer that to the projects page on my website.
  4. After documenting my projects as a first pass, I can spend more time organizing/ordering my projects and focus on polishing my most important projects.
  5. 30 minutes before the interview starts, I need to go over my research about the company. I need to get a piece of paper out and brainstorm. Questions for the interviewer, a game plan, and other general items.

During Interview:

  1. Be myself. My friend who referred me gave me advice on to "not be too professional", and to "just be myself".
  2. Easy. I'm always myself, for better or for worse lol
  3. Listen.
  4. Ask deep technical questions.
  5. Avoid monologuing.
  6. Take some notes!

Post Interview:

  1. Reflect on how the interview went.
  2. Think about next steps for moving the process along.
  3. Continue massive effort of documentation.

focus level

enthusiasm level

burnout level

Task 0

task reflection summary

Dave

task goal

Will

Pre Interview - Document my previous projects at a high level and prepare for phone screen.

task description

Will

I'm going to go back and look through my github. I need to write basic documentation for all of my projects. I need to then take that documentation and add it to the websites "projects" page. Also, take some time before the interview to condense my research on the company and do a little brainstorming. I'm not going to write a script, but I'm going to at least write down a list of questions.

task expected difficulty

task planned approach

Will

I'll start by going through all of my github projects:

  1. List out all of the projects I want to showcase.
  2. Grab documentation for projects that already have it.
  3. For projects that don't have documentation, write a barebones simple README
  4. Start transfering this information into React components on my projects page.
  5. Polish everything.
  6. Add pictures, links, and make each project on the page more interactive.

I'll end by taking time to brainstorm and create a list of questions for my phone screen.

task progress notes

Will


Reflection

learning outcomes

Will


next steps short term

Will


next steps long term

Will