Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Codex40416230135dAsk the companies you interview for for feedback, both when you get the job and not get the job (I don't see it as failing).
alex922135dSeems that the companies that you applied to are not very professional. I think that each interview participant should get a yes or no answer. Plain silence is not very professional. BTW, how long have you waited so far? I consider 2 weeks to be the maximum I would have to wait. 1 week is decent.
DucksCanCode4016135dAs mentioned, ask them for feedback. It doesn't hurt to go above and beyond with practical too. Maybe throw an Easter egg in too (only if they're a cool kind of company. I once put the konami code in a webapp and I got the job :).
And good luck!
mundo034367135dNow days it is more a bout the fit than the knowledge... Of course a minimum knowledge and willing to improve needs to be proven.
So here are my suggestions:
Don't lie, always be super honest about your knowledge and what do you do to be better
Ask questions, as many as you can ok the environment, rules, git, anything that will affect your work.
Be relaxed, like when talking ti a friend, show how you really are, be authentic. No one wants to hire a fucking liar false piece of shit.
Also ask for feedback and read through their bullshit
hitko699135dMake sure you prepare for the interview in every way; this includes learning as much as you can about the company - check out their website, try out their apps on your phone, see if they've posted any photos of their last team building trip, see what tools they use, etc.
And once you're at the interview, keep in mind the company is usually looking for a person to fill a gap in their team, not just some coder.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job