
CodeScience Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Which role are you interviewing for?
9 roles · 12 reportsCandidate interview experiences
First-hand accounts from people who interviewed at CodeScience.
Business Development
I had an initial call with the recruiter, then a video call with the sales manager. After that, I had a joint video interview with two employees at my level. Next were individual video calls with the CEO and COO. I also chatted with HR about benefits. The final stage was a presentation over video to everyone I had interviewed with, plus some others from the company. While I was fine doing everything remotely, it was good that I'd met some team members before, as there would have been a chance to meet in person otherwise. The process was tough but taught me a lot about the company and let me share about myself. It was thorough enough that I could decide if it was a good fit. The presentation is challenging, but if you set expectations clearly upfront like in a sales deal, it should go well. They don't expect you to know everything, but they want to see you've done your research.
- What are the best traits for a salesperson, in your opinion?
- How would you collaborate with an ISV AE at Salesforce to ensure your territory's success?
- Is this quota achievable, and why or why not?
Technical Architect
So, I think there were five people I talked to, from different teams. We did them a few days apart because I wasn't in a rush for a new role and they were cool with that, which was great because my schedule was already packed. It was a bit different from other places I've interviewed. They hit me with a lot of technical stuff and asked me to solve problems on the spot, but they also asked a ton about me personally – like hobbies, family, travel. It felt more like a chat than an interrogation, honestly. Even if I hadn't gotten the job, it was a pretty good experience. I was kinda nervous for the final presentation to a group of people, but I got to talk about a project I really loved. They grilled me on pretty much everything, from the tech choices and design to dev environments, data size, connecting with other systems, rules, keeping track of changes, testing, and getting code out automatically. I was upfront about what I didn't know and explained how I'd find out, which I think is important for any professional. It all went well, I got an offer, and started a couple weeks later building my first AppExchange product.
- Did you ever build stuff for the AppExchange?
- Explain the standard oAuth web flow steps.
- Tell me about your background with version control and CI/CD.
Quality Assurance Analyst
I applied online and got an interview request 2 days later. I had a screener (video call) with a recruiter 2 days after that. The first negative experience was when the recruiter rescheduled the interview a couple hours before it was to start, moving it later in the day. I had plans that I ended up canceling to accommodate this new time. The conversation was pleasant and consisted of standard questions: "Tell me about yourself...", "What do you know about CodeScience", etc. It ended on a good note and I was told they'd get back to me in a few days. A week later I got an email from the recruiter stating hiring had "hit a bump and [they] aren't moving as fast as [they] usually do." Essentially, hiring for the position had been put on hold for some reason, but they'd keep my application for when they start back up again. Three days after I received that email, I got a rejection email. Strange and almost dishonest if you ask me, since I had just been told they weren't hiring right now. Oh well.
- Can you tell me a little about yourself?
- What knowledge do you have about CodeScience?
Project Manager or Engagement Manager
The interview process was great, casual and an enjoyable conversation as opposed to the traditional interviews. I thought at the end of the interview and conversation with the HR director that I had a good shot at a second interview. It was even mentioned during the interview that after reading other Glassdoor interview reviews that they had made improvements, one of them being that they wouldn't let people hang and waste their time or wonder where they were in the interview process, that they would let someone know if their candidacy was being ended. After 2 weeks, due to being over the holidays I emailed to follow-up on the status of my application/ interview and the position, only to be ignored. No response stating "thank you but we have filled the position", "thank you but we are proceeding with other candidates", or even "we are still involved with the reviewing process". It only takes 5-10 seconds to send a quick email response to a job seeker so they know where they stand, but they did not even have the courtesy to do so. The only way I determined that the position was filled is that it was no longer listed on the website. These people forget what it's like to be a job seeker and should use a bit more common courtesy and respect to keep applicants informed. Very disappointed in the company as due to the reviews and interview process I was very excited about the opportunity.
- What are you looking to do, as opposed to reviewing experience, where are your passions and interest levels of future employment taking you?
CodeScience Interview Questions
Quoted word for word from CodeScience interview reports.
“Explain the standard oAuth web flow steps.”
Read reports →“What's the most crucial part of the SCRUM process?”
Read reports →“Is this quota achievable, and why or why not?”
Read reports →“Could you code out a whiteboard representation of the provided form fields?”
Read reports →“Can you write some SQL statements?”
Read report →“For a given item description, what would you test?”
Read report →“What are the best traits for a salesperson, in your opinion?”
Read report →“How would you collaborate with an ISV AE at Salesforce to ensure your territory's success?”
Read report →“Did you ever build stuff for the AppExchange?”
Read report →Formats, difficulty and experience
Across all 12 CodeScience interview reports.