applied internally to a role thatd be a nice pay pump. its a data role with a strong emphasis on python and sql skills. i studied my ass off on data concepts anticipating questions like “how would you start solving xyz problem” or “how would you find business insights on zyx” and the first question is “whats the difference between a dict and a list in python?” or hell, even a leetcode-like question. i like to think im decent at USING python and sql, but not having used them in a current role in ~2 years, these google-search-esque questions threw me off guard. i fumbled making up answers for a few but some i straight up had to say i have no fkn clue. so todays been a bit of a demeaning experience! has anyone else ever had an interview where they asked questions like that?

edit: thanks to yall for being supportive, this is the kindest comment section ive had. im still recovering from the embarrassment of these guys thinking I probably lied about having these skills lol. part of my difficulty is that ive been on a rotation program at work and have spent almost the last year on a cyber analyst position and it didnt hit me how much I forgot to code! so now I’m applying to some cyber roles too, wish me luck!!

  • Nollij@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    8
    ·
    2 days ago

    Interviewing is a skill in itself, and one that you can practice. I would encourage you to apply for all sorts of positions you don’t actually want just for the experience.

    Sometimes, these questions aren’t meant to get an accurate answer. They’re meant to see how you approach an issue, especially under pressure. I’ve seen people print out multiple pages of indecipherable code and ask a candidate “what does this code do?”. Of course, if you can answer it correctly you’re hired, but no one realistically can. But they can watch how you break down code you’ve never seen, in an unfamiliar environment, to piece it together.

    Sometimes the questions are meant to call a bluff, or reveal a know-it-all. In a good interview, you’ll flat out say “I have no idea” a couple of times. But you’ll follow it up with details on how you would handle it. For instance, I’ve never heard of a dict in Python until now, so I googled it. It seems they’re the same as key-value pairs that are common in other languages.

    They will never find a perfect candidate. The question in their minds is whether you’re close enough and can be trained.