Learn More
Resend Email
9
hyejeejung
8y

So it turns out I was interviewing for a senior role, when in fact I'm looking for a junior-mid role.

Two days ago I had a bad feeling creep up on me when the HR interviewer mentioned to me that they were looking to fill a senior role. I should have interjected. Instead, I stupidly asked the recruiter after passing the HR interview. He answered that the company would also take a mid-level developer and he thinks that I have a good chance. In retrospective, I'm not sure on what basis he made the judgement call.

I had the technical interview today and didn't get the job as I expected. But the same recruiter told me that the company said they'd take me for an intermediate role in the future, but I didn't make it for the senior role.

Can I take that as "you're not technically sound enough" put in a nicer way to soften the blow? But by the company or the recruiter? Or would they actually consider me for a mid-level role in the future? Who is lying or not lying?

Steam off my head now. Thanks for reading my rant.

Context: I'm still transitioning from another field and barely had one year of web development experience so far, half of which was from where I just learned to hack stuff together. I'm now going to focus on landing an internship or a junior role, without going through recruiters since I'd be waste of their time.

undefined

recruiter

interview
Favorite
Ranter
Comments
  • 4
    8y
    You will get a lot of "No's!" At every level. Keep building and practice the things that intimidate you! #goodluck 😀
  • 2
    8y
    @varEnigmatic Thanks for the encouragement! I was on the verge of cancelling the interview but I pushed through and it obliterated the fear of the unknown. I learned what to expect and what I need to study more. I'm also in the process of organising a regular meetup series for practising technical interviews in my city. One day I'll start ranting about a new job!
  • 2
    8y
    I've recommended not hiring people for that exact reason... It's meant to be factual in most cases, not personal. :) If I didn't think someone was a good fit for the company, it's more of a "they weren't a culture fit..."

    The recruiter shouldn't have submitted you for a senior role. That being said, practice interviewing is almost never a bad thing.

    I used to keep a journal of questions I was asked at technical interviews so that I never got a question wrong more than once. You'll get better at interviews as time goes on, don't give up!
  • 5
    8y
    Been doing this shit for more than 10 years no and I still get "no" when I interview. Most companies have no clue what they're looking for which is why interviewing is a crapshoot for all parties involved.
  • 2
    8y
    Just keep learning stuff and getting more experience.

    When a company needs a job doing and they realise you can do it, thats all that matters!

    Interviewers, recruiters and companies do not always know best. Learn more, get better, accept the knocks, then get the jobs and be even more successful :-)
  • 2
    8y
    There's also a reason why the tech industry is fixated on hiring "seniors". There is an illusion overall that someone senior will get things done better/faster. In short be very wary of companies that have more "senior" than junior engineers.
  • 2
    8y
    You'll get your in, at the right company at the right time, as long as you keep fighting for it.
    I spent more than 6 years trying to get my foot in the door of a local company, and I now have full-time work there, with no formal training or experience.
  • 1
    8y
    @lreading Thanks! Yes, I'll keep pushing! At the time of writing I think I was frustrated at how the recruiter could have been upfront about the role being out of my league, but a great experience came of it so I can't complain! I documented the problems too. Thanks for the tip and kind words!
  • 0
    8y
    @binhex I feel like there could be a better way. But it's like money. It's shit but it's the best model to hold the shit together until a better solution is born. I feel like programming assignments might be better, but then it often seems to end up a handful of effort.
  • 0
    8y
    @spl0 Yes! I'll keep going! Thank you heaps!
  • 1
    8y
    @pyrotazz That's inspirational, thanks heaps! I'm really thankful for all the support I had from devRant today. One day I'll share a news that I passed the technical interviews!
  • 3
    8y
    Been there. I just got turned down by a company for being "too confident" for a junior dev. Wasn't sure if it was a strange lie/blow off, or if it was true, what the hell that meant as I've never been described as "too confident" about anything. Interviewing is hard.
  • 2
    8y
    FWIW, anyone that wants to do a mock tech screen, I'd be happy to help. I'd probably only be somewhat helpful for Microsoft stack and JavaScript, but practice never hurts!
  • 2
    8y
    @chewbacca Haha wtf does that even mean? Too confident for a jr eng? So are jr engs supposed to piss themselves during an interview? "S/he didn't piss themselves - much too confident for a junior engineer. NEXT"
  • 0
    8y
    @binhex I really don't know. I thought it was better to act like I'm not terrified, and I wasn't acting like I was an amazing developer. Really strange stuff.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment