Preguntas de entrevista de Datacom Systems

The process consisted of three interviews: an initial screening, a technical interview, and a final interview with the team. The initial interview focused on confirming your skills and experience. After that, you’re asked to prepare an architectural diagram of a system you’ve built or contributed to - something like a simple flowchart is sufficient. The technical interview centers around this diagram, with interviewers diving deep into different components. They clearly have strong expertise, so expect detailed questions. Topics included cloud technologies, AKS, system design, CI/CD, and general DevOps concepts. They won't ask questions that are clearly outside of the list of skills they posted in the job post or unrelated to the system you presented. The final interview was more of a casual introduction to the team. Overall, all interviews were conducted in a relaxed manner. The technical portion is challenging, but manageable if you have a solid understanding of the system you’re presenting - which you should, since it’s based on your own experience.

Interview was fine, reasonably easy. I did find the interviewer to be a little snappy with some of the other people interviewing though. She was swamped with discovery day sessions so I can understand being frustrated and possibly stressed, but admittedly it was a major turn-off from the company. Asked about: - Education - Experience - Transferrable skills - Why I want to work for Datacom Be aware that you need two managerial references to be considered, which is quite intense for an entry-level role. Sadly, I was not informed of this requirement until the end of the virtual interview, after I had already put hours into preparation and forage tasks, and provided multiple non-managerial references in my CV.