
Jiffy.com Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 17 interview experiences · FREE TO READ
Which role are you interviewing for?
5 roles · 17 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Jiffy.com.
SEO Strategist
I had a phone interview with the recruiter first. After that, I had a remote video call with an executive. It was a quick 15-minute chat, very direct and to the point. They showed me some website data and asked for my ideas on strategy to improve their metrics. They actually offered me the job at the end of the call. I didn't get to ask much about the company culture, work-life balance, or how they handle team conflicts. I declined the offer because they wanted me to start immediately, giving me very little time to decide, which was a big deal since I'd be leaving a stable job for something uncertain. Also, the company seemed really focused on revenue through rapid growth and hard work. While I'm a hard worker and not against growth, I didn't see much substance behind it to keep motivation high. It's a custom t-shirt business that appears to have high turnover and, from what I could see, treats employees like disposable tools. I might be wrong, but there wasn't much to convince me otherwise. My suggestion to the execs would be to find better ways to get employees to commit, like building an appreciative culture focused on collaboration and problem-solving.
- Are you okay with a super fast-paced work environment?
Software Engineer
The interview for Sr Software Engineer at Jiffy.com was tough but educational. They really focused on software engineering basics, like what makes code good (easy to read, SOLID) versus bad (anti-patterns, tech debt). They also asked about practical stuff, like breaking down big methods into smaller parts and fixing flaky tests with RSpec tools. The panel talked about keeping up with new tech using company resources and their detailed PR review process (checking context, edge cases). They pointed out common Rails issues like N+1 queries and messy ActiveRecord code. It was a tough process, especially needing to know about flaky test workflows, but the interviewers knew their stuff and were helpful. It gave a good idea of how the company values clean code, current practices, and teamwork. It’s great for engineers wanting to grow and work with high tech standards, but you gotta show off your Rails skills and be ready for new best practices.
- Can you walk me through how you would refactor a big, messy method into smaller, testable pieces without breaking anything or introducing bad practices?
Customer Service Representative
So there were 4 interview rounds for this role from July 7th to July 22nd, 2022. The first was general questions, the second was an email round. The third round had the department manager asking more specific, situational, and behavioral questions. The final round was with a senior HR person who said I'd get an offer via email within 24 hours. It was an employee referral. After two days with no offer email, I followed up. Surprisingly, they said hiring was paused for the August 2022 batch due to a management decision. They promised I'd be the first to know when the next training batch started. I followed up again in 2023 when I saw the job posting and the referral confirmed hiring was back. It's really disappointing to be given false hope like that. The whole hiring process took almost two weeks, then they paused and kept me in the pipeline for the next batch with false hopes. I was so optimistic they'd respond, but it was all for nothing. I'd advise not to believe what they say because they don't keep their word.
- Can you give an example of a time you turned an unhappy customer into a happy one?
Product Manager
It was a pretty terrible experience, felt super fast and chaotic at first, but I liked the energy. They didn't focus much on my experience, more on 'culture' fit and hustle. I got a homework assignment, basically 'do a week's work in 48 hours for our roadmap'. It involved researching a new product vertical, proposing a strategy, designing the product, and presenting it to leadership. It was intense, and the craziest part? They never discussed ANY of it in the 5 interviews I had after it was due. I got lots of positive feedback and was excited, then they just ghosted me. I followed up with everyone, even a C-suite leader, but no response. Turns out it's all smoke and mirrors, lots of energy but no real direction. The homework was likely just fishing for ideas to steal. I know I dodged a major bullet.
- Build a new product for a "hyper-growth viral engine" to boost adoption.
- Design and build an AI strategy bot to analyze data for you.
- Decide between running a viral campaign versus rewarding your loyal customers.
Jiffy.com Interview Questions
Quoted word for word from Jiffy.com interview reports.
“What's the distinction between empathy and sympathy?”
Read reports →“Can you explain the difference between empathy and sympathy?”
Read reports →“Build a new product for a "hyper-growth viral engine" to boost adoption.”
Read reports →“Design and build an AI strategy bot to analyze data for you.”
Read reports →“Create a long-term product vision to achieve our 700M revenue goals and disrupt Adobe.”
Read report →“Do you have any upcoming travel plans?”
Read report →“How can I handle speaking with others if I have an accent?”
Read report →“How do you define teamwork?”
Read report →“Can you describe a negative online shopping experience you've had?”
Read report →Formats, difficulty and experience
Across all 17 Jiffy.com interview reports.