interviewing at Loom in about 3 weeks for a mid-level frontend role. trying to get a sense of what the technical loop looks like now that they're under Atlassian.
specifically curious about: is the take-home still a thing or did they switch to live coding? what topics come up in system design at L4/mid-level? are they doing distributed systems or more product-level design? how much does knowledge of the Loom product itself matter vs. general frontend chops?
if anyone has done a loop in the last 6 months, even for backend or fullstack, sharing your experience would really help. even partial info is useful.
4 replies
mobile_mara
did a frontend loop at Loom about 4 months ago. they still had a take-home when I went through. it was a realistic small feature build, not a leetcode in disguise. they wanted clean component structure and attention to edge cases in the UI. how you handle loading/error states mattered more than raw algorithmic complexity.
staff_steph
on the system design question: at mid-level they're usually scoping it to product design, not distributed infra. think 'design the Loom recording upload flow' rather than 'design a global CDN.' the video-streaming context is relevant, but they're not expecting you to have Twitch-level video expertise.
newgrad_neil
is this helpful even for new grad roles? or is the loop structure totally different for entry-level?
frontend_fran
from what I can tell new grad loops at most places skip the system design and add more standard coding rounds. I'd still use this channel for general vibe/culture info but yeah the technical structure is probably different.