Tricky Coding Interview; thoughts?

No.11140673 ViewReplyOriginalReport
Just had my first coding interview and, good lord, that was not what I expected. No data structures or algorithms whatsoever. Also no real code writing.

Only had 2 sessions (was told that there was a misscheduling? Could that've been a lie and I got cut early or something?)

First session was coding, but not really. First question was a cost analysis problem, but not a coding one. Evaluate the cost of 3 different possible projects and recommend one to the CTO. This was really strange and threw me for a loop immediately. I tried to verbalize my thinking process as you should, but it was just calculating costs. No coding whatsoever.

Next question I absolutely fucked up on. First, I forgot that fg is the linux command for displaying processes. Just completely blanked and admitted it. They then asked if I knew how to find out more about a process. I mentioned ways to deconstruct its code/debug (like looking for improper forks), but he gave as a hint "it is the file grep uses". Knowing that grep can parse any text file, I didn't know what he meant. They just kept grilling me on this for like 15 minutes, and finally said it was logs. Of course I know what logs are! They were being very vague and saying "data files".

Third question was object oriented programming, which I explained fine I think. Standard build a system with superclasses, subclasses etc.

2nd session went amazing, and I really hit it off with the other developers. This section was more about my personal projects and previous job experience.

After that though, it was just a tour of the office and then I was sent out. I feel so strange. I was never asked a single data structure question at all, not a single thing about database management or algorithms either.

Do I have any shot? They said I asked a lot of good questions on the other 2 coding questions, and I solved them. Aced session 2. I just feel like its fucking ridiculous if it comes down to me forgetting a linux system command.