
GiveCampus Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at GiveCampus.
Software Engineer
I had a really solid experience with the GiveCampus interview team. From the very first email, their communication was clear, timely, and genuinely thoughtful, which honestly makes a big difference when you're going through the stress of interviewing. Everyone I spoke with was friendly and transparent about what to expect at each step. They laid out the process clearly, gave me enough prep time, and followed up quickly after every round. No black holes or ghosting here, just real people who seem to actually respect your time. What stood out most was how human the whole process felt. Even the technical parts didn’t feel like a trap; it felt like they wanted to understand how I think and solve problems, not just quiz me.
- Can you walk me through your work history?
- Tell me about past projects you've worked on.
- What makes you interested in this company and this role?
Software Engineer
I applied through their website and got an auto rejection. But then the recruiter reached out a month later. The process started with a recruiter call, then a call with the VP/hiring manager, then a call with the CTO. After that, there was a live coding exercise, followed by a take-home assignment, and finally a final interview. It felt a bit unusual to have so many interviews before a proper technical one. Unfortunately, I didn't get past the live coding part. I got another auto rejection email and didn't get any feedback when I asked.
- Write a Ruby function to parse a CSV file and organize the data into various data structures.
Principal Software Engineer
The interview process included an HR Call, a Tech Interview, a meeting with the VP, and an SDI Interview. A major red flag was that the salary offered in the listing was not at all close to what was discussed. They also require you to be in DC twice a year. The qualifications were also misleading and didn't make much sense. They mentioned Python, but the team works in RoR, and you were expected to interview in straight Ruby. I still went through with the interviews to see if there was any potential fit. The meeting with the VP was the end of the line for me, similar to what others have experienced. My conversation with the VP felt confusing and didn't make much sense. Many questions could have been answered just by looking at my resume. By the end, I was unclear about what they were looking for or even what the job entailed.
- How often are you able to travel to DC per year?
- Have you worked with a project manager before?
- Have you had prior experience with a SaaS product?
GiveCampus Software Engineer Interview Questions
Quoted word for word from GiveCampus interview reports.
“Write a Ruby function to parse a CSV file and organize the data into various data structures.”
Read reports →“Could you build a palindrome checker app?”
Read reports →“Could you process a CSV file using data models?”
Read reports →“What are your thoughts on reading and parsing CSV data?”
Read reports →“What is your basic knowledge of React?”
Read report →“What is your basic knowledge of JS?”
Read report →“Have you had prior experience with a SaaS product?”
Read report →“Have you worked with a project manager before?”
Read report →“What makes you interested in this company and this role?”
Read report →Formats, difficulty and experience
Across all 6 GiveCampus interview reports.