Mythic Interview Questions

Three steps total: a hiring manager screen, a coding challenge, and an on-site. The on-site consists of several rounds of interviews -- some technical, some social. Some of the technical interviews involve coding. They are not copy-pasted from LeetCode. Overall, I felt it was a challenging but fair interview.

They were very prompt, and provides us with rounds to showcase our knoweledge. Spoke with a two managers in the interview process, couldn't get past the second manager. Intitally they asked about our interests, this is so that they can identify where they can put us in. Second round, was a code pair session.

The interview process was a drawn out... I felt the company wasn't sure what they were looking for ... or that their reach was extending beyond their grasp. What they need is a CTO or VP of Information Technology... but they are trying to recruit a person at a lower salary to do a lot more work. This seems to be a consistent issue with the company culture.

Without any discussion about what I do I was given a cut-pasted question where the focus was on syntactic nits of C instead of understanding of the higher level skills of algorithms or compiler design. The interviewer seemed unsure of his compiler knowledge because he didn't have much. Mine was a better high level solution than the interviewer had anticipated, but they seemed disinterested to engage beyond their narrow experience and scope which should have been evident from the cookie-cutter manner the problem was cut and pasted. These questions may be okay for a entry level engineer but not for someone with extensive algorithm and compiler design experience. I applied with a strong internal referral but still the recruiter didn't sound very enthusiastic, so may be the company doesn't have sound engineering processes. The interviewer sounded snippy, like he just wanted someone to do what they were told, instead of really looking for long-term growth or skills. Overall, a poor fit for me and I couldn't see myself working for the interviewer located in Austin who was supposedly a lead but lacked strong compiler skills.

Only thing I can really fault Mythic's interview process for is the single most important thing: the end result. Their loss. I know full and well I can do the job, and I would have stayed to the end if given the chance. It starts with a phone screen, followed by an on-site. The center of the on-site is a 2-hour technical challenge, which is tailored to your particular role you are interviewing for. They must spend a substantial amount of time on this (I anticipate Mythic might start getting "interviewing fatigue" before long. So this might change later). Be prepared with loads of coffee and energy drinks. and bring your A-game. And don't try to BS your way through. Frankly, I think these challenges are designed so that--at most--only the very tip-top candidate can complete it (if that). They give you a very short time window to complete it, and really they are more interested in seeing how you behave under the circumstances. I can't honestly fault them for that--that's exactly the way I would have done it. HR was very up-front about everything. Which is refreshing, in a professional world where recruiters' communication normally is pretty dirt-poor; especially when you don't get the job. I liked the office, I liked the people. The work is meaningful. Not getting the offer was downright heartbreaking. But thanks to HR, I know exactly what it was: it had more to do with my fit for that particular role, and not about Mythic. Overall, I am probably a better person having done the interview; offer or no offer. However, I would have really preferred not to have spent all day + time prepping on it, if my chances for that particular role were slim to begin with. However, nobody's perfect, and I liked Mythic as a company.

There were many interview rounds unrelated to each other. They took forever to respond back. There was no coherence amongst the questions asked in separate rounds. Not recommended if you have short time window.

Interview was a little tough. Multiple rounds with different people. Technical round was a coding exercise with a senior engineer. Recommend practicing Leet code for preparation. 8 months of prep should be sufficient

Company Recruiter contacted me through LinkedIn. Interview process took three weeks since Interviewer is on vacation. Arranged an phone screen and Hackerrank codepair interview just before long weekend. Interviewer briefed about her experience and role(i didn't get not even a single point since she spoke most of the time on speaker phone). Interview process took one hour and give feedback during long weekend. Didnt even ask any devinfra questions and interview given feedback to recruiter that i am not aware of devinfra ( strange)!!!

Phone interview with a recruiter then an on-site with several key members of HR and office operations. During on-site, each interviewer comes prepared with 2-3 questions to ask so it is a pretty easy process to go through.

I had a phone conversation/introduction, a code screen, an onsite, and a cultural interview. Throughout the process I was given many opportunities to ask questions, and received a lot of information about the team and company. The process took several weeks. During the onsite, I met with several engineers to do whiteboard coding, technical discussion, and live coding. The engineer administering the live coding question was helpful and even helped me debug my code at the end.