Change.org 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 Change.org.
Change.org
Software Engineer
Senior Easy Neutral experience No offer 2 rounds
Interview process
Recruiter call Onsite
Interview formats
Behavioral Technical
Had a great interview with the recruiter there who seems to really be invested in my candidacy. They tried to fast-track the scheduling of my interview with the hiring manager because they knew there were candidates already in the latter stages of the interviewing process. Unfortunately, my interview with the hiring manager was cancelled as a candidate had accepted an offer for the role. Can't speak much for the rest of the staff but the recruiter was amazing and actually knew her stuff about tech tools.
Confirmed questions2 questions
- Tell me about how you collaborate.
- Describe your communication skills.
Change.org
Software Engineer
Entry Average Positive experience No offer 3 rounds
Interview process
Phone screen Take home Onsite
Interview formats
Technical Coding System Design Behavioral Technical
The interview process was pretty straightforward. It included a phone screen, a take-home assignment, and then an onsite. Nothing too intense. They asked a lot of questions specific to the programming language and also questions about handling scale, which is understandable given it's a consumer-facing app. A key point about the take-home is that the time it takes will depend on your familiarity with their tech stack and the role. Finishing it within the suggested time is a good sign you're a fit, otherwise, it might not be the best match.
Confirmed questions5 questions
- Did you get asked JS specific questions like spread operator and callbacks/promises? Also, how did you approach the take-home assignment?
- What about questions on scale, like throughput and threads?
- Did you get the classic TinyURL system design question?
Change.org
Software Engineer
Mid Difficult Positive experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Presentation
Interview formats
Behavioral Technical Coding Presentation
After the recruiter call, there were 4 interviews. One was with the manager to understand my experience and work methods. Then a technical interview focused only on architecture and development techniques. Another interview with a product manager to discuss job challenges. Finally, a live coding session to solve requirements in code.
Confirmed questions1 question
- When disagreements arise with product and design teams regarding technical matters, how do you approach collaboration?
Change.org Software Engineer Interview Questions
Quoted word for word from Change.org interview reports.
“What about questions on scale, like throughput and threads?”
Read reports →“Did you get the classic TinyURL system design question?”
Read reports →“And what about product questions, like how would you improve the product?”
Read reports →“When disagreements arise with product and design teams regarding technical matters, how do you approach collaboration?”
Read reports →“Did you get asked JS specific questions like spread operator and callbacks/promises? Also, how did you approach the take-home assignment?”
Read report →“Were there any behavioral questions like weakness/strength?”
Read report →“Tell me about how you collaborate.”
Read report →Formats, difficulty and experience
Across all 6 Change.org interview reports.