Schoology Software Engineer Interview Questions
& Process

I found the role through Hired.com. First, I had a call with their technical recruiter. Then, I had to sign up for Schoology and do some coding challenges on their platform. I had to complete 2 out of 6 problems from a 'Programming Competition' packet, using languages like PHP, Java, Ruby, or Python. There were optional assignments too, for JS/CSS, web questions, Big O, and a small Schoology test. After that, I went in for an in-person tech interview that lasted 3 hours. 2.5 hours were for a tech challenge where I had to build a site in PHP, Ruby, or Python, create a DB table, load CSV data, and make pages to CRUD records. The last 0.5 hours were for questions. Finally, there was another in-person meeting with the CEO/CTO and other team members. They don't ask for much but offer chances to do more with optional tasks. I did a lot of the optional stuff, not sure if it helped, but I got an offer in the end.

They reached out to me for a lead role, but after our first chat, they asked if I'd consider a senior software engineer position instead. I agreed, and we set up an onsite interview. During the onsite, I only had two interviews, one with new people and one with the person I spoke to on the phone. He then mentioned they might not have the budget for me even if they liked me. A few days later, the recruiter asked me to come in for another interview, but only after the initial phone guy called to say he didn't think I was a good fit for Schoology. I went for a second onsite, and it went great. Then the same initial phone guy called again and said I aced the second onsite, but because of how I answered some questions in our first call, I was only being considered for a regular software engineer role (not senior). He also said they couldn't meet my salary expectations. At that point, I withdrew my application.

I applied and then there was a long wait, over 2 weeks, for the phone interview. I had to push them a bit because I had other things going on, and then they seemed to speed things up. Not sure if it was the recruiter or Schoology's fault. The phone interview itself wasn't too tough. The interviewer, who was an engineering VP, was really nice. There weren't any actual coding questions, mostly questions about design, databases, and architecture.