Real, anonymous reports from people who interviewed for Software Engineer at Shutterfly, newest first and distilled into what to expect across the loop.
Get your personalized Shutterfly Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I started with a short HR conversation, then about a week later I went to their office for the main interview. The whole experience felt pretty intense, mostly because the people interviewing me were very sharp and asked practical, hands-on questions rather than anything overly theoretical. I remember thinking I was being evaluated on how I work through real problems.
After the in-person round, I had a home assignment to complete. From my first discussion with the recruiter to a final decision, it took roughly two weeks, and I didn’t end up getting an offer. Looking back, I appreciated how direct the process was, even though the assignment made it feel like the bar was high and the timeline moved quickly once things started.
> 1 year
Difficult Neutral Haifa
My process was fairly focused: I did just one in-person technical interview. They began by asking a few questions about my background and the projects I’d done, and the tone felt straightforward. What stood out was that they didn’t stop at discussion—they turned the interview into active problem-solving.
I then had to write code on paper, and part of it included SQL queries. Overall it was difficult in the sense that it demanded accuracy and recall in a format I wasn’t used to. I didn’t receive an offer afterward, but the experience was clear about what they expected from me: practical coding ability, including data/query thinking.
> 1 year
Difficult Positive Fort Mill, SC
I went through a sequence of two technical rounds followed by a managerial round, all face-to-face. The questions were described to me as medium compl…
> 1 year
Average Positive United States
The interviews themselves were pleasant, and the communication felt clear during the process. The overall vibe was that it was moving, and I didn’t fe…
> 1 year
Average Neutral United States
I went through a short series of interviews that, overall, felt pretty easygoing. I didn’t get a lot of heavy technical questioning, and the conversat…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically starts with an HR call, followed by technical assessments and in-person interviews, often spanning two to three weeks. Candidates noted that the timeline can feel rushed, with some experiencing delays in communication after interviews.
HR calltechnical assessmentin-person interview
Technical & Coding Challenges
Candidates faced a variety of technical assessments, including coding challenges that required practical problem-solving skills, often in a live coding format. Some reported difficulty with the coding tasks, particularly when they involved SQL or architecture-focused questions.
coding challengeSQLarchitecture
Behavioral & Managerial Rounds
Interviews included behavioral questions and managerial discussions that focused on past experiences and fit within the team. Candidates were expected to articulate their thought processes clearly, especially regarding design decisions and project experiences.
While many candidates appreciated the clarity during the interview process, several expressed frustration with the lack of follow-up or feedback after interviews, leading to feelings of uncertainty and disappointment regarding their application status.
communicationfollow-upfeedback
Interview Atmosphere & Difficulty
The interview atmosphere was generally described as friendly and professional, though some candidates found the technical rounds to be quite challenging. The overall difficulty varied, with some candidates feeling overwhelmed while others found the process manageable.
Some candidates noted discrepancies between what was communicated during the recruiting process and the actual technical focus of the interviews, leading to confusion about the role's requirements and expectations.