Prepare for Job Shadow: AEIOU
Activities: what questions do you have about the activities that a software developer does on a daily basis?
- What is a typically day's schedule like?
- How often do you have stand ups, team meetings, etc?
- How long is a typical sprint (do you work in sprints)?
- How much of a typical day is spent actively working with code?
- What does workflow and project management look like on a typical day?
- What do you like most about working for SOVRN?
Environment: what questions do you have about the overall environment and culture of this workplace?
- Describe the work/life balance?
- Are you close with coworkers/teammates?
- Dresscode, pto, benefits?
Interactions: what questions do you have about the team at this company? What do you hope to see in your interactions during the shadow?
- How often do you have stand ups, team meetings, etc?
- How long is a typical sprint (do you work in sprints)?
- How often do you receive feedback from a manager?
- What is coaching/training like?
Objects: what questions do you have about the code or the product?
- Which technologies/languages do you primarily work with?
- How do you collect and sell user data (behavior, emails) while still protecting security and privacy?
- What percentage of payment does SOVRN receive through Instant Pay and how is that determined?
Users: what questions do you have about how the company interacts with their users?
- How often (if at all) do you interact with customers and publishers?
- What does growth look like for SOVRN in terms of expanding the user base?
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?
They seemed to enjoy having freedom to make decisions and advocate for what they thought was good. There was a lot of autonomy for the devs, and they seemed to enjoy that.
Environment: what did you notice about how they talked about the culture and environment of this company?
This was kind of hard because it is all remote, but as mentioned above they seemed to feel valued (like they could speak up and had input that mattered). The manager mentioned that being a good cultural fit was more important than technical skill when it came to a new dev right out of bootcamp.
Interactions: what did you notice about your interactions with this person/people?
The gentleman I shadowed was friendly and eager to be part of the job shadow experience. He patiently walked me though a typical part of his work (noticing a problem, making a ticket, and resolving the ticket).
Objects: what did you learn about their approach to code and/or product development?
I learned that asking questions is not only ok, it's essential. He told me that asking questions and being honest about what I do not know yet is extremely important for any new dev, or even an experienced dev who is new to a company.
Users: what did you learn about their approach to their users?
This was not something we really discussed, but it was reflected in the ticket that we worked on. The point was to improve the UX of the UI by making the numbers on a graph more intuitive and easier to understand.
What are your main takeaways from the shadow? How will you use this information to help you with your job search strategy?
- When hiring a new dev, companies really care about things like attitude, culture, problem solving, attitude, etc.
- Ask questions and be honest. Don't be embarrassed, just be honest.
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?):
Rancid Tomatillos
- This was the first project of Mod 3 at Turing. I worked with one partner.
- Rancid Tomatillos was designed to teach us React, Router, and React Testing. It also provided practice for async coding with fetching data from an API.
- We started this project by reviewing the guidelines of the MVP, writing a DTR agreement, psuedocoding the main components of the app, outlining a wireframe of the project, and starting a kanban project board on GitHub. From there we set a timeline of targets and worked to keep out timeline. We worked together while coding to make sure both partners fully learned all aspects of the technology. We occasionially touched base with other teams to share tips, ideas, and best practices. Most importantly, we maintained regular daily communication and honored our commitments in terms of progress and time.
- We met all project requirements and also accomplished the stretch goals that we chose for ourselves. The app was fully functional and contained several features beyond the MVP. Our instructor feedback was positive and reflected that we were proficient in all rubric areas.
Write about a time you failed and what you learned from that experience:
I briefly failed on an early Turing solo project. I allowed myself to become overcome by the scope and breath of the project spec. I tried to do too much at once. I learned that I need to break things down, start small, and have a modular approach. Take baby steps until the project is complete. It is also important sometimes to just "get started". Don't be paralyzed by the scope. Have an overview, break it down into small chunks, and get started. Make a plan, revisit the plan as you go, and get it done.
Write about how you've approached working with a team using a specific example:
Experience has shown me how important it is to clearly communicate expectations in advance, from day one. Norm setting is very important. It is also important to be respectful, honest, and direct. In a situation where my teammates were making decisions without me, I had to be direct (respectfully) that I felt disrespected and excluded. This was a great move because it cleared the air, gave them a chance to explain, and improved the working dynamic moving forward.
What other stories will you prepare to share?
Norm settign is essential because failure to do so leads to miscommunication and frustration. This was an issue in previous projects in tersm of app design and work schedule. When these were not clearly communicated in advance it ultimately created friction and frustration, as well as wasted time.
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?
I have noticed that lot of companies are using Typescript and React, which is great news because that is what I am using right now. I learned that this is true for both Nordstrom and Quizlet.