5 questions to ask the interviewer!

แชร์
ฝัง
  • เผยแพร่เมื่อ 31 พ.ค. 2024
  • Here are 5 crucial questions you should ask the interviewer in any software development interview to stand out as a data-savvy candidate.
    Join this channel to get access to perks:
    / @java.brains

ความคิดเห็น • 14

  • @SriramNarasimhan90
    @SriramNarasimhan90 หลายเดือนก่อน +11

    1) Time from commit to production - 2:58 - th-cam.com/video/2fZszuimOEw/w-d-xo.html
    2) Core review turnaround - 5:52 - th-cam.com/video/2fZszuimOEw/w-d-xo.html
    3) Incidence response time - 8:39 - th-cam.com/video/2fZszuimOEw/w-d-xo.html
    4) Deployment frequency - 11:01 - th-cam.com/video/2fZszuimOEw/w-d-xo.html
    5) Average onboarding time - 14:16 - th-cam.com/video/2fZszuimOEw/w-d-xo.html

  • @anthonya880
    @anthonya880 หลายเดือนก่อน +13

    Please make a deep dive course on Java 9 to Java 21 features.

  • @ZajoSTi
    @ZajoSTi หลายเดือนก่อน

    The best! Thank you.

  • @MadanNeelapu
    @MadanNeelapu หลายเดือนก่อน +1

    Great questions. Thanks a lot for this video.
    However, as Koushik mentioned.. pls don't take it too objectively.
    Although these are data driven but can be very subjective to the industry/domain.
    For example in a Healthcare IT project where Regulations are so stringent.. we need to go through a lot of quality, verification and validation phases and checks before we ship something to production servers. So Commit to production can be high.
    However in the same industry the Incident response time can be super fast. Thereby not every commit ships to production at the same speed.

  • @rtothec1234
    @rtothec1234 หลายเดือนก่อน +1

    We ship code fast. Cause we have no standards. 😂

  • @agytjax
    @agytjax หลายเดือนก่อน +1

    I am not a big fan of pushing the code on the same day(excluding Hi-Pri issues), no matter how small the feature or defect fix is.
    I have seen teams and managers pushing developers to push every feature on the same day just to earn some brownie points from customer, only to backfire with a Prod Hi-Pri Incident. The focus should instead be on process and due diligence. If the process is so bullet proof that it can push features to Prod on te same day without developers burning themselves, go for it.
    Otherwise stick to the process and take the time it justifiably requires

  • @themrambusher
    @themrambusher 15 วันที่ผ่านมา

    fresh video

  • @foruvasanth
    @foruvasanth หลายเดือนก่อน

    Morphis, the master!!

  • @user-ke2lz5kk7g
    @user-ke2lz5kk7g หลายเดือนก่อน

    U best

  • @Arkainebe
    @Arkainebe หลายเดือนก่อน

    Dear mr Brains
    I've sent you a couple of emails already without reply so far.
    Could you please have a look. I love your teaching style.
    thanks!

  • @sunilssutamani6347
    @sunilssutamani6347 หลายเดือนก่อน

    sir please give me access to the courses I sent email to you but no reply Thank you

  • @TheGuroguro12
    @TheGuroguro12 หลายเดือนก่อน

    😂