Does extreme remote proctoring measure developer skills?
This is a certification aimed at developers.
After seven months of intensive Kubernetes preparation, including hands-on work, books, paid courses, constant practice exams, and even building an AI-based question simulator, I started the exam and could not get past the first question.
Within less than 10 minutes, I was already warned for: - whispering to myself while reasoning - breathing more heavily due to nervousness
At that point, I was more focused on the proctor than on the exam itself. The technical content became secondary due to constant fear of additional warnings.
I want to be clear: I do not consider those seven months wasted. The knowledge stays with me. But I am willing to give up the certificate itself if the evaluation model makes it impossible to think normally.
If the proctoring rules are so strict that you cannot whisper or regulate your breathing, I honestly question why there is no physical testing center option.
I was also required to show drawers, hide coasters, and remove a child’s headset that was not even on the desk. The room was clean and compliant.
In real software engineering work, talking to yourself is normal. Rubber duck debugging is a well-known problem-solving technique. Prohibiting it feels disconnected from how developers actually work.
I am not posting this to attack anyone. I am sharing a factual experience and would genuinely like to hear from others: - Have you had similar experiences with CNCF or other remote-proctored exams? - Do you think this level of proctoring actually measures technical skill?