eventbrite logo
Eventbrite· Software Engineer II – Full Stack

Eventbrite Interview Experience – SWE II

Posted
25 May 2025
266 reads

Summary

I interviewed for a Software Engineer II (Full Stack) role at Eventbrite, which included an online coding assessment, HR introductory call, hiring manager round, system design, and a code maintainability round. I was ultimately rejected after the final rounds.

How it went

Company: Eventbrite Role: Software Engineer II – Full Stack Interview Format: 5 Rounds


1. HackerRank Test

Type: Online Coding Assessment Duration: 1 hour Platform: HackerRank

  • The problem involved creating an adapter class to convert responses from a third-party API to match the company’s pagination format.
  • The question tested understanding of OOP principles, clean code, and some backend concepts.

I passed this round and was invited to interviews.


2. HR / Recruiter Introductory Call

Duration: 30 minutes

  • Recruiter introduced themselves and asked for my self-introduction.

  • Discussion focused on:

    • Current notice period (they preferred <30 days).
    • Salary expectations
    • Why Eventbrite?
    • My current role, tech stack, and day-to-day responsibilities.
    • Preference between frontend vs backend.
    • A time when I went above and beyond for a customer.
    • The engineering process and team structure at my current company.

This was a non-technical round but quite thorough to assess motivation and team fit.


3. Hiring Manager Round

Type: Technical + Behavioural Duration: 1 hour

  • Mixed focus on technical depth, past experience, and alignment with Eventbrite’s values.

  • Topics included:

    • Why Eventbrite?
    • My work on previous projects and decisions made.
    • Situational and behavioural questions mapped to their core values.
  • Interviewer wanted to understand ownership, collaboration, and problem-solving mindset.


4 & 5. Final Rounds (Back-to-Back)

Duration: 2 hours total (1 hour each + 5-minute break in between)

4. System Design Round

Type: Full Stack Design Duration: 1 hour

  • Problem Statement: Design a user management system

    • Admin should be able to:

      • View all users
      • Search users by name and DOB
      • Edit user details
    • Users should be able to:

      • Register
      • View and edit their own profile
  • Covered both frontend architecture (admin and user views) and backend APIs, data models, and search functionality and database designs.


5. Code Maintainability Round

Platform: HackerRank Duration: 1 hour

  • Given a poorly written codebase (with bad OOP practices and tight coupling).

  • Asked to:

    • Refactor it to follow good object-oriented principles
    • Make it more maintainable, testable, and extensible

Final Verdict: Rejected

Questions asked (5)

  1. 01

    API Pagination Adapter Class

    Data Structures & Algorithms

    The problem involved creating an adapter class to convert responses from a third-party API to match the company’s pagination format. The question tested understanding of OOP principles, clean code, and some backend concepts.

  2. 02

    Why Eventbrite?

    Behavioral

    The recruiter asked 'Why Eventbrite?' and led a discussion focused on my current role, tech stack, day-to-day responsibilities, preference between frontend vs backend, and the engineering process and team structure at my current company.

  3. 03

    Describe a time you went above and beyond for a customer.

    Behavioral

    The recruiter asked me to describe a specific time when I went above and beyond for a customer.

  4. 04

    Design a User Management System

    System Design

    Design a user management system where an admin should be able to view all users, search users by name and DOB, and edit user details. Users should be able to register, view, and edit their own profiles. The discussion covered frontend architecture (admin and user views), backend APIs, data models, search functionality, and database designs.

  5. 05

    Refactor Poorly Written Codebase

    Other

    Given a poorly written codebase with bad OOP practices and tight coupling, I was asked to refactor it to follow good object-oriented principles and make it more maintainable, testable, and extensible.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Eventbrite recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!