---
# System prepended metadata

title: Vendor Interview

---

# Vendor Interview

#### AGENDA
1) Leads Introduction
2) Engineering Manager Questions [~10 mins]
3) Principal Engineer Questions [~20 mins]
4) Code Walkthrough
    - Android [~45 mins]
    - iOS [~45 mins]

### Step 1: Introduction

### Step 2: Engineering manager (10 mins tops)

- Initial intro
- EM Meta Questions 
    - Comparable mobile projects have you worked on as a lead of a team of engineers?
        - Large-scale? retail/ecomm?
    - How do you communicate & ENFORCE code standards/guidelines to your team/engineers?
    - How do you ensure code quality from the rest of team/engineers? 
        - How do you find time writing unit tests while keep up with sprint? 
    - Approach to quickly gain familiarity for an unfamiliar but established codebase?
    - Example of your passion for mobile?
    - Give an example of a problem in mobile realm that you have solved?
        - Follow-up: if not initially mentioning team / leadership, ask about this
    - [If team is already involved] How was your engineering team chosen?
        - Did you / will you have input to the engineers to fill out your team?
    

### Step 3: Principal Engineers (2o mins tops)
>Participation from both platform is desirable. Let make that known before starting this series.
- [ ] SOLID^principal^ (Single reposibility, Open Close, Liskov subsitution, Interface segregation, Dependency inversion )
- [ ] DRY^principal^, ETC^principal^ (Easy to change)
- [ ] What kind modular project you have worked with if not then how would you approach modularizing a large project. 
- [ ] If modular code how would you handle ==nested dependencies==?
- [ ] How would you avoid avoid ==circular dependencies==?


### Step 4: Code review 
> To avoid confusion who goes first, Lets go alphbatically order. Hence ==Android first==. 
> Steve will be the time-keeper.
- Code Walkthrough (10 mins tops)
    - Alloted time is about 40 mins. Grace period is for 5 mins for Wrapup. 45 mins is hard stop. 
- All Questions are going to be based on the code. There is low scope of other questions. However relvant question can be asked. Q&A (35 mins tops) 