What questions are asked at an interview for a vacancy of a circuit engineer?

Question

Electronics

Good afternoon!
Need advice from people with experience in passing/interviewing.
I got to my current job after internship, so there was no “normal” interview. I graduated from university in February and decided to try to find a better job now. After analyzing hh according to the requirements in the job description, there was some misunderstanding of what they might ask because the requirements differ quite widely: from standard ones - knowledge of data transfer interfaces and circuitry + board tracing, to the development of software for FPGAs and MCs. I am not embarrassed by software development, because I also did this, but how much it is needed because the main task is to develop hardware after all. In this regard, questions:

1. What are the interview questions for this position? I would like specifics on circuitry in the style: "You can't shortchange the transistor key - sit and learn."
   
2. Is it worth it to stick to CAD both in terms of board routing and in terms of modeling? At work, I traced boards in Cadence Allegro, and Altium is listed in most of the vacancies.
   
3. Since I only wrote test firmware for MK (on C) / FPGA (Verilog and on C for cores), will this be enough?
   

PS Of course, you can find out the answers to these questions experimentally, but I would like to go at least a little prepared.

Answer 1

1. Are you a circuit engineer or an electronics engineer? The first one develops circuits, the second one selects components, develops a circuit, designs software, etc. He often does programming as well.
2. Software is very different. I initially studied Altium, therefore, at any interview, I say that I work in it, because it is better to know one software well than a bunch - mediocre.
3. Start a portfolio. Circuitry is confidential, but it’s difficult to understand something from the PCB topology, so I have a pdf file where I upload topology screenshots, 3D models, other achievements, small descriptions for the boards.
4. If there is a code, then also post it on github and give a link.
5. Questions can be very different. In one place they gave me a circuit and asked me to explain what was happening on it, in another they asked what impedance is, what kind of bad influence of vias happens, the last time they simply asked "did you do it? and this?" went through the portfolio and took it for a trial period :D only the work will show my strengths and weaknesses (but I'm more of a tracer than an electronics engineer). In this case, it’s impossible to predict at all, so go and go to interviews. If there is a better opportunity via Skype, then in 9 out of 10 cases the company is looking for a specialist that is not at all like this and you are wasting your time. I once listened to the director for three hours, so that in the end it turned out that they needed a case design engineer, and I can only draw 3D models of components and in general I am a different specialist (this is despite that I specified on the phone who they needed and that I was doing a specific thing). So hold on.