/9918578/Banner

/9918578/Banner_2

/9918578/Mid

section

articleId

product

orgType

parrefer

accountID

Consulting

Banking

Accounting

Fintech

Internships

Rankings

Internship Rankings

Intern Resource Center

Explore Internships

Vault Law Home

Practice Area Resource Centers

Regional Resource Centers

Summer Program Resource Center

Vault Law Culture & Inclusion Survey

Vault Law

Guides

Events

Financial Services

Technology

Grad School

Work Relationships

Productivity

Diversity, Equity & Inclusion

Social Impact

Remote Work

Negotiating

Changing Jobs

Workplace Issues

Blog

Resume Samples

Cover Letter Samples

Interview Tips & Questions

A Day in the Life

International

Career Readiness

Explore Professions

Research Industries

Search Companies

Career Advice

Employers

Schools

&lt;p&gt;Kevin Dolan, the chief technology officer of Metric Collective, knows a thing or two about tech interviews. Dolan has been on both sides of the interview table dozens of times, and so he knows about both the common pitfalls and best answers when it comes to interviewing for top tech positions.&lt;/p&gt;&lt;p&gt;In the video below, Dolan discusses how to nail the three types of tech interviews, which he breaks down as follows:&lt;/p&gt;&lt;p&gt;&lt;strong&gt;1. Quizzes&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;These are questions about specific tech concepts and general computer science concepts. They&#39;re meant to test your knowledge of certain concepts. But don&#39;t worry, says Dolan, if you haven&#39;t heard of a certain concept or word. If that&#39;s the case, just focus on adjacent concepts that you have heard of, and it&#39;s even okay to state that you have never heard of the concept you&#39;re being asked about. The important part of answering this type of question (or any question) is to avoid dead air, according to Dolan. That is, you don&#39;t want silence in an interview. Instead, you want to keep the conversation moving along, going forward. And, says Dolan, remember one very important thing: Inteviewers want you to succeed. They don&#39;t want to trip you up. Best case scenario for them is you&#39;re the right person for the job and then they can get back to coding.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;2. Experience Questions&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;These questions focus on things that you&#39;ve done, projects you&#39;ve worked on. They could cover tech projects or non-tech projects. Dolan says he&#39;s usually looking for the overall narrative of a certain project to get an idea of how someone deals with hurdles and solves problems that arise. So, ideally, you want to talk about a project that didn&#39;t go 100 percent as planned (as Dolan and all experienced tech workers know, no project goes as planned, so your interviewer will not believe you anyway). The point is don&#39;t be afraid of talking through the problems and difficulties and miscues of projects. You&#39;ll be judged not on the success of the project you talk about but on the problems you faced and solved and how you went about solving those problems, especially under time constraints. Dolan adds that if you don&#39;t have much project experience on the job, then hackathons are certainly fine to talk about here.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;3. Hypotheticals&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;These are the whiteboard questions where you&#39;re given a hypothetical project and asked to walk through how you would approach it. When Dolan asks these questions, he lets the interviewee either talk through the answer, use a whiteboard, or use paper. Whatever they&#39;re most comfortable with works for Dolan, who notes that it&#39;s not about correctness here but process. That is, the most important thing to keep in mind when answering these questions is showing your thought process and your problem solving ability. It&#39;s even fine, when talking through the problem, to get to a dead end and then identify that end and say, Oh, this isn&#39;t going to work because of X, Y, and Z. And then take another route to solving the problem. A specific tip here from Dolan that will set you in the right direction when answering these types of questions is to first reiterate the problem back to the interviewer. This, says Dolan, buys you some time to think about the problem. It also gives you a minute to compose yourself before you jump into how to solve it.&lt;/p&gt;&lt;p&gt;Check out more about how to ace a tech interview, according to Dolan, here:&lt;/p&gt;&lt;p&gt;&lt;iframe width=&quot;560&quot; height=&quot;315&quot; src=&quot;https://www.youtube.com/embed/GBp0yIdJtUk&quot; frameborder=&quot;0&quot; allowfullscreen=&quot;&quot;&gt;&lt;/iframe&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;Follow me on&#160;&lt;a rel=&quot;noopener noreferrer&quot; href=&quot;https://twitter.com/vaultfinance&quot; target=&quot;_blank&quot;&gt;Twitter&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;Follow us on&#160;&lt;a rel=&quot;noopener noreferrer&quot; href=&quot;https://www.instagram.com/vaultcareers/&quot; target=&quot;_blank&quot;&gt;Instagram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

Derek Loosvelt

Article

How an Ex-Google Employee Answers "Walk Me Through Your Resume"

What Does Microsoft CEO Satya Nadella Look For in New Hires?

3 Resume Tips from Tech Firm Recruiters

The Library