One coding question for Meta E6 interview

Had a phone screen with Meta today for an E6 role. 30 minutes was behavioral questions, which left 25 minutes for coding. I think behavioral went well as I’ve had large scope that I can speak to. I thought we’d move to coding after 15 minutes of behavioral but interviewer said we were ahead of schedule and wanted to ask more behavioral. Coding question was straightforward, so I was able to get to optimal solution easily and coded it up with 15 minutes left. I offered to run through a test or skip in case we wanted to do another question but interviewer said let’s test. Communication was strong, code was clean, caught some minor bugs in testing. Biggest issue is I might have been off on my space complexity answer. Other than that, I’d say my coding performance was about as good as it could have been. Edit: Def wrong on space complexity. I said O(n), should have been O(n^2). Other variations of this question are of O(n) but one modification to the requested output (and thus data stored) makes it O(n^2). I knew this might be the case, I wish I said as much. Does one coding question mean reject? Or am I overthinking it? @meta