Programming

17444 readers

221 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

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

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

What is your job interview ritual? (lemm.ee)

submitted 1 year ago* (last edited 1 year ago) by skybox@lemm.ee to c/programming@programming.dev

35 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] Cube6392@beehaw.org 1 points 1 year ago (1 children)

Hackerrank is a huge joke for so many reasons. I would rather hire a Dev whose biggest project thus far is an arduino project with 6 stars on github than looking at someone's hacker rank

[–] varsock@programming.dev 1 points 1 year ago

my experience with hackerrank is a company will use hackerrank platform to facilitate the online assessment - NOT look at someone "hacker rank" like you mentioned.

Candidates follows a link a company sent them and gives them an in-browser IDE to solve a problem. The platform records keystrokes, mouse events (like if you left the tab) etc etc. Then when you submit your code it is complied, executed in a sandbox, and tested with test cases. Based on which test cases pass, the execution time and memory usage, hacker rank will generate a report and fwd to the hiring team.

What I was saying in the above comment is if you had the right idea but your code didn't compile or failed the test case, it's as if you failed entirely. No hiring teams sits there and reads the code. Not even garuanteed that an engineer is reviewing your submission.

Hackerrank (to my knowledge) does not parse the code to determine your knowledge of algorithms, data structures, etc etc, it inferes it from which test cases passed and their execution time amd memory usage.