Skip to content

Instantly share code, notes, and snippets.

@robertorodriguez12
Created October 29, 2020 19:34
Show Gist options
  • Save robertorodriguez12/02141944a85a246613deeeab7a4b3a31 to your computer and use it in GitHub Desktop.
Save robertorodriguez12/02141944a85a246613deeeab7a4b3a31 to your computer and use it in GitHub Desktop.

Prepare for Job Shadow: RxRevu

  • Activities: what questions do you have about the activities that a software developer does on a daily basis?

    1. What does an average day look like?
    2. What does a busy day/week look like?
  • Environment: what questions do you have about the overall environment and culture of this workplace?

    1. What is the working environment like? Is it cubicles or an open space?
    2. How approachable are most individuals at your company when it comes to reaching out for help?
  • Interactions: what questions do you have about the team at this company? What do you hope to see in your interactions during the shadow?

    1. During this shadow, I am looking forward to observing how the teams interact with one another, the workflow and the overall demeanor of the group.
  • Objects: what questions do you have about the code or the product?

    • N/A
  • Users: what questions do you have about how the company interacts with their users?

    • N/A

After the Job Shadow, reflect on the same questions; what are your takeaways from the shadow?

  • Activities: what was engaging to the person/people you shadowed?

    1. During the job shadow, I was in a group with 3 employees and 3 Turing students, we were able to observe the way they interacted with one another, the workflow and gave me a deeper understanding on how a regular day may look like.
  • Environment: what did you notice about how they talked about the culture and environment of this company?

    1. The group overall was very laid back with one another.
    2. They were supportive of each other.
    3. Relaxed yet professional environment.
  • Interactions: what did you notice about your interactions with this person/people?

    1. The employees that we were job shadowing were very open to us just hopping of mute and asking questions, they were very willing to answer them to the best of their knowledge.
  • Objects: what did you learn about their approach to code and/or product development?

    1. I learned that their approach to code was very similar to the approach we take here at Turing, they wrote tests first in order to let the errors guide them. It helped put a lot more things into perspective that Turing is teaching us.
  • Users: what did you learn about their approach to their users?

    1. These individuals are passionate about what they are doing, most of the individuals we shadowed/met had some sort of connection/story as to why this type of product/company was important to them.
  • What are your main takeaways from the shadow? How will you use this information to help you with your job search strategy?

    • Main takeaways were:
      1. During an interview, the interviewer is most likely looking at the interviewees ability to problem solve
      2. Make sure to read the entire error message instead of doing what you think would solve it, let the error messages guide you.
      3. Be willing to learn, have an open(growth) mindset.

Interview Prep:

  • Pick a successful project and write about it with the STAR method (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?):

    • Situation/Scenario of project: The project name was Viewing Party. This was our first real dive into consuming an API.

    • Task/target of the project: The task of the project was to successfully consume an API and display information for the User to view/interact with.

    • Action steps taken: Utilize the documentation that was on the API website on how to use it, test our connection to the API and the information by using Postman

    • Result: Successfully consumned an API and made the data usable for the user.

  • Write about a time you failed and what you learned from that experience:

    • There have been plenty of occassions that I have failed in during my time at Turing. Out of these failures, I have learned that it is ok to ask for help from others. It is better to reach out early(after doing some research/troubleshooting yourself) than to spend hours on end on trying to make something work.
  • Write about how you’ve approached working with a team using a specific example:

    • My most recent example of working with a team was during Turing Mod 2. We were working on Monster Shop (a make believe online marketplace). During my time working with this group of 5 total individuals, we would do a stand up meeting where we would discuss what topics/stories we would be tackling next and what was accomplished the night before. We would then split off into two different groups so that we were able to tackle different stories. Overall this project went well.
  • 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 doc, pick out at least 3 resources you will use to prepare for interviews as well as 3 behavioral questions you could practice:

    1. Ian's guide to technical interviews
    2. Leet Code
    3. Top 50 Programming interview questions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment