Branding Brand logo

Branding Brand Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 24 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
37.5% Positive experience

Which role are you interviewing for?

13 roles · 24 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Branding Brand.

Showing 4 of 24
Branding Brand logo
Branding Brand

Production Assistant

Operations · more than a year ago

Entry Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical

The hiring journey usually kicks off with a resume review. Next up is a preliminary chat, often on the phone or video, to see if you've got the basics down and if you'd vibe with the team. If that goes well, you might get invited for more interviews, which could involve skill tests, hypothetical scenarios, or chats with other folks in the company, maybe even higher-ups. The end game is usually hashing out the job details and maybe a quick background or reference check before they officially offer you the gig. Basically, everyone's checking each other out to make sure it's a good match.

Confirmed questions1 question
  • Can you share an example of a time you dealt with a challenging stakeholder?
Branding Brand logo
Branding Brand

Software Engineer

Engineering

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Onsite
Interview formats
Technical Coding Behavioral Behavioral Technical Coding Behavioral Behavioral

Started with a recruiter call. Then a 2-hour interview with a Branding Brand Engineer and the Engineering Manager, which was more technical, involving a React coding challenge and around 10 conceptual questions (some on newer React features). The manager's part was more behavioral, covering work background. The third interview was a 1-hour session with a Branding Brand Client's Lead Engineer. This was split between a React technical challenge and conceptual software engineering questions plus workplace situations. The final interview was with a Branding Brand Client's Engineering Manager, focusing on culture fit, likely under an hour. Communication was good throughout, with practical, day-to-day challenges discussed rather than brain teasers. Interviewers were nice and allowed time for questions.

Confirmed questions8 questions
  • Reason for wanting to join Branding Brand?
  • Questions about React concepts in general.
  • Could you build a React component from scratch based on the prompt?
Branding Brand logo
Branding Brand

iOS Engineer

Engineering

Mid Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral

I had a quick, informal chat first to see if we were both interested. Then, there was a simple online coding quiz. The next step was a Zoom interview where I was asked different questions and had to do a coding challenge. The second interview was a bit of a mess; I waited in an empty Zoom room for 20 minutes. I was about to leave when they quickly contacted me to rejoin. The interviewer only asked very basic questions about my background and didn't seem interested in my actual experience or any technical challenges I'd tackled. They focused heavily on iOS architecture terms and definitions, which seemed to be their main concern. The coding challenge itself was pretty straightforward and practical. I coded what I remembered, and they told me to use Google to finish some parts that Xcode usually autocompletes. Throughout this, the interviewer seemed distracted by laptop notifications and didn't really engage with my progress or the coding itself, not even commenting when the URLSessionDataTask didn't work as expected in the test environment. I'm not sure if there was a solution for that specific issue in that setup, but they didn't seem to care either way. I got a rejection email the next day. Overall, it was a negative experience; I wouldn't recommend it because they didn't seem to respect candidates' time or have a real interest in developers' backgrounds.

Confirmed questions2 questions
  • Could you explain the difference between a delegate and notifications?
  • What do you know about deep linking?
Branding Brand logo
Branding Brand

Angular Developer

Engineering

Mid Average Negative experience No offer 1 round
Interview process
Technical screen Take home
Interview formats
Coding

This was my second interview with Branding Brand after not getting an offer the first time. I was expecting a conversation, but it turned into a coding challenge immediately. The challenge itself wasn't hard, but I wasn't allowed to use any resources, so I had to have everything memorized. The interviewer was completely silent and didn't seem to care. It's a strange way to interview developers, and it makes me think of the rumors about how mismanaged the company is. I'd avoid them, they're not worth your time.

Confirmed questions1 question
  • What have you been up to recently?

Branding Brand Interview Questions

Quoted word for word from Branding Brand interview reports.

Could you explain the difference between a delegate and notifications?

Read reports

Can you build a frontend for a shopping cart using React?

Read report

What are your thoughts on using GCD or NSOperation instead of synchronized?

Read report

Formats, difficulty and experience

Across all 24 Branding Brand interview reports.

Interview formats

Technical 39%
Behavioral 28.8%
Coding 25.4%
System Design 3.4%
Presentation 1.7%

Interview difficulty

Easy 37.5%
Average 54.2%
Difficult 8.3%

Candidate experience

Negative 45.8%
Positive 37.5%
Neutral 16.7%

Reports by job function

Engineering 17
Operations 4
Analytics 2
Design 1