Behavioral and OOP design questions involving some database queries

Don't want to spoil their interview, but there were no LeetCode-style riddles. I had to do very simple things that I do all the time in Rails, like make endpoints, design classes, and so forth. If you normally copy-paste your company's code and make necessary changes so you don't have to write boilerplate, stop doing that for a bit before interviewing here. Lesson learned. The job posting didn't mention jQuery and I was asked a jQuery question, though the recruiter told me that I'd be asked about it in the technical interview a week beforehand so I should have been prepared.