At the end I said there are more important matters than a broken access point, I would just change it, with a different model and everybody could focus on their real job instead of wasting time (Don't answer that, they wanted someone as talented as themselves to manage their LAN)
To be fair to the company, in this scenario it doesn't sound very much like the role was for you. I would totally expect a 'Senior IT Technician/Manager' to troubleshoot basic network problems and resolve them without swapping the hardware. Perhaps working in a technical networked environment is outside your current skillset.
Nick, were you there to know what were my answers? It seems so, according to your certainty. I think my answers did troubleshoot basic network problems, as you said. But they wanted a specialist. In such roles, reliably and cost go above pride. You learn to put efficiency above time consuming pride when you are in charge of the whole IT. I installed hundreds of wifi AP in my careers, the answers I gave Yoti always were enough to provide really good service. At the end I said if I can't find, there's no point in wasting more time, Yoti is not a wifi provider and has more important tasks. Money matters, this role would include budget management. When I installed a wifi service for small companies, it worked for years. The next time I'll install one, I would learn for the latest standards: so much changes in 2 years. No need to be a wifi specialist for a small company, and it's easy to re-learn it when it becomes necessary, with updated literature. For your information, their solution was awful, I would never use it unless I'm bored at work and need time consuming tasks, which never exists when alone for the IT Administration of 170 colleagues. But if they like spending time on settings again and again, it's their business.
I didn't know by heart the functions for reading CSV files and uppercase. I said in Systems Administration, we don't write code everyday, our code works for months, even years. And it's not secure to write a script from scratch, since we can't think about everything before going back to the IT Support. I usually take a good script from the internet, read all of it, adapt what needs be.
'I usually take a good script from the internet' does not sound like something somebody experienced in a command language would say. This exercise is extremely basic, one I would expect to find within the first few pages of a tutorial on learning bash with zero experience needed. Perhaps you should not put a command language on your CV if you are not confident in its most basic applications.
You have totally the same spirit as them. Great. Never said they were wrong. I'm pretty sure of my skill with those language as my programs were always reliable and secure and even taught them for a few years at university. I simply dont need them on a daily basis when in charge for the IT. I'd remember more easily how to secure an OS for a job interview.
Just learn a few examples of each competency (e.g. influences and persuades, works as part of a team, focuses on customers and partners) and you will ace it, seriously. There is very little preparation needed as every interview follows the exact same format.
This is no longer the case and interviews have changed to be more than just competency
This IS still the case. Questions are still competency based just as before but sometimes you have an additional role play aspect, a scenario to consider or presentation to complete prior to the interview. If you have access to the competency dictionary (internal document) then it would still be beneficial to read through this to prepare for an interview.