Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
HR will not read your FAQ. Never.
Today, shit is more complex than in the 1980s and requires collaboration. HR is there to filter out candidates who have too low social skills to be of value in a team. -
@TeachMeCode These questions appear in *technical* interview. Should I perceive team lead as a robot? It may be not obvious, but in 3rd world country HRs are nothing but a redirect request. Come to think of it, this perfectly fits your description. 🤭
@Fast-Nop OK, what about tech lead that can ask for GitHub profile? So, they don't click on personal website linked in resume, or they just ignore the massive parts there like FAQ? There is stuff that can be inferred from oral communication, of course, but I feel like I should get at least some attention in return to writing efforts. I wouldn't like to work on a dick that ignores what I type. 😕
Speaking of "FAQ": what a suggestive abbreviation. 🤦♂️😆 I'd like to find a synonym to "FAQ". Perhaps, "Common Questions"? -
@vintprox They may care about portfolio projects, and you can link that in your resume.
What they won't do is dropping half of the interview in favour of RTFM. -
@Fast-Nop fair enough. I just have an impression that if I need to answer the same questions in more detail, then I could use this as a reference for the rest of the room, which saves time and breath.
Also, this looks like a fair test about how much of my stuff anyone reads, it just tells me more about the further work in the team. -
It strikes me as odd that we end up being the tested ones, but not the other way around. I'm sure someone here is familiar with the background check and carrot-and-stick. So, why shouldn't I use these methods to probe who I entrust my time working with?
-
@vintprox Of course, the interview is a mutual process.
I remember one of my first interviews as fresher where the boss admitted that they didn't have any documentation, only the code. When I asked whether there were any plans to move on to a more professional way of development, the interview was pretty much over. He had failed my test.
Related Rants
-
marolt41Looking for a job as a deveoper be like: Job title: car driver Job requirements: professional skills in dr...
-
sagemaker23Just applied to a new job with this as my cover letter. Wish me luck!
-
TrojanMorse9One company i applied for never wanted to give me the job because they where building a prototype and they wan...
(Questions below.) At this point I probably just whine about job search in IT w/o much commitment. It's because I don't learn stuff from interviews and have no willingness to prepare for primitive questions from HR's book. You know, stuff like: "What was your experience on previous jobs and why you quited them?" and "What are your advantages and cons?"
Even though I see them a bit discriminatory. I barely find words and make them audible alrite, and so rush to the stack questions. I answer 50% of them in average, 20% ideally. As a result, I get no conclusive offer. Fair... probably not. Doesn't matter.
All of a sudden, idea chimed in to make a personal website with all of the frequent questions answered in advance. At last, I've got some time to make the decent replacement of the CV into a landing page that communicates my professional and emotional ability to headhunters.
TL;DR: I wanna make my personal website portfolio and I need your word about the following.
1) Can I make up for the absence of my own live projects with OSS commitments or other smooth talk?
2) Is there a merit in answering the common interview questions right off the bat in written form?
3) So, I already prepared 4 conclusive theses with thoughtput choice of words, that I wanna place as a grid in first scrolling section. I call it "Principles", but perhaps there is a synonym to this one or it's good as it is?
4) I don't want to represent myself as a blunt set of "features". How do I transite into explaining the usage of my stack in these circumstances? Less text better, right?
question
jobhunt
introvert
content
interview practices
job hunting