Interviewing for a part time internship for Entry Level IT. I am a full time student Comp Sci major and wanna go into networking, servers, security, so hopefully this gets me my foot in the door. I am a terrible soft skills person and really nervous. My friends told me to print out my resume and transcripts, I will surely do that. Anybody got anything else to suggest?

Update: I got the position! I honestly didn’t even prepare for it, didn’t even know what the company did. The comment that talked about learning to search things up was right on, they asked me what I would do if I didn’t know how to do something. I answered “looking things up, asking others, and consult documentation.” The company seemed really cool and is structured pretty much like Valve Corp in that they wanted jacks of all trades and it was company owned.

Thank you for all the helpful advice. It definitely helped me out, and hopefully, it helps others out as well.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    3 months ago

    Bullshit only works on non technical people. If you are in a technical interview saying you don’t know is the correct answer.

    Im a senior engineer at a global MSP, when doing my interview I 100% blanked on the TCP threeway handshake. Even now I only remember 2 of the steps, syn and synack.

    • d00phy@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      3 months ago

      Building on this, if you don’t know at first but think you might, it’s ok to ask questions to flesh out and better understand the question. It highlights your troubleshooting skills. If you still don’t know and they tell you the answer, there’s nothing wrong with asking follow up questions. This can demonstrate your interest in the subject as well as possibly highlight knowledge they haven’t specifically asked you about.

      In this vein, don’t forget that logs usually exist, and if they don’t you can often enable debugging. When something’s going wrong the first question I usually try to answer is “what’s the error message?” There isn’t always one, but if there is, knowing it can be a big help.

      ETA: Most technical interviewers recognize that the average candidate will need some training for their specific environment, especially for junior positions. They’re looking for trainability, critical thinking, and troubleshooting skills. You may not be well versed in the specific tool they use for, e.g., configuration management, but if you demonstrate an understanding of the concept, that will show them that you can be easily trained to meet their specific needs.