← Back to Directory

Patreon

Mid-sized

Screna has 3 Patreon interview write-ups. The most reported round is the technical phone screen (2).

3 interview notes · updated Jun 2026

Patreon·Software Engineer·Technical Phone Screen

Jun 2026
This was a follow-up technical question at Patreon for a software engineering role, digging deeper into a previous org chart problem. The interviewer pushed past the implementation itself and wanted a real complexity analysis, which is where things got more interesting.
  • Given your implementation of the org chart lookUp function (which returns role, direct report count, and total report count from a list of manager/direct_report pairs), analyze the time and space complexity. Cover both the preprocessing cost to build any data structures and the per-call cost of lookUp. Use N for number of employees and reference tree properties like depth or branching factor where they matter.

“I fumbled this a bit.”

View Post

Patreon·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Patreon system design follow-up focused entirely on scaling the read path for an org chart lookup service. The session went deep on caching, update propagation, and horizontal scaling tradeoffs, which I was not fully prepared for.
  • If the org chart lookup service needs to handle massive read traffic, how would you scale it? Walk through precomputing results per employee, caching options, handling org chart updates, and horizontal scaling.

“This was a follow-up to an earlier org chart traversal problem, so I thought I knew where it was going.”

View Post

Patreon·Software Engineer·Technical Phone Screen

Apr 2026
Patreon software engineering interview with a data structure / tree traversal problem dressed up as an org chart. Pretty straightforward on the surface but the total-reports piece tripped me up a bit.
  • You're given an org chart as a list of [manager, direct_report] pairs. Implement a lookUp(name) function that returns the person's role ('IC' if they have no reports, 'Manager' if they do), their number of direct reports, and the total number of people under them transitively.

“The direct report count was easy, just build an adjacency list and you're done.”

View Post