
Webdam Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 35 interview experiences · FREE TO READ
Which role are you interviewing for?
19 roles · 35 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Webdam.
Front End Engineer
First, I had a coding challenge that was pretty interesting, followed by a tech phone screen. The overall interview process was great – it was fast, well-organized, and I met nice people, although my specific experience with the phone screen itself was quite negative. They asked some irrelevant questions about my coding challenge and an inappropriate personal question about my background. The technical questions were unnecessarily tricky, focusing on things a beginner would know or could easily Google, like obscure CSS properties. It didn't feel challenging or relevant for an experienced candidate.
- What is the function of this CSS property that I rarely use?
Senior User Experience Designer
The interview process felt pretty thorough and comprehensive, but honestly it was smoother and less intense than at other places I've interviewed. It kicked off with about two or three phone screens with really nice people from HR, the VP of Product, another designer, and a front-end dev. After that, I had an on-site day with a panel of staff for a brainstorming session, which involved about three or four interviews. Then came a take-home design challenge that was actually quite manageable. Finally, there was another on-site interview where I presented my solution for the challenge. The initial phone screens were pretty standard, covering my background, skills, and giving me a rundown on the company and what they're looking for. The main on-site day was pretty packed with back-to-back meetings with the product team – the PM, a designer, and the VP of Product (who would be my direct manager). They walked me through their product and asked how I'd tackle certain issues. Mid-day, there was a design challenge, more like a group brainstorming session with about five or six people observing, which was definitely the most nerve-wracking part. I also met briefly with a co-founder who asked a lot about how I work with developers. After that intensive day, I got a design challenge to do at home. I was a bit worried about getting a huge assignment, as some companies do send ridiculous amounts of work, but WebDAM's was reasonable. I had to solve a specific part of their product, focusing on UX but requiring at least one high-fidelity screen. It took me about 4-5 hours, though I tend to work pretty fast. I ended up presenting around 15-20 screens with animated interactions, and my sidebar panel design was high-fidelity throughout. Once I submitted that, they invited me back for a shorter, 2-hour on-site session to present my solution and thought process. I was super thankful to get an offer and for them to start the visa process.
- Could you share an example of a project you've worked on that progressed from an initial concept to a final developed product?
- Describe your process for working with developers.
- What kind of documentation or assets do you provide to developers?
Software Development Engineer in Test
The interview process was pretty smooth. The recruiter Nicole was really prompt and made sure I was informed throughout the process. The process started with an interview call from her followed by: A take home assignment. Phone interview with SDET, Phone Interview with Manager, Onsite->5 rounds (one was coding round and other technical discussions). Offer-> after 2 days. I really liked the people I interviewed with and everybody is super nice and happy about the place they are working at! One of the best interview experiences I had where I was in the loop from start to finish.
- A coding question of medium-easy difficulty was asked.
- Questions related to your technical testing and automation experience were posed.
Director
The hiring process started with a recruiter call, then a chat with the hiring manager. After that, I had my first of three onsite interviews, which was a panel of 1 on 1 meetings. Then, I did an online demo of the app. The second onsite was just a 1 on 1 with the CEO. The final onsite involved a 30/60/90 day presentation. I got the offer about a week after that. It was a pretty thorough process. I asked to chat with some other folks at the company, and they were cool with that. I'm glad they were thorough, but it would've been better if they'd combined some of the onsite interviews to cut down on how many times I had to go in. It's tough to get time off work for that. All in all, it was a good interview process.
- What are your criteria for selecting a new team member?
Webdam Interview Questions
Quoted word for word from Webdam interview reports.
“What is the function of this CSS property that I rarely use?”
Read reports →“What is your understanding of WebDAM?”
Read reports →“How would you draft an email to an external party to schedule a meeting?”
Read reports →“What kind of documentation or assets do you provide to developers?”
Read reports →“What qualities make for a good or successful customer service representative?”
Read report →“We have some questions about PHP, could you answer them?”
Read report →“We also have some questions about SQL, are you ready?”
Read report →“How do you approach brand positioning?”
Read report →“Tell me about a time when being aggressive was beneficial.”
Read report →Formats, difficulty and experience
Across all 35 Webdam interview reports.