Production

I just had my PE coding interview for Meta, and honestly, it didn’t go well. The phone screen is split into two parts: PE coding and PE basics. I was expecting more file-handling-related stuff or maybe a "dinosaur handling" type of question. At the start, the interviewer mentioned there would be two coding problems. I was given a variant of an LRU cache – a problem requiring me to return the most recent, popularly viewed store, but there were quite a few conditions to handle. I was slow to code, needed some hints, and by the end of the interview, I had only managed to code the first problem. I never even got to the second one as time ran out. Next week, I have the PE basics interview. I’m familiar with Linux, but I’ll need to spend this week diving deeper into it, especially troubleshooting. My big question: Is it worth preparing for PE basics, or does bombing the coding part mean I’m already rejected? If anyone has been in a similar situation or has any advice, I’d really appreciate it. Should I focus my efforts on nailing the PE basics, or is it better to move on? Thanks in advance! Edit: I am sorry I noticed I didn't put acronym in brackets. PE stands for Production Engineer.