I had the nerve to ask “Do you have any reservations about hiring me?” during an interview today. No regrets. Recommend.

  • 6
    so brave πŸ€—
  • 10
    Always ask the hard questions.
    Ask the ones that are hard for them to answer, and especially the ones that are hard for you to ask.
  • 4
    @Root Have any other suggestions for hard questions, experienced friend?
  • 1
  • 1
  • 1
  • 21

    I am tired as hell, so this isn’t a great list at all, but here are some off the top of my head.

    • Is the company profitable?
    • When will it be / what is the plan to make it profitable?
    • How do you (or the company) handle conflicts?
    • How does the company pay off technical debt?
    • I have a feature I want to write in a certain way because of architecture/scalability concerns, but management refuses to listen and wants a quick hack. Who do I talk to about this? Which will I end up writing?
    • Who makes the architectural/feature decisions, and are they open to discussion?
    • Who makes scheduling (deadline) decisions?
    • Do you do code reviews, have CI, staging environments, redundancy?
    • Does someone keep management and HR out of the devs’ hair?
    • What is the meeting policy? Do you have excessive or pointless meetings?
    • What is the average workday like? How about sprint?
    • How many people regularly work overtime?
    • Is slack/jabber/irc/chat/zoom informal? Does anyone feel like they have friends here?
    • Are there personality conflicts? How are they handled/mitigated?
    • Are you happy with the quality of the code/project?
    • Are you happy here?
    • Has anyone in your department gotten a raise in recent memory?
    • If you could change something about the company, what would it be? How about codebase/infrastructure?
  • 0
  • 0
    What did they respond @AmyShackles?
  • 2
    @orimligt A good question that I will feel more comfortable answering once I know how the next stages of the process shakes out. XD
  • 0
  • 1
    @Root πŸ“Œtactical dot right here
  • 0
    @orimligt yeah even I would like to know how they responded @AmyShackles?
  • 0
  • 3
    Received the news that they’re not moving forward, so...

    Response had been that their reservations were that they felt like I felt the need to prove that I knew what I was talking about and that I had a deeper knowledge about React than they’d expect from someone at my career level and they were concerned about how that would translate to a work environment.
  • 3
    @AmyShackles concerned that you know a stack in-depth and how it would translate in good work ?

    what kind of bullshit answer is that ?
  • 7
    @penless ¯\_(ツ)_/¯ I also thought that interviews were specifically opportunities to prove you knew things. It’s one of those few times where I was left thinking, “Maybe it’s ‘cuz I’m a chick?”
  • 3
    @penless yeah what the hell is that, I mean don't some companies expect you to have a deep knowledge of a stack. I think it's utter bullshit, @AmyShackles good you missed a bullet, these are red flags.
  • 1
    @AmyShackles "I had a deeper knowledge about React than they’d expect from someone at my career level and they were concerned about how that would translate to a work environment", don't sweat it my friend, this just mean that they were expecting someone with less knowledge to be paid with pennies.

    Anyways I hope you land in a good job 🌞
  • 0
    @AmyShackles Sounds like the "heu! We wanted a noob/beginner, so you're overqualified; bye" type of rejections. If so, then seems like you dodged a bullet.
  • 0
    Here's a great list of reverse interview questions:
Add Comment