this post was submitted on 22 Sep 2023
0 points (NaN% liked)

Programming

17343 readers
386 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

I'm in the middle of sending out applications and considering all the things I should refresh on. Does anyone have some good resources or practices they run through to get refreshed or otherwise prepared for technical and skill/personal interviews?

Ex. Sites, blogs, yt videos to refresh on data structures and algorithms. Checklist of things to look for when researching companies. Questions to ask recruiters during an interview. etc.

top 10 comments
sorted by: hot top controversial new old
[–] varsock@programming.dev 0 points 1 year ago* (last edited 1 year ago)

fantasize of all the ways I can hand in my resignation.

Then 3 months go by and still no offer, lower the bar and fantasize of all the ways I can hand in my resignation - but nicer

[–] JackbyDev@programming.dev 0 points 1 year ago

I usually skim the Gang of Four design patterns because that's something people love to ask about despite it not necessarily being something folks need to memorize for work.

I think the most important thing is to think of or look up interpersonal questions like "tell us about a time you got negative feedback" and have moments ready to talk about. If someone is asking me about HTTP verbs I know a lot off the top of my head but things like that I usually have to actively think about to remember.

[–] MarekKnapek@programming.dev 0 points 1 year ago (2 children)

The interview starts ... the interviewer asks me "Tell me about yourself." ... I respond "Did you receive my CV? I put all important details about me ... right there. What questions do you have about my past jobs?" The interviewer encourages me again to tell him about myself, my past projects, etc. ... Me: Awkward silence. ... Me to myself: Dafuq? Should I read the CV from top to bottom OR WHAT?

[–] addys@lemmy.ninja 0 points 1 year ago

They're asking not for the info, they are asking to see how you communicate (ie "soft skills"). Your response immediately demonstrates that you do not like people, are probably a PITA to interact with, and will have a hard time collaborating with any other humans who do not think exactly like you do. The good news is that soft skills are skills, and as such they can be learned and improved on.

[–] atheken@programming.dev 0 points 1 year ago* (last edited 1 year ago)

I’d rather they ask me a question on something for which I’m an expert (myself) and that I can prepare for, than to fire off leetcode question.

Yeah, it’s a little bit redundant, but it can break the initial tension and get the conversation going. You can also use the time to emphasize some specific aspect of your work history that you think matches up with the job req, or shows why you actually want to work there.

If they don’t ask this question/prompt, what question would you want them to ask?

[–] Cube6392@beehaw.org 0 points 1 year ago

Focus on jobs that don't do white boarding

[–] manapropos@lemmy.basedcount.com 0 points 1 year ago (1 children)

I’m here because I’m interested. I’ve put in so many applications but have had no interviews despite 3 years of experience and a masters degree. Y’all let me know

[–] randompepsi@lemmy.ml 0 points 1 year ago (1 children)
[–] manapropos@lemmy.basedcount.com 0 points 1 year ago (1 children)
[–] JackbyDev@programming.dev 0 points 1 year ago

I think you can phrase a lot of these more strongly. For example,

Provided 24-hour production support resolving issues with said system one week out of every month. Resolutions involved checking production Splunk logs, issuing bug reports, and pushing bug-fixes to production

  • Receive alerts and triage issues with Splunk to identify problems in a timely manner
  • Perform root cause analysis of production issues and apply hot fixes to production to ensure timely delivery of critical notifications so customer value is not impacted