this post was submitted on 28 Aug 2024
71 points (98.6% liked)

Asklemmy

43945 readers
25 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago
MODERATORS
 

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.

all 32 comments
sorted by: hot top controversial new old
[–] [email protected] 34 points 2 months ago (2 children)
  • Don't try to bullshit your way through anything. It's actually a strength to admit that you don't know something. Bonus points if you can describe the resources you would use to learn the answer.

  • Almost a repeat of the first one, but slightly different. Don't play buzzword bingo or you'll sound like the 5th grader that just learned a new curse word and is showing it off on the playground. It's fine to use the industry jargon in appropriate ways; just be sure you know them.

  • It's an entry level position. The kind of skills and initiative they're going to be looking for is the desire to learn, the ability to correct/improve documentation, understanding/following procedures, thoughtful suggestions for improvements, and having enough confidence and competence that they don't have to babysit you constantly.

  • Networking / servers / security really covers a lot of ground and it leaves me wondering exactly what it is you're saying you'd like to do. Give some thought about how this entry level position helps you build your skills on your path to your ultimate goal and how you'll provide value along the way.

[–] [email protected] 9 points 2 months ago (1 children)

Everything here, but I'd like to build a little on this.

Remember that you are also interviewing the company. You need to make a decision about whether this is a place you want to work. Will it give you the opportunity to learn when you need to learn? Are they a team that treat each other well? Do they have good dynamics? Can you see yourself benefiting from working here beyond just taking a pay check?

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago) (2 children)

Worth noting and not crazy important for an entry level position. Double true if there are limited options available. Take the job, learn some skills (including how to work in a bad environment) and then look for and move on to better opportunities. Caveat: Just don't take one of these roles with a place where it's going to stereotype you and/or give you no transferable skills/knowledge.

[–] [email protected] 2 points 2 months ago

Even if you decide to compromise, it's worth doing so knowing that you are. It also looks good to the employer if you're taking a real interest in the position and sizing it up.

[–] [email protected] 1 points 2 months ago

Even if it is a deadend job, usually a year doesn't hurt. Unless the work or pay suck, but that's true everywhere.

[–] slazer2au 7 points 2 months ago (1 children)

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 3 points 2 months ago* (last edited 2 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.

[–] vladmech 13 points 2 months ago

Don’t try to BS your way through answers; if you don’t know, let them know that but also tell them how you’d go about getting that information.

[–] bluemellophone 12 points 2 months ago* (last edited 2 months ago)

Relax, show a willingness to learn and you’ll be ok.

I got my start working for university IT and made it all the way to a CS Ph.D. and into industry.

Edit: and get good sleep! It’s nearly midnight on the West coast, get as much good quality sleep as you can.

[–] [email protected] 10 points 2 months ago

Talk about your interests. Show a passion for your hobbies outside of work/the industry. Relate those passions to your goals within the industry. Generally just be interested and they’ll find you interesting. You got this!

Update edit: Congrats on the offer!

[–] [email protected] 7 points 2 months ago
[–] MissJinx 7 points 2 months ago

My tip.is always to remember that this is not yours to loose, its just an interview like a 1000 others you'll have. If you don't get it you didn't, try again tomorrow. When I think like that I'm usualy more relax and don't over talk.

[–] [email protected] 7 points 2 months ago

Be prepared to talk about class projects you've done, what went well, what didn't go well and how you'd improve that next time. If you do any extracurriculars like clubs, game night, or even a frat, include that as it shows you can be social.

[–] [email protected] 5 points 2 months ago* (last edited 2 months ago) (1 children)

It's okay to be nervous. You're not a CONfidence man.

[–] RandomUser 4 points 2 months ago

Remember that you are also interviewing them. They won't expect you to know all the answers, but will want someone that they can work with. If you can, answer questions with the STAR method (situation, task, approach, result), but don't waffle. You can use one piece of experience in a variety of ways: teamwork, research, urgent deadline etc.

It's ok to say that you are nervous, they should try to put you at ease.

You may be asked 'trick questions', these are not usually to to you up but to see how you work an unknown problem. There is no right answer. Not knowing stuff is ok. Not being able to think up a plan is less so.

Remember whatever the outcome, this is really useful experience. See if you can get a site tour, ask about the tech used... You can then add this to your knowledge for later. In my experience, industry is frequently several years ahead of academia so you get a good chance to understand the real world.

[–] Etterra 4 points 2 months ago

Go to the bathroom before you go into the place.

[–] Whelks_chance 2 points 2 months ago* (last edited 2 months ago)

STAR. For every question try to give a situation, task, action and result which came from you personally. E.g. situation, someone was manually copying data from an online portal every month. As a task, you're asked to write some code which scrapes an API, and you defined the task via docs and planned tests. Then as an action you worked on it for a few days, and the result was the company didn't need to manually spend a few days per month doing it, freeing up people to do more exciting things.

It shows you understand the problem and know how to go about solving it in a professional way.

[–] saddlebag 2 points 2 months ago

Interviewing is a very specific muscle. You should try and do as many as you can. It’s also something you should regularly practice, even if you have a job you love and never want to leave. I’d say every year or two, just go and interview at a half dozen companies for roles that could be interesting to you.

I’ve just been through several rounds of interviews with different companies for a tech role. You want to build a brand and learn to communicate it to others. This doesn’t mean you need to write a laundry list of skills that you’ve obtained but rather define who you are and practice explaining that to strangers.

Nothing can prepare you for an interview scenario except and interviews. I’ve been in customer facing roles as well as being the interviewer and the only thing they have in common with being interviewed is that you’re sharing a table with someone else.

Good luck for tomorrow!

[–] [email protected] 2 points 2 months ago (2 children)
[–] [email protected] 2 points 2 months ago (1 children)

I updated the post. It went really well. I got the job. I kept asking a bunch of questions and it wasn't too hard to do that since the company is really interesting since they dive into so many products.

[–] [email protected] 2 points 2 months ago
[–] Clinicallydepressedpoochie 2 points 2 months ago* (last edited 2 months ago)

Ask 'what success looks like' at said company.

[–] [email protected] 2 points 2 months ago

Hell yea, glad you got it. I have my third interview at a software company later today, here's hoping.

Networking/security is some really neat stuff, I have dabbled as I used to work doing systems stuff, but moved to robotics automations after that. See if you can get your new employer interested in paying a bit for you to get certs at some point (often if you bring it up that you want some cert, they might be interested in putting some percentage of money towards helping you get it), Network+ and those other Cisco certs are pretty sought after as I understand it and could definitely help progress your career.

Also welcome to the industry!

[–] [email protected] 2 points 2 months ago

Good luck. Nice to see happy news here.

[–] [email protected] 2 points 2 months ago (1 children)

Congrats! Welcome to the field. You'll be slinging ones and zeros in no time.

[–] [email protected] 1 points 2 months ago (1 children)

I have no idea what slinging ones and zeros mean but thanks

[–] [email protected] 2 points 2 months ago (1 children)

Moving bits of data: networking.

[–] [email protected] 1 points 2 months ago (1 children)

Oh I guess. I just thought it was really broad. Could've been literally anything computer related and even circuits related.

[–] [email protected] 2 points 2 months ago

I mean, it could also be data recovery, malware thwarting, etc. Working with digital devices. It's just a computer thing.