The interview process began with a recruiter screen, followed by a technical phone screen. The technical screen presented a LeetCode-esque problem, described as easy to medium difficulty, with four to five parts. It assessed knowledge of fundamental computer science concepts and multithreading.

The next round consisted of a coding round, a systems design round, and a 30-minute chat with the CTO.

The systems design round involved designing a system to integrate with banks, allowing users to inquire about their total balance. The interviewer was notably quiet and asked few follow-up questions, concluding the interview 15 minutes early.

The coding round focused on matching two strings and had multiple parts, of which I solved two.

The interview with the VP went reasonably well. They asked me to discuss my past projects and provide brief explanations. At the end, the VP indicated that I met their criteria but that the decision would depend on the other interviewers.

A few days later, I was informed that they would not be moving forward, without a specific reason provided beyond an enjoyment of our meeting. My assumption is that the position had already been filled, and my interview was largely a formality. This is because they had proposed scheduling the second round of interviews a couple of days before the original agreement, and my recruiter had mentioned the possibility of an offer that same week if my interviews were successful. I declined this adjustment due to prior commitments.

You are given two strings, s1 and s2. Return true if they are equal, or false otherwise.

Assume that s1 can contain a wildcard character, denoted by a '.'.

Examples:

i) r.kt, rokt returns true ii) r.k, rokt returns false

The second part is similar, but instead of a period, you will have a digit which denotes how many wildcard characters there are. For example, a3d translates to a...d.

Examples:

i) r1kt, rokt - returns true ii) r2k, rokt - returns false