Episode 369: Staying at a sinking ship and behavioral interview questions

Published: Aug. 14, 2023, noon

This episode is sposored by OneSchema, the best way to build CSV import into your product.

\n\n

Check OneSchema out at https://oneschema.co/softskills

\n\n

In this episode, Dave and Jamison answer these questions:

\n\n
    \n
  1. \n

    My employer offered a retention bonus after:

    \n\n
      \n
    1. The CTO left two weeks after I arrived
    2. \n
    3. Two weeks later 1/4 of the staff was laid off
    4. \n
    5. Two weeks after that the COO left
    6. \n
    7. Two weeks after that 2 board members resigned
    8. \n
    9. Three or Four weeks after that the Director of Engineering left
    10. \n
    \n\n

    What does that mean? What do I look out for?

    \n
  2. \n
  3. \n

    I discovered your podcast just about 2 weeks ago and I love it, and I listen to them daily when driving to office, this make forced RTO feels a little bit better.

    \n\n

    I am currently a mid to senior SWE at FAANG. For the past 1.5 years I have been trying to interview for other opportunities at Staff level. I have good result with coding and design interview but I felt like I\u2019m always falling short at behavioral questions. Example is \u201cTell me a time when you have a conflict\u201d. How do I go about showing seniority in these type of questions? I led a few projects and powered through a lot of conflicts to deliver results at my company, at the same time I can\u2019t think of a particular methodology I used to get through them. There were times I compromised, pushed back hard, meet halfway depends on situation. I dont want to show i\u2019m a pushover at the same I don\u2019t want to show i\u2019m not easy to work with. What are the signals they are looking for for a Staff level engineer in behavoral style questions

    \n
  4. \n