Picsart logo

Picsart Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
71.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Picsart.

Showing 3 of 7
Picsart logo
Picsart

Senior Software Engineer

Engineering · a year ago

Senior Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Coding

The interview process was pretty smooth overall. Started with a screening interview, and then I had a code challenge assessment. That code challenge was tough, though. It basically required building a full project from the ground up, including list and detail pages. For the list page specifically, they wanted infinite scrolling and virtualization, plus routes, responsiveness, styling, and all that. It was actually kind of fun to work on, but it was definitely hard to get done.

Confirmed questions1 question
  • Can you share some insights into your behavioral and past experiences?
Picsart logo
Picsart

Software Engineer

Engineering · more than a year ago

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

The interview experience was pretty standard. It felt like they cared more about theoretical knowledge than practical skills for the actual job. I was asked about JS reactivity, the event loop, and Big O notation. I talked about data structures like hash tables, linked lists, and trees. They seemed a bit surprised and threw in some unexpected questions, like asking me to explain how the JavaScript event loop works and how garbage collection functions. I also explained how to update indexedDB. I got rejected because I admitted I wasn't super deep into garbage collection details, although I did try to explain my idea about dependency graphs for unloading functions. They disagreed, saying it's more about tracking references, not just call counts. Apparently, the main reason for rejection was that they wanted someone with a deeper JavaScript understanding than I showed, even though I've been using it professionally for nine years. One interviewer was also surprised when I mentioned other WebGL formats like .glb and .gltf, acting like I was making them up.

Confirmed questions4 questions
  • Can you explain garbage collection and the event loop in JS?
  • Tell me about basic geometry.
  • What about canvas and webgl?
Picsart logo
Picsart

Software Engineer

Engineering

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

I had an interview with a recruiter who also does HR admin stuff. She was great - friendly but professional, and she told me about the company, the role, and what to expect. It wasn't a typical recruiter interview, and I really liked it because it felt like they wanted me as much as I wanted the job. I also enjoyed hearing the story of how Picsart was founded. The technical interviews were standard but pleasant, and the onboarding process was smooth, thanks in part to the recruiter who also managed it.

Confirmed questions2 questions
  • What is your interest in Picsart?
  • Have you had any experience using the Picsart application before?

Picsart Software Engineer Interview Questions

Quoted word for word from Picsart interview reports.

Can you explain garbage collection and the event loop in JS?

Read reports

Have you had any experience using the Picsart application before?

Read report

Could you describe the most challenging project you've tackled lately?

Read report

Can you share some insights into your behavioral and past experiences?

Read report

Formats, difficulty and experience

Across all 7 Picsart interview reports.

Interview formats

Coding 35.3%
Technical 29.4%
Behavioral 29.4%
System Design 5.9%

Interview difficulty

Easy 0%
Average 85.7%
Difficult 14.3%

Candidate experience

Positive 71.4%
Neutral 14.3%
Negative 14.3%