
Greenbits Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 27 interview experiences · FREE TO READ
Which role are you interviewing for?
12 roles · 27 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Greenbits.
Customer Success Manager
The interview process at Green Bits involved 2 phone screens and then 4 video calls, each lasting about half an hour. The whole thing took around 2 months, spanning the holiday season. Everyone on the team was really helpful, answering all my questions and making sure I understood what a career path there could look like. They really seemed to care about that. You'll need to be ready for behavioral questions about your past work experience. They always leave plenty of time at the end of each call for you to ask questions. Overall, it was a good experience with the hiring team.
- Tell me about a time you had to handle a really angry customer. What did you do?
- Describe a situation where you successfully de-escalated an issue with a difficult customer.
Customer Support Specialist
Applied online and got an email asking me to solve a problem and provide clear instructions for someone without technical knowledge. Shortly after, I received an invitation for a phone interview with HR. This initial HR chat was short and focused on my background and personality. Next, I had a second phone interview with the head of the Customer Satisfaction team. While their questions were prepared, we had a good conversation, giving us both a sense of each other and the company's culture. The final stage was a two-hour onsite interview with four different groups. The first was a relaxed chat about my work history. The second interview began with scripted technical questions but evolved into a friendly discussion where we shared experiences on various topics, including our personal interests. The last interview was with two people from the Customer Satisfaction team, and their dog, who came over to say hello.
- Tell me about a time you had to deal with an angry and irate person you were working with.
Rails/Front End Developer
It took a couple months to hear back after I applied. A 3rd party recruiter reached out and basically wanted me to rehash my resume since she hadn't read it. Then, I was told I'd get a code challenge and then a phone interview with the CTO. I never received the code challenge. On the day of the phone interview, they emailed me to reschedule, which was kinda last minute, and I had already set up to work from home for it. The phone interview itself was a waste of time. The CTO seemed uninterested. After he bragged about their fast-growing startup for 5 minutes, he only asked me two questions. The first was okay: 'describe a challenging project you've worked on.' His response was just 'ok cool.' I would've expected him to ask me to elaborate or follow up based on my experience. Then he asked what 3 values I'd instill in a startup if I owned one. I'm not interviewing for CEO, and those questions are better for an in-person interview after a technical assessment. He then asked if I had questions. I didn't really, as I had done my research and was expecting to be interviewed. I asked a few to keep things going and learned they pair program 6 hours daily, so keep that in mind. He said he'd discuss it with his team and contact me, but I got an automated rejection email.
- Can you tell me about a challenging project you've worked on?
- If you owned a startup, what three values would you instill?
Software Engineer
Green Bits' hiring process was pretty chill compared to other Bay Area tech companies. I went through 3 rounds in total, and everything was handled smoothly. They were super flexible too; my final interview, which was supposed to be onsite, was done remotely because I was out of town. First, there was a quick chat with the recruiter to see if my background matched what they needed. Then, I had a technical phone interview where I had to solve a coding problem on a whiteboard within about 45-60 minutes. The last step was an onsite interview that lasted around 4 hours. I met with four people: a QA engineer, an engineering manager, the head of HR, and a product manager. They asked me two coding questions, but mostly, the conversation was about how I'd fit into the team, my previous experiences, behavioral stuff, and giving me a chance to learn more about them.
- Can you share a career accomplishment you're particularly proud of?
- Tell me about a past project or achievement in your career that you are most proud of.
Greenbits Interview Questions
Quoted word for word from Greenbits interview reports.
“How do you make ajax requests using Promises?”
Read reports →“How would you address a bottleneck in a binlog linear data stream caused by a transform step?”
Read reports →“In your opinion, what's the quickest way to end this conversation that I'm not interested in having?”
Read reports →“What's a product you dislike and why?”
Read reports →“Can you wait, for the third time, one more week for your interview?”
Read report →“Can you describe how you would architect a simplified Facebook/Twitter clone?”
Read report →“Are you specifically interested in API testing?”
Read report →“If you owned a startup, what three values would you instill?”
Read report →“What interested you in the marijuana industry?”
Read report →Formats, difficulty and experience
Across all 27 Greenbits interview reports.