Ticketer Server Developer interview questions

I was approached by George by email via Linked In, because of my relevant experience. I rarely respond to recruiter emails, but this one caught my attention because the industry, tech stack and office location were all a good match for me. The first phone call was on the Monday with George, who enthusiastically described the company and the working environment. I was convinced that Ticketer was a good opportunity, and so we arranged a call with Johnnie (Technical Business Architect) for a couple of days later. This second call felt like more of a technical chat than an interview, and we talked through the product and the vision for the future. These were appealing to me, and I felt that Ticketer offers a more dynamic approach to problem-solving than my current company. Although the 30 min call ended abruptly to fit into my working day, the feedback was positive and we scheduled a face-to-face. I arrived at the Ticketer office, and briefly met Johnnie before being handed over to Nik (CTO). This started informally with an interesting discussion about the company history, its growth and some of the challenges that lie ahead, as well as my relevant experience. The conversation was followed by a more standard interview question, where I was asked to design and talk through an online Captcha style system. Nik pointed out some flaws in my design, and I was given the chance to suggest solutions. Following that, I was asked to do an online test over the weekend. I did a full stack developer test, which consisted of several multiple choice questions, and some coding tests in SQL, C#, HTML5 and Javascript. This took around 2 hours. The feedback was positive and I was made an offer, which I accepted.