Girls Who Code logo

Girls Who Code Interview Questions
& Process

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

Based on 126 interview experiences · FREE TO READ

1.6 Rounds average
Easy Typical difficulty
80.2% Positive experience

Which role are you interviewing for?

13 roles · 126 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Girls Who Code.

Showing 4 of 126
Girls Who Code logo
Girls Who Code

Salesforce Administrator

Operations · more than a year ago

Mid Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The HR Manager was super nice and always kept me in the loop. The Hiring Manager threw some technical and non-technical questions my way. Even though I didn't get an offer in the end, the whole interview experience was great and I felt informed the whole time.

Confirmed questions2 questions
  • Tell me about any exciting Salesforce release updates.
  • What is the origin of change sets?
Girls Who Code logo
Girls Who Code

Work Prep Lead

Operations · more than a year ago

Lead Easy Negative experience No offer 1 round
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

Got an email to set up an interview and then had a 30-40 minute Zoom chat. It felt pretty standard for the job, with questions all tied to the job requirements (like experience, what I learned, hows and whys). The reason I felt it was a bad experience is that I pretty much knew I wouldn't get an offer by the end. The interviewer seemed a bit cold and cut me off when they thought I was going off track. I was trying to give a full answer, but since it wasn't exactly what they wanted to hear, they thought interrupting was the way to go. I could tell they weren't really into it and just wanted to finish. They didn't do much of the usual polite stuff or give any reassurance that they were listening or understood, which usually makes for a better interview. I felt I had to write this review because it seems that for this interviewer, just being aligned with the GWC mission and passionate about increasing diversity in tech, which really shows the company's values, isn't enough to get past their idea of who should be in the role.

Confirmed questions5 questions
  • Can you share an example of a time technology failed you and how you handled it?
  • Describe your experience with managing corporate partnerships.
  • What draws you to this role at Girls Who Code?
Girls Who Code logo
Girls Who Code

Computer Science Teaching Assistant

Other · more than a year ago

Entry Easy Positive experience Accept offer 1 round
Interview process
Recruiter call Technical screen Presentation
Interview formats
Behavioral Presentation Technical

there were three parts of the process within the one interview meeting itself. the first part was behavioral, the second part was a brief mini-lesson (where you treated the interviewer as a student and pretended to be a teacher reviewing a concept from programming), and the third part was a quick technical question about debugging a simple program.

Confirmed questions1 question
  • How would you approach a student or group of students who do not seem engaged or interested in learning in class?
Girls Who Code logo
Girls Who Code

Outreach Manager

Sales · more than a year ago

Mid Average Negative experience Decline offer 3 rounds
Interview process
Recruiter call Take home Onsite
Interview formats
Behavioral Technical Presentation

So first there was a phone call, then I had to do this big work sample that I wasn't paid for, and then I went in person. The recruiters were super nice and always got back to me quickly. But they asked for a bunch of work samples that took over 5 hours to complete (a really detailed country research analysis that needed to be only one page, an email draft, and a sales pitch). This was all before the in-person meeting. When I finally met them in person, they told me they hadn't even reviewed the work sample. My advice to them is that asking for a work sample is easy for them but takes a ton of time for candidates. It would be better if they asked for a shorter work sample or paid us for it. Apparently, other people who interviewed there had the same issue. Maybe they should rethink their hiring process to be more considerate of people's time.

Confirmed questions2 questions
  • What makes you interested in this organization?
  • Where do you see yourself career-wise in the next few years?

Girls Who Code Interview Questions

Quoted word for word from Girls Who Code interview reports.

Describe an algorithm to determine if an integer array of length 10, containing numbers from 1 to 99 in any order, has a pair that sums to 100.

Read reports

How would you calculate the sum of all integers within a given array?

Read reports

How would you check if any two numbers in a given array of integers from 1 to 99 add up to 100?

Read reports

If you have an array containing numbers from 1 to 1000, with exactly one number missing, what method would you use to identify that missing number?

Read report

How would you determine if any pair of numbers in an array of 10 elements, containing random numbers between 1 and 99, sums up to 100?

Read report

How would you find two numbers in a list that add up to 100?

Read report

If you have a list of numbers from one to a certain number, and one is missing, like having 999 numbers from 1 to 1000, what approach would you take to find the missing number?

Read report

Can you teach me how to find the minimum integer in an array?

Read report

Formats, difficulty and experience

Across all 126 Girls Who Code interview reports.

Interview formats

Behavioral 42.3%
Technical 24.7%
Presentation 17.2%
Coding 12.5%
Other 2.2%

Interview difficulty

Easy 50.8%
Average 46%
Difficult 3.2%

Candidate experience

Positive 80.2%
Neutral 14.3%
Negative 5.6%

Reports by job function

Other 101
Operations 9
Engineering 6
Marketing 5
Sales 4
Product 1