http://blog.interviewing.io/wp-content/uploads/2016/07/just-...
Also, maybe add a redirect from http to https?
31–40 of 394 posts
http://blog.interviewing.io/wp-content/uploads/2016/07/just-...
Also, maybe add a redirect from http to https?
This article seems like another example of mid-level people giving advice to junior-level people. There are far more red flags you can expect from a company by asking the right questions. The article doesn't dive into any of that and reads more like a few gripes from a guy who did way too many interviews and became jaded by it. The technical interview itself is not likely to be a good indicator of what work looks lik…
This article seems like another example of mid-level people giving advice to junior-level people. There are far more red flags you can expect from a company by asking the right questions. The article doesn't dive into any of that and reads more like a few gripes from a guy who did way too many interviews and became jaded by it. The technical interview itself is not likely to be a good indicator of what work looks lik…
Why is the font on this article so hard to read? Maybe it’s not the font, but the weight. I had a hard time reading it and stopped part way through.
"Not Enough Clarity about your Role" - Like the author mentions, this can definitely signify that the role is not important. The other thing I've noticed over my career is that it could be that the role involves "grunge" work (awful oncall shifts, doing backend work when you want to do only frontend, etc). Companies hide behind cool titles/department names/etc, promising whatever you want to hear to get you in.
Or you are interviewing "for the company" (e.g. Google or Facebook). While it fits their processes, it's always seemed a way to create and reinforce lock in.
Why is the font on this article so hard to read? Maybe it’s not the font, but the weight. I had a hard time reading it and stopped part way through.
"Not Enough Clarity about your Role" - Like the author mentions, this can definitely signify that the role is not important. The other thing I've noticed over my career is that it could be that the role involves "grunge" work (awful oncall shifts, doing backend work when you want to do only frontend, etc). Companies hide behind cool titles/department names/etc, promising whatever you want to hear to get you in.
Someone, somewhere at that company chose to hire someone... and they know what they want them to do. Why aren't they telling me?
Here I am sitting down expecting to divulge all sorts of things / do a dance, but they can't tell me what they want...
There's all sorts of reasons to not tell anyone / corporate circumstances, but it's a really bad foot to start off with / makes me worry.