Recruiter Screening

• Share more about the company
• Share more about the position
• Hear more from the candidate interest
• Take the value they can bring to the company
• Share salary banding and candidate salary expectations (avoid)

Signals to look for

• Interest in the position
• Years of experience
• Kind of experience of the candidate (Projects, companies…)
• High level technical skills

Coding

Hackerrank, LeetCode, CodeSignal, eSkill. Algo Monster. Book cracking the code.

Values and Behaviours

Key Areas

• Collaboration
• Values, Behaviours, Culture Add
  • Handle disagreements and different opinions

Signals to look for

Explain to me the biggest challenge you have had in the past six months.

• Drive Impact
  • How you measure it?
• Communication
  • Explain to me the biggest challenge you have had in the past six months
• Collaboration
  • Prioritization
  • Examples of close collaboration with ICs, Product, Design, and Customer support
• Empower Customers
  • What it brings to the users?
• Mentorship / mentee-ship
  • Tell me how they has act and impacted as a mentor
• Diversity
  • Initiatives or open source?

Common Questions

• Why you want to work on this company?
• What do you expect from the next role?
• Tell me when you had a conflict with a colleague
• What was the most difficult bug you have found in the past 6 months?
• What’s the most constructive feedback you have received?
• How do you deal with failed deadline?

Coding Maintainability

Explain what we expect. 1/4 adding the feature. 3/4 refactoring the code.

Key Aspects

• Technical Complexity
• Ability to write clean code
• Ease of adding functionalities without generating bugs
• Programming principles and best practices
• P2. Plan before code
• P2. Plan testing
• P2. Bonus point. Do tests

Expense Report Example

View code example

System Design

The objective of system design interviews is to evaluate a candidate’s skill at designing real-world software systems involving multiple components. We want to understand the candidate’s knowledge on the big picture, given a fairly ambiguous design problem, how do they gather missing requirements, propose solutions and ask questions to get more clarity, so they reach a good solution.

Key Evaluation Areas

• System Design
• Ambiguity
• Continuously Learn
• Knowledge/Judgment
• Cultivate Authenticity (Collaboration)

View System Design Board