This document provides an overview of preparing for and succeeding in a technical interview process. It discusses finding job openings, the typical interview stages including phone screens and in-person interviews, common technical interview questions, and tips for each part of the process. The key advice is to practice coding problems daily, focus on breaking problems down step-by-step, ask clarifying questions, and follow up after interviews by thanking interviewers.
AI & ML Product Management by Google Product LeadProduct School
Main Takeaways:
-Research breakthroughs can open up product opportunities.
-Partner readiness and values alignment can make or break your product.
-Community engagement can accelerate adoption.
What Are the Road Mapping Essentials by former Capital One PMProduct School
Product road mapping is an art, one that requires a strong pulse on the state of the business, your customers and stakeholders. Road maps are meant to provide a clear path towards reaching the business objectives giving transparency and predictability to anyone involved on the team. But how often have you heard “Hey, we are agile, we don’t need a roadmap”; or the opposite “Hey, this feature was on the roadmap, but why haven’t you delivered?”.
In this session, Angela Govila, former Product Manager at Capital One, talked about how to handle both of these situations and everything in between, by diving deep into the basics of how to conduct road mapping sessions.
Webinar: From Engineer to Product Manager by fmr Uber PMProduct School
Main takeaways:
- Insight and Experiences
- On deciding and navigating the transition
- Differences in mindset, skillset, and the nature of work
- How (and when) engineering thinking can be beneficial to Product Managers
Tips for remote product management by Amazon Sr PMProduct School
Main takeaways:
-Product Management is about communicating. Remote Product Management is about communicating more.
-Send notes for each interaction. Both formal and informal. Include owner and estimated time of delivery.
-Set up recurring meetings. With key stakeholders. Keep the meeting even if the agenda is light.
-Offer full transparency. Share supporting notes even if not asked. Make the roadmap public.
-Get to know your teammates. Learn their preferred schedule. Pay attention to their environment and start conversations.
How Product Managers Can Lead a Team by fmr Pivotal Sr PMProduct School
Main Takeaways:
- Build psychological safety within a team: learn how to create a shared understanding within a team you lead so that team members are comfortable raising important issues or concerns
- How to facilitate constructive conflict so that obstacles and risks are identified early and often, enabling you to create opportunities to clear or address those obstacles
- When and how to practice communication techniques for the regularly scheduled meetings that are critical to team progress
How to Succeed as a Non-Technical PM by Spotify's Product OwnerProduct School
Many companies require Product Managers to have a technical background - whether it be a formal Computer Science degree or experience with writing code.
"Over the years I've been self-conscious about my lack of technical background, yet I’ve learned that technical skills aren’t everything when it comes to Product Management." Jori Bell broke down the myth of needing technical skills to be a successful Product Manager.
She talked about how you need to understand the types of skills that will make you a successful Product Manager. She also discussed the importance of bringing non-technical value to a team and how to do it, and how you can build trust with a technical team.
Managing Product Managers by Spotify Sr Product ManagerProduct School
Main Takeaways:
-When becoming a manager you need to change your mindset
-Creating a culture of bi-directional feedback
-Your team's success is your success
AI & ML Product Management by Google Product LeadProduct School
Main Takeaways:
-Research breakthroughs can open up product opportunities.
-Partner readiness and values alignment can make or break your product.
-Community engagement can accelerate adoption.
What Are the Road Mapping Essentials by former Capital One PMProduct School
Product road mapping is an art, one that requires a strong pulse on the state of the business, your customers and stakeholders. Road maps are meant to provide a clear path towards reaching the business objectives giving transparency and predictability to anyone involved on the team. But how often have you heard “Hey, we are agile, we don’t need a roadmap”; or the opposite “Hey, this feature was on the roadmap, but why haven’t you delivered?”.
In this session, Angela Govila, former Product Manager at Capital One, talked about how to handle both of these situations and everything in between, by diving deep into the basics of how to conduct road mapping sessions.
Webinar: From Engineer to Product Manager by fmr Uber PMProduct School
Main takeaways:
- Insight and Experiences
- On deciding and navigating the transition
- Differences in mindset, skillset, and the nature of work
- How (and when) engineering thinking can be beneficial to Product Managers
Tips for remote product management by Amazon Sr PMProduct School
Main takeaways:
-Product Management is about communicating. Remote Product Management is about communicating more.
-Send notes for each interaction. Both formal and informal. Include owner and estimated time of delivery.
-Set up recurring meetings. With key stakeholders. Keep the meeting even if the agenda is light.
-Offer full transparency. Share supporting notes even if not asked. Make the roadmap public.
-Get to know your teammates. Learn their preferred schedule. Pay attention to their environment and start conversations.
How Product Managers Can Lead a Team by fmr Pivotal Sr PMProduct School
Main Takeaways:
- Build psychological safety within a team: learn how to create a shared understanding within a team you lead so that team members are comfortable raising important issues or concerns
- How to facilitate constructive conflict so that obstacles and risks are identified early and often, enabling you to create opportunities to clear or address those obstacles
- When and how to practice communication techniques for the regularly scheduled meetings that are critical to team progress
How to Succeed as a Non-Technical PM by Spotify's Product OwnerProduct School
Many companies require Product Managers to have a technical background - whether it be a formal Computer Science degree or experience with writing code.
"Over the years I've been self-conscious about my lack of technical background, yet I’ve learned that technical skills aren’t everything when it comes to Product Management." Jori Bell broke down the myth of needing technical skills to be a successful Product Manager.
She talked about how you need to understand the types of skills that will make you a successful Product Manager. She also discussed the importance of bringing non-technical value to a team and how to do it, and how you can build trust with a technical team.
Managing Product Managers by Spotify Sr Product ManagerProduct School
Main Takeaways:
-When becoming a manager you need to change your mindset
-Creating a culture of bi-directional feedback
-Your team's success is your success
Product Management in Startups vs Big Org by Amazon Product LeaderProduct School
Main Takeaways:
-Prioritization in big companies is more complex (and across engineering orgs in different geographies)
-Stakeholder management is more than 50% of the PM role in bigger companies compared to startups
-Speed of execution and levels of ownership in startups are higher
Side-Stepping Into Tech by BBC Product LeaderProduct School
Main Takeaways:
- What is a Product Manager
- Transferable skills if you don't have direct experience in Product
- My non-linear path into Product
- Steps I took to sidestep into Tech during my job search
Level Up Your Tech Skills to Build Better Products by Upwork PMProduct School
Main Takeaways:
- While it's definitely not necessary for a PM to have a CS degree or be a skilled programmer, it's important that PMs are good at systems thinking and have an understanding of how technology powers their product so that they can have high quality discussions with their technical partners - a good way to assess or test this is if you can diagram the high-level architecture of your product.
- As AI is leveraged more broadly and deeply in products, PMs have to reinforce their existing technical understanding and also incorporate a new element into their thinking - data.
- Ask your technical partners to help you learn, both in general and about your product's tech - you'll learn more quickly and also deepen your relationship with them.
Thinking Like a PM w/ former VP of Product at Lynda.comProduct School
Product Managers must balance four very different and sometimes conflicting mindsets when approaching ideation, creation, and delivery of high-value products. These are Exploration, Analysis, Critique and Evangelism. No matter what stage in the product lifecycle, simultaneously and deliberately viewing your product through these perspectives will help avoid common pitfalls and help deliver a superior solution.
Former VP of Product at Lynda.com, Ken Sandy, talked about the relative advantages of each of the four mindsets: how Exploration drives innovation, Analysis drives understanding, Critique identifies risks, and Evangelism provides a path to delivery.
He also talked about how to execution in context: your role is to build the right product, not to build the product right, and how to know what questions to ask yourself at each stage of the lifecycle and strategies to bring stakeholders along with you.
The Predictable & Unpredictable in PM Journey by Amazon Sr PMProduct School
Main takeaways:
-Product journey is filled with predictable and unpredictable scenarios.
-Breakdown the problem, identify your resources and leverage those to navigate through chaos.
-Acknowledge your success. Learn from failures. Own the outcome.
How to Get a PM Role w/ Non-Tech Background by Salesforce PMProduct School
In this presentation, Tanvi Dali discusses how to position yourself so that your dots will connect to land you a PM opportunity in the future. For those who are already in PM, she also discusses a few tips on how to make a good first impression (within the first 90-days as a new PM) and what a typical day or week looks like as a PM at Salesforce.
Finding Your Superpower in Product Management by Disney Sr PMProduct School
Main takeaways:
-Avoid the tyranny of a blank page (or a blinking cursor) - start with something (which is better than nothing) then edit, open for comments and learn
-Answering "What to build" is good but generating "Why we are doing this" is awesome
-Context is a product manager's superpower
Scrum Transformation - 1 year after - our story - Agile by Example 2017pproductivity
15 minutes, three presenters, one story - 1 year of Agile transformation within Fru.pl told by Paweł Gawliczek (CTO) and Marta Borkowska-Bierć (People aspects) and Piotr Nabielec (Produktywni.pl, process aspects).
This presentation took place during Agile by Example 2017 conference in Warsaw.
Venture boss a program to coach train 1 million entrepreneurs by 2026Bryan Cassady
At venture-boss our mission is to help train and coach 1 million young entrepreneurs by 2026.
But for billions of people around the world, Entrepreneurship is just a dream. It is something other people do.
Venture-boss will change this by offering a simple, but powerful, 5-day learning by doing program that can be run in any language, for almost any type of business, online or in-person by thousands of trainers worldwide.
Our business model is inspired by Innovation engineering taught at 26 US universities. And the Founder Institute run in 182 cities. Our program and their programs are based on independent local programs that are easy to scale AND collaboration for continual improvement.
We’ve already taught students as young as 17 from 22 countries. Based on these successes, we have started new programs in Nigeria, Angola, India and Malaysia.
Top 5 Learnings as a Google Product ManagerProduct School
Main takeaways:
-Not-so-obvious insights about the Product Manager role in general
-Approaches to deal with some organizational and prioritization challenges
-Ideas to plan your PM career and much more!
30-Day Plan for New Product Managers by Sr PM at NewselaProduct School
Main takeaways:
- When to start talking to customers and what questions to be asking
- How to approach conversations with stakeholders
- Strategies for learning existing processes and informing product discovery
Karoliina Luoto, Codento. J. Boye Web and intranet conference 2013 presentation on how problems in agility are often fixed by going back to basics and taking the humble lesson.
Choose the Right Problems to Solve with ML by Spotify PMProduct School
Main takeaways:
-What problems are best solved with ML and what problems are NOT
-What you need to understand and how technical you need to get as a PM of an ML product
Working as a PM in a Startup Environment w/ Banjo's PMProduct School
The product manager at Banjo talked about the different skills you need to be successful and how your journey doesn't need to be the same as anyone else.
When starting on your product journey its important to know the differences between startups and larger companies. Matt spoke about his transition into product management at a startup from Google.
Семинар "Стартиране на ИТ кариера" - http://academy.telerik.com/seminars/it-career
Подготовка и явяване на интервю за работа в ИТ индустрията. Как да се подготвим? Какви въпроси да очакваме? Как да се държим по време на интервюто?
Лектор: Николай Костов, софтуерна академия на Телерик.
Product Management in Startups vs Big Org by Amazon Product LeaderProduct School
Main Takeaways:
-Prioritization in big companies is more complex (and across engineering orgs in different geographies)
-Stakeholder management is more than 50% of the PM role in bigger companies compared to startups
-Speed of execution and levels of ownership in startups are higher
Side-Stepping Into Tech by BBC Product LeaderProduct School
Main Takeaways:
- What is a Product Manager
- Transferable skills if you don't have direct experience in Product
- My non-linear path into Product
- Steps I took to sidestep into Tech during my job search
Level Up Your Tech Skills to Build Better Products by Upwork PMProduct School
Main Takeaways:
- While it's definitely not necessary for a PM to have a CS degree or be a skilled programmer, it's important that PMs are good at systems thinking and have an understanding of how technology powers their product so that they can have high quality discussions with their technical partners - a good way to assess or test this is if you can diagram the high-level architecture of your product.
- As AI is leveraged more broadly and deeply in products, PMs have to reinforce their existing technical understanding and also incorporate a new element into their thinking - data.
- Ask your technical partners to help you learn, both in general and about your product's tech - you'll learn more quickly and also deepen your relationship with them.
Thinking Like a PM w/ former VP of Product at Lynda.comProduct School
Product Managers must balance four very different and sometimes conflicting mindsets when approaching ideation, creation, and delivery of high-value products. These are Exploration, Analysis, Critique and Evangelism. No matter what stage in the product lifecycle, simultaneously and deliberately viewing your product through these perspectives will help avoid common pitfalls and help deliver a superior solution.
Former VP of Product at Lynda.com, Ken Sandy, talked about the relative advantages of each of the four mindsets: how Exploration drives innovation, Analysis drives understanding, Critique identifies risks, and Evangelism provides a path to delivery.
He also talked about how to execution in context: your role is to build the right product, not to build the product right, and how to know what questions to ask yourself at each stage of the lifecycle and strategies to bring stakeholders along with you.
The Predictable & Unpredictable in PM Journey by Amazon Sr PMProduct School
Main takeaways:
-Product journey is filled with predictable and unpredictable scenarios.
-Breakdown the problem, identify your resources and leverage those to navigate through chaos.
-Acknowledge your success. Learn from failures. Own the outcome.
How to Get a PM Role w/ Non-Tech Background by Salesforce PMProduct School
In this presentation, Tanvi Dali discusses how to position yourself so that your dots will connect to land you a PM opportunity in the future. For those who are already in PM, she also discusses a few tips on how to make a good first impression (within the first 90-days as a new PM) and what a typical day or week looks like as a PM at Salesforce.
Finding Your Superpower in Product Management by Disney Sr PMProduct School
Main takeaways:
-Avoid the tyranny of a blank page (or a blinking cursor) - start with something (which is better than nothing) then edit, open for comments and learn
-Answering "What to build" is good but generating "Why we are doing this" is awesome
-Context is a product manager's superpower
Scrum Transformation - 1 year after - our story - Agile by Example 2017pproductivity
15 minutes, three presenters, one story - 1 year of Agile transformation within Fru.pl told by Paweł Gawliczek (CTO) and Marta Borkowska-Bierć (People aspects) and Piotr Nabielec (Produktywni.pl, process aspects).
This presentation took place during Agile by Example 2017 conference in Warsaw.
Venture boss a program to coach train 1 million entrepreneurs by 2026Bryan Cassady
At venture-boss our mission is to help train and coach 1 million young entrepreneurs by 2026.
But for billions of people around the world, Entrepreneurship is just a dream. It is something other people do.
Venture-boss will change this by offering a simple, but powerful, 5-day learning by doing program that can be run in any language, for almost any type of business, online or in-person by thousands of trainers worldwide.
Our business model is inspired by Innovation engineering taught at 26 US universities. And the Founder Institute run in 182 cities. Our program and their programs are based on independent local programs that are easy to scale AND collaboration for continual improvement.
We’ve already taught students as young as 17 from 22 countries. Based on these successes, we have started new programs in Nigeria, Angola, India and Malaysia.
Top 5 Learnings as a Google Product ManagerProduct School
Main takeaways:
-Not-so-obvious insights about the Product Manager role in general
-Approaches to deal with some organizational and prioritization challenges
-Ideas to plan your PM career and much more!
30-Day Plan for New Product Managers by Sr PM at NewselaProduct School
Main takeaways:
- When to start talking to customers and what questions to be asking
- How to approach conversations with stakeholders
- Strategies for learning existing processes and informing product discovery
Karoliina Luoto, Codento. J. Boye Web and intranet conference 2013 presentation on how problems in agility are often fixed by going back to basics and taking the humble lesson.
Choose the Right Problems to Solve with ML by Spotify PMProduct School
Main takeaways:
-What problems are best solved with ML and what problems are NOT
-What you need to understand and how technical you need to get as a PM of an ML product
Working as a PM in a Startup Environment w/ Banjo's PMProduct School
The product manager at Banjo talked about the different skills you need to be successful and how your journey doesn't need to be the same as anyone else.
When starting on your product journey its important to know the differences between startups and larger companies. Matt spoke about his transition into product management at a startup from Google.
Семинар "Стартиране на ИТ кариера" - http://academy.telerik.com/seminars/it-career
Подготовка и явяване на интервю за работа в ИТ индустрията. Как да се подготвим? Какви въпроси да очакваме? Как да се държим по време на интервюто?
Лектор: Николай Костов, софтуерна академия на Телерик.
Learn why you should do internships, how to choose, and of course, how to get them!
This was originally presented on 2nd September 2016 during Friday Hacks #116 hosted by NUS Hackers.
Watch a video of the presentation here: https://engineers.sg/video/friday-hacks-116-internships-and-why-you-should-do-them-nus-hackers--1105
In a whiteboard interview, your goal should be to convince the manager that you will be a positive influence on the team and contribute to the team's success. This guide will help you set the right mindset, ask the right questions, and showcase your strengths.
CONNECTWorking 2019-09 - Jumpstart to get a jobBC Talents
It's Back-to-School! It is time to build the foundations for your job search and career. In order to get your dream job, your resume must be clear, your cover letter convincing, and you must be able to present yourself in a concise and striking way.
Every month, BC Talents finds the best speakers to help you achieve the career of your dreams and thrive in your professional goals. This month we will host Tyler Yang, Talent Growth Specialist chez Shopify, who will share his secrets to build a strong resume, cover letter and Elevator Pitch, as well as what HR are looking to see.
On September 3rd, come meet Tyler and the BC Talents team to talk about you and how you should present yourself in Canada to be remembered. You are your own brand, and it is essential to know how to sell it.
How to land your first job in tech without an engineering degreeStuti Verma
Although, formal education helps in creating opportunities for first job but it is not necessary to have a degree in computer science, math or other STEM fields to get a job at a tech company. In today’s fast-paced technology industry, most of the information of the world is never more than a few clicks away and where things change so fast, education must in fact be a life-long process and not the learn-once-use-forever one-off process. Therefore, relevance of a degree is easily compensated with relevant skills combined with business use-cases and projects.
In this talk, we will discuss about the roles and opportunities in the tech industry and why skill-driven approach changes mindset of the recruiter. It will include how one can break barriers of academic limitations, tap into opportunities through soft skills and networking, choose to slip into the job they want rather than slip away. Concluding it with useful resources and hacks to network better to land into opportunities life-long.
My goal with this talk was to provide developers and tech folks with an understanding of requirements gathering. Key concepts and resources that they can use to make their own coding practice better. Part of being a professional coder
Facing interviews is both science and an art. Typically for freshers, it becomes very challenging to face interviews. Here is a presentation that gives you practical tips and inputs to crack interviews.
NIDM (National Institute Of Digital Marketing) Bangalore Is One Of The Leading & best Digital Marketing Institute In Bangalore, India And We Have Brand Value For The Quality Of Education Which We Provide.
www.nidmindia.com
Exploring Career Paths in Cybersecurity for Technical CommunicatorsBen Woelk, CISSP, CPTC
Brief overview of career options in cybersecurity for technical communicators. Includes discussion of my career path, certification options, NICE and NIST resources.
New Explore Careers and College Majors 2024.pdfDr. Mary Askew
Explore Careers and College Majors is a new online, interactive, self-guided career, major and college planning system.
The career system works on all devices!
For more Information, go to https://bit.ly/3SW5w8W
4. 01 Allabouttheinterviews
FIND AN OPENING
APPLY FOR POSITION
PHONE SCREEN /
IN-PERSON
INTERVIEW
FOLLOW-UP
REVIEW / ACCEPT
OFFER
Find public postings
or network to find
open positions
Positions should
match your current
skill set
The hard part –
showing what you
know
Don’t forget to thank
the team or ask for
feedback
You win! Time to put
that negotiation hat
on
5. 01 Allabouttheinterviews
1. The average job opening attracts 250 resumes
2. Only 2% of applicants will be called for an interview for the average job opening
3. 42 days is the overall average time it takes to fill a given position
4. The interview process takes an average of 23 days
5. It takes five to six weeks on average to get a job offer
Getting totheinterviewishalfofthebattle!
WhatcanIexpect?
Source: https://www.ebiinc.com/resources/blog/hiring-statistics
6. 01 Allabouttheinterviews
• Understand that anyone can fall prey to the “Interview Anti-Loop”, i.e. for every qualified candidate, there is
at least one set of interviewers who would not hire that person
• Interviewers may not be trained in good interviewing skills and processes
• Many interview exercises do not have a set rubric to weigh out performance, leading to interviewer
bias
Notallinterviewsandinterviewersarecreatedequally
Source: http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html
7. 01 Allabouttheinterviews
• Technical screening
• In-person interview
• Coding exercise – 60 mins
• Code review exercise - 45 mins
• Break – 15mins
• Debugging exercise – 30 mins
• Technical Discussion – 30 mins
• Chat with Director of Technology – 30 mins
• NO take-home test
We have a rubric – a set of instructions and a set of things to look for and how to weigh out each
candidate in the same way.
We train our interviewers – each engineer that proctors an exercise has taken the exercise
themselves.
Theprojekt202’stechnicalinterview
Source: http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html
9. 02 Beforetheinterview
Most technical phone interviews will focus on questions that can be answered on the fly – you won’t
have to spell out a function that reverses an array.
You may be asked:
• About your engineering career
• Ex. Tell me about your current role and your responsibilities as part of your team
• Questions specific to the role, technology, and tools
• Ex. Describe the Android Activity Lifecycle
• Personal drive / self-learning questions
• Ex. How do you stay up-to-date on the latest iOS news?
• To explain best-practices for general engineering activities
• Ex. What are the Agile ceremonies that matter the most to you?
Preparingforaphoneinterview
10. 02 Beforetheinterview
Some common reasons why someone did not seem like a good match after a phone interview:
• “Candidate had a decent breadth of experience but not a lot of depth.”
• Don’t just answer questions, dive into as much detail as you know
• “Candidate wasn’t passionate about his work”
• Focus on your extra-curricular activities that showcase your passion for engineering
• “Candidate could not elaborate on software engineering basics like the SDLC”
• Polish up on best practices, even if you have never used them in a work setting, read up on
some of these things so you can speak about them
• “Candidate applied for a senior position but did not have matching technical skills”
• Make sure to introspect and apply to positions that fit your skillset or a good phone screener
will rule you out quickly
Preparingforaphoneinterview(cont.)
11. 02 Beforetheinterview
Before a technical call make sure you:
• Find a quiet place to talk without being disturbed
• Use headphones so you can have your hands free
• Have paper and pen ready to write down your thoughts and questions
• Read up on the company, their work, and check out the interviewer on LinkedIn
• Write down a list of questions you may have for the interviewer
Preparingforaphoneinterview(cont.)
12. 02 Beforetheinterview
Most in-person or online interviews will center around trying to get a rough understanding of your:
• Knowledge around Computer Science basics
• Algorithms
• Basic data structures like arrays and linked lists
• Binary Search Trees
• Big O Notation
• Software development best practices in teams
• How to use version control systems
• Performing code reviews
• Advanced technical concepts
• Scalable system architecture designs
• Describing pieces of the SDLC
• Analytical thought process
• Tell me about a difficult problem that you were able to resolve after trial and error
• Describe a complex problem in easy to understand smaller chunks
• Soft Skills
• What has been your experience working in multi-disciplinary teams
• Explain a technical concept to non-technical people
Preparingforanin-personinterview
13. 02 Beforetheinterview
What you should practice:
• Coding algorithmic and data-structure exercises
• Reviewing code that someone else wrote
• Whiteboarding or discussing open questions
• Computer science and engineering best practices
Preparingforanin-personinterview(cont.)
14. 02 Beforetheinterview
How do you prepare?
• Study the fundamentals
• Solve coding questions every day
• Practice white-boarding
• Participate in mock interviews
Howmuchyoupractice is reallyuptoyou –butdailypracticeisthenextbest thingtoafull-timejob
Preparingforanin-personinterview(cont.)
15. 02 Beforetheinterview
What pitfalls you should avoid when trying to prepare:
• Know what you know
• Cramming the day before the interview is not the way to go
• Choose sleep over studying – being alert and coherent is more important than that last sample
problem!
Preparingforanin-personinterview(cont.)
17. 03 Duringtheinterview
On the technical side of things:
• Focus on the breaking down every problem into smaller pieces
• Lay everything out in pseudo-code if you can before you start coding
• Treat everything like it should be production ready
• Run your code
• Include tests if you can
• Watch out for edge cases
• Ask clarifying questions when you need to – not getting caught up in rabbit holes is essential
Practiceeachof thesesteps inyourdailyexercisestoo!
WhatshouldIdowithmyhands?
Source: https://medium.com/@nickciubotariu/ace-the-coding-interview-every-time-d169ce1fd3fc
18. 03 Duringtheinterview
The most important non-technical things to remember during an interview are:
• Be engaged – don’t give 1 word answers, interviewers are looking for as much information as they
can usually in a short amount of time
• Know your audience – most likely, the person interviewing you will be another very technical
person, use technical terms and make sure you use them correctly
• Speak your mind – interviews are not about coming up with the right answer out of the blue, the
reason why they are proctored is to have someone follow along with your train of thought, so
make sure to walk the interviewer through your thought process
• Dress for the part – make sure you know if the office has a casual environment before you head in
with a suit and tie
Nooneishiredpurelybasedontechnicalskill,trainingyoursoft-skills arejustas important
WhatshouldIdowithmyhands?(cont.)
20. 04 Aftertheinterview
Make sure that you don’t forget the little things
• Send a follow up email thanking each of the individual interviewers
• Make sure you ask about next steps and when you should hear back
• Ask any questions that you may have regarding:
• the culture
• the company’s focus on personal / technical growth
• the engineering process
• work / life balance
• benefits
Howdoyousetyourselfapart?