
Branch Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Branch.
Integration Engineer
I applied online. The whole thing took about a month. It was a really thorough process, and the HR folks were super engaging. They made sure I was totally prepped for each part, giving me details like how long each round would be, who would be interviewing me (with their LinkedIn profiles!), what they were looking for, and even some extra open-source stuff to check out. What was awesome about Branch was how on time everything was; interviews started and finished exactly when they said they would, which was pretty cool. Before each round, the interviewers would explain what they were hoping to find, and I'd get feedback within 24 hours. HR also kept in touch during breaks between rounds to make sure I was ready for the next step. The main thing for the interview is to really understand Branch's basic technology well.
- Can you explain what Deep linking is and what attribution means?
- Could you explain the concept of attribution?
Integration Engineer
I interviewed for the Associate Integration Engineer role at Branch. The process had a few parts. First, a Technical Round with the Manager, focusing on Android basics. Then, an Assignment Round where I had to integrate the Branch SDK into an app and answer questions about it. After that, a Team Fit Round, highlighting Branch's collaborative culture. Lastly, an HR Round, which was both professional and personal, showing their interest in candidates. The recruiting team was really great, super helpful, answered all my questions, and kept things professional.
- Could you detail the steps involved in integrating the Branch SDK?
- What functionalities does the Branch SDK offer?
- In what ways does the Branch SDK support the operations of an application?
Integration Engineer
There were about 7-8 rounds of interviews that took place over 2 months. These included separate rounds for values, about the company, about the company's product, HR, projects, and management. I applied for Associate Integration Engineer, but it ended up being a Support Engineering role. When I asked about this, they explained that they call Support Engineers 'Integration Engineers' at their firm, which felt like a deception. They spend about 4-5 rounds just asking about the company and its product, which seems completely pointless.
- Could you explain what Branch is?
- What is attribution?
- What makes you want to join Branch?
Branch Engineer Interview Questions
Quoted word for word from Branch interview reports.
“Write a function that generates a random integer, taking an upper bound as a parameter.”
Read reports →“If you know the location of a node in one tree, how would you find the corresponding location in another tree?”
Read reports →“What is attribution?”
Read reports →“Can you define Deeplinking?”
Read reports →“What's the pricing for the product?”
Read report →“How does deep linking work?”
Read report →“What functionalities does the Branch SDK offer?”
Read report →“Can you integrate the Branch SDK by following the integration steps provided here?”
Read report →“Can you explain what Deep linking is and what attribution means?”
Read report →Formats, difficulty and experience
Across all 11 Branch interview reports.