Agreed. It's almost impossible to know how to improve or make oneself more hire-able without that knowledge. I provide it to many applicants at MousePaw Media, but I've seldom received it from any company I've applied to.
Yes! A company should always respect that you gave your time, and the nerves it takes to show up for an interview. These can be nerve-wracking, and that should be appreciated.
I had a suspicion that might be the mismatch here. If the recruiter was asking for 5 years experience, I would venture a guess that's it's probably a place still using Angular 1.
My date was going by its official release, which I think it more relevant when looking for X experience in Y tech. If you worked with/on a pre-release tech, that should be gravy. :)
That said, I have seen a posting requiring that kind of experience in Vue. They should have just said "we want Evan You." :D
Figuring out what their culture is really like.
"Are you lying about all this great stuff about working here you just told me" just never seems to come off right.
A company hiring and letting someone go quickly doesn't show up as easily as your resume having a one month job stint because it just didn't work out because of culture or values, or they said you would do one thing and dumped you somewhere else.
I keep a list of questions around on what to ask to get a better idea of the company for when I look for a new job next time.
Do you have anywhere that you've shared that list? This is one of my frustrations, too, and I'd love to have some options for questions to ask companies.
It was questions like
"how the team structure and work divided?" Trying to get out how big team sizes are and how they function. Is work organized and driven by clear leaders or is it a free for all.
If you get to talk to your potential future coworkers and not just HR and boss, ask them how they got the task to be in an interview. did someone drop by and say "hey we got a person in right now come join" or did they know in advance and get to schedule work around it and actually prepare. Did people respect their time and yours.
Do they actually respond to anything in particular to what you say?
I'll be biting the bullet soon and looking for a new job again. Ill have to dig up my old note and send them to you. Though since it hasn't been long I wont assume I am too successful, but life's to short to stay where its not fun and interesting in tech.
I haven't really done the traditional job search thing, but I get so annoyed with recruitment for positions that don't make sense. Like, I have no interest in becoming a junior java dev that's a contract role in Kansas. Just seems to be a waste of everyone's time, especially if the recruiter gets snappy if you don't respond to them.
Not knowing upfront how long will an interview process last.
Same but for how much time will the process require from you (how many different interviews, their duration and on how many days).
Needing to do 1/2 day or 1 day work tests as technical test. Actually I automatically withdraw from any process that asks for this.
But there are many others:
Companies using recruiters.
Not taking into account when the applicant have a job already.
Companies that make any sort of personality tests.
Not being honest on what the position is about. E.g. getting people in the process because of Elixir and then letting them know that the position is about Ruby but there's a very small microservice that rarely requires any work in the stack which uses Elixir.
After graduating with a Law Degree, I decided to stick with my passion for software engineering. Currently focused on learning Javascript. It’s a dream to be able to master it enough to teach it.
I can relate. I'm fairly new but know I can be productive but the lack of years of experience is why I get turned down. I have heard from a few recruiters and it's always lack of experience. I'm trying to overcome that by building as many projects as I can.
I can certainly relate to the first three. I haven't found a job via a recruiter, so I have no experience with 4, and my last interview was for my current role, just over 6 years ago, so I can't recall what 5 is like.
Totally agree with (5). I have not had a single interview where the HR has gotten back to me with feedback, despite my asking with utmost politeness.
I feel this should be made mandatory as part of the interview process. If I were to interview someone, I would definitely want to let the candidate know the good and the things that need improvement (constructive criticism).
Here in Québec the shortage is big enough that they hire juniors for any roles. They pay them as juniors but expect intermediate or senior level skills. Getting a first job is hard enough, but now here we have to make sure the employers know that they are hiring a junior and that this is what they want.
While looking for job openings: everyone wants a rock superstar developer with at least 4 years of experience.
Interviewing: not knowing in advance what the requirements are (and if you even have enough skills for the position) and coming there "just for a chat" and getting into two hours interview with coding on the spot.
Being interviewed about algorithms and the bleeding edge stuff, and then, when I've given chance to look at their code, it's just a damn spaghetti mess.
Also, so-called "talent hunters", I don't like the idea of being hunted 😄
Sometimes the bug its me, i'm junior dev who wants to work with js and .net , love games and in my free times read about game design and development , hope some day thats gonna be my main work. GLHF
I'm Jake Cahill. Lifetime Pythonista, web scraping and automation expert. Enjoy books. Love my wife, dog, and cat, and think AI and Julia are pretty nifty
Location
Maine, USA
Education
A Master's patient mentorship and insatiable curiosity
As a freelancer, it's the fact that there is really nothing that I personally can do to make potential clients care how I can solve their very real problems until their hair is on fire. Then it needs to be done yesterday, but MUCH cheaper than quoted because they weren't expecting the outlay...
This made me stop freelancing an focus on my degree. I'm definitely going back to it now but I think having some sort of agreement form with stuff like "Agree to pay me extra for random deadlines"
Oldest comments (74)
Not knowing what the job will be like exactly. It is both frustrating and exciting 😃
Not having feedback about your interview or when you send your resumé and the company doesn't say anything, not even a rejection.
I'm aware that some companies receive hundreds of applications and can't answer all of them, but it is frustrating nonetheless.
Agreed. It's almost impossible to know how to improve or make oneself more hire-able without that knowledge. I provide it to many applicants at MousePaw Media, but I've seldom received it from any company I've applied to.
Yes! A company should always respect that you gave your time, and the nerves it takes to show up for an interview. These can be nerve-wracking, and that should be appreciated.
Dealing with HRs who know a sh** about the industry.
Funny part is, I saw once a job post where they want someone who has 5 years of experience in AngularJS (its initial release is in 2016) 😂
update: I mean Angular2+... thx Eric for noticing.
I agree with the sentiment, but Angular is definitely older than 2 years. Wikipedia says the initial release was in 2010.
Angular 1 (aka "AngularJS") was released in 2010. Angular 2 (aka "Angular") was released in 2016.
I had a suspicion that might be the mismatch here. If the recruiter was asking for 5 years experience, I would venture a guess that's it's probably a place still using Angular 1.
My bad, I meant Angular2+ for sure, and it existed actually since 2014 (still less than 5 years): github.com/angular/angular/graphs/...
We both know that Angular1 is not really practical.
And we both know that Angular1 and Angular2+ have dozens of differences, two differnet creatures!
So yeah, the previous experience with Angular1 shouldn't count as "experience" for Angular2+
My date was going by its official release, which I think it more relevant when looking for X experience in Y tech. If you worked with/on a pre-release tech, that should be gravy. :)
That said, I have seen a posting requiring that kind of experience in Vue. They should have just said "we want Evan You." :D
😂😂😂
I think it's when you need to talk in front of a recruiter, those moments are awkward and you never know what questions will be asked
Figuring out what their culture is really like.
"Are you lying about all this great stuff about working here you just told me" just never seems to come off right.
A company hiring and letting someone go quickly doesn't show up as easily as your resume having a one month job stint because it just didn't work out because of culture or values, or they said you would do one thing and dumped you somewhere else.
I keep a list of questions around on what to ask to get a better idea of the company for when I look for a new job next time.
Do you have anywhere that you've shared that list? This is one of my frustrations, too, and I'd love to have some options for questions to ask companies.
Sorry that notebook is an another state.
It was questions like
"how the team structure and work divided?" Trying to get out how big team sizes are and how they function. Is work organized and driven by clear leaders or is it a free for all.
If you get to talk to your potential future coworkers and not just HR and boss, ask them how they got the task to be in an interview. did someone drop by and say "hey we got a person in right now come join" or did they know in advance and get to schedule work around it and actually prepare. Did people respect their time and yours.
Do they actually respond to anything in particular to what you say?
I'll be biting the bullet soon and looking for a new job again. Ill have to dig up my old note and send them to you. Though since it hasn't been long I wont assume I am too successful, but life's to short to stay where its not fun and interesting in tech.
I haven't really done the traditional job search thing, but I get so annoyed with recruitment for positions that don't make sense. Like, I have no interest in becoming a junior java dev that's a contract role in Kansas. Just seems to be a waste of everyone's time, especially if the recruiter gets snappy if you don't respond to them.
You get those Java in Kansas emails too? :)
My top 3 for interviews:
But there are many others:
Being told "We liked you but someone with just a bit more experience applied so we went with them"
I don't blame the company for doing that, but holy heck is it ever frustrating.
Happened with me way too many times. :(
Th pile of emails wherein the required skills are not even closely related. No, I am not interested in a .NET C# Jr position in Washington D.C.
This is closely followed up with the end of the process wherein the day-to-day is nothing like the conversations leading up the offer.
I am in the same boat and can relate 100%
Hi Donita, so true, being a junior dev is a struggle these days.
This github repo We Hire Remote Jr. Devs might help.
I can relate. I'm fairly new but know I can be productive but the lack of years of experience is why I get turned down. I have heard from a few recruiters and it's always lack of experience. I'm trying to overcome that by building as many projects as I can.
^ This. Hang in there and build those projects Nicole.
Thanks will do! 😊
I can certainly relate to the first three. I haven't found a job via a recruiter, so I have no experience with 4, and my last interview was for my current role, just over 6 years ago, so I can't recall what 5 is like.
Totally agree with (5). I have not had a single interview where the HR has gotten back to me with feedback, despite my asking with utmost politeness.
I feel this should be made mandatory as part of the interview process. If I were to interview someone, I would definitely want to let the candidate know the good and the things that need improvement (constructive criticism).
Here in Québec the shortage is big enough that they hire juniors for any roles. They pay them as juniors but expect intermediate or senior level skills. Getting a first job is hard enough, but now here we have to make sure the employers know that they are hiring a junior and that this is what they want.
I found another resource full of summer 2019 internships
While looking for job openings: everyone wants a rock superstar developer with at least 4 years of experience.
Interviewing: not knowing in advance what the requirements are (and if you even have enough skills for the position) and coming there "just for a chat" and getting into two hours interview with coding on the spot.
The shift from the "why me" to the "why not me" state of mind...
Being interviewed about algorithms and the bleeding edge stuff, and then, when I've given chance to look at their code, it's just a damn spaghetti mess.
Also, so-called "talent hunters", I don't like the idea of being hunted 😄
code questions for a managment and mails job 😁
As a freelancer, it's the fact that there is really nothing that I personally can do to make potential clients care how I can solve their very real problems until their hair is on fire. Then it needs to be done yesterday, but MUCH cheaper than quoted because they weren't expecting the outlay...
This made me stop freelancing an focus on my degree. I'm definitely going back to it now but I think having some sort of agreement form with stuff like "Agree to pay me extra for random deadlines"
From my job search last year and early this year.
Ageism. I'd pass phone interviews, often multiple ones, only to get quickly dismissed when they figured out how old I was when they met me in person.
Lack of timely feedback from interviews, especially after initial contact with recruiters and HR reps.
Recruiters getting my name and number and calling about contract jobs I had no interest in or didn't have the appropriate skills.
Misleading statements by recruiters. They seem to work on the philosophy that it's not a lie if they believe it.
Recruiters who don't live in the same city who don't understand the length of commutes here.
Pushy recruiters.
Language trivia or code on a white board interviews.