Interview Tips

  • Comments posted to this topic are about the item Interview Tips

  • I think it's important to familiarize with the current boilerplate questions that are trending on social media, not because these are actually great questions I would personally ask when interviewing a candidate, but because it will potentially come up when sitting on the other side of the table.

    Also, if asked a very specific technical question about a topic you're not very familiar with, you can always punt by confidently and casually responding with: "Yeah, I'd probably use PowerShell for that, and it's great for automating the process too."

    The beauty of this reply - there is a guaranteed 95% chance that it's technically true.

     

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • The timing on this editorial couldn't be better.  While I'm happy where I'm at, occasionally I get the "itch" to see what the grass is like on the other side of the fence, especially when I see the "jobs you might be interested in" emails with the magic phrase "fully remote" in them.

    I *know* I'm not all that great at interviews, that sort of "off the cuff" Q&A is not my forte' but often I know enough to get by (and, I'm not afraid to use the answer of "I don't know the exact answer, but here's how I'd go about finding out the answer.")

    We don't have enough turnover on the tech side of our team for me to be involved in interviewing, otherwise I'd have some selection of questions I could rif off of to "practice" my interviewing.

  • Preparation is key.  Beyond the technical aspects I'd say make damn sure you know what you want from your move.  In my early career my needs were very simple.  I want to do more of what I love and get paid for it.

    My needs and wants are very different at this end of my career.  I still love what I do, which is a not something to be taken for granted.

    At this end of my career I am more interested in the culture of the organisation and its stability.  I want to work with people  where respect goes in both directions.  If people don't agree then we have at least listened to each other and listened to think rather than listening for a gap to thrust forward an opinion loudly.

    There's the questions both from me as a potential employee and them as a potential employer

    • Can I/they do the job
    • Will I/they do the job
    • Will I/they fit in

    If I am going for a job in an industry I am not familiar with I will do some research into that industry so I understand the pressures and constraints under which I am likely to operate.  The job description should tell me what technical capabilities they are shopping for.  If you have 100% of their requirements those requirements then this may not be the job for you as you need stimulus not to stagnate.  Early on in my career I would have gone for roles where I only had 60% of the skills.  At this end of my career I'd go for a higher percentage, possibly 80% as my top limit.

  • My only advice on this subject is to stay FAR AWAY from LinkedIn.  Most of the people there should be LockedUp.

    Rick
    Disaster Recovery = Backup ( Backup ( Your Backup ) )

  • Eric M Russell wrote:

    I think it's important to familiarize with the current boilerplate questions that are trending on social media, not because these are actually great questions I would personally ask when interviewing a candidate, but because it will potentially come up when sitting on the other side of the table.

    Also, if asked a very specific technical question about a topic you're not very familiar with, you can always punt by confidently and casually responding with: "Yeah, I'd probably use PowerShell for that, and it's great for automating the process too."

    The beauty of this reply - there is a guaranteed 95% chance that it's technically true.

    My answer to that would be, "Excellent!  Show us how!"

    Don't let candidates BS you with such answers.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • My tips:

    Don't use an AI resume.  Write your own.

    Delete yourself from LinkedIn before you apply.

    Rick
    Disaster Recovery = Backup ( Backup ( Your Backup ) )

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply