Developer
1. Your resume is too long. I don't have time to review an 8 page resume. Please don't do this. Same goes for resumes that are too short. Rarely do I see a use case where it's okay for your resume to be less than half a page long.
Prikaži ovu nit
Since I'm going through the hiring process again, I'm going to put some red flags here that lead to me immediately eliminating a candidate from a position.
-
-
-
2. Your cover letter has very obvious typos and grammatical errors. This may be specific to my line of work, but if you're going to be communicating on behalf of the company, your cover letter should be reviewed for grammatical errors and spell checked.
Prikaži ovu nit -
3. If qualifying questions are asked on an application, fill them out. If I ask you for some work examples and to explain why you chose them, I expect you to do that. Saying "N/A" or linking to your GitHub account is not going to fly.
Prikaži ovu nit -
4. Research the company. I can immediately tell based on an application if you even visited our website to learn at least a little bit about the company. Even 60 seconds of research into who the company is and what they do makes a positive impact.
Prikaži ovu nit -
5. If you don't have specific experience listed in the requirements, I'm okay with that, but I'd like to know about related experience and/or why you're interested in making this shift. Just saying you have no experience and leaving it at that doesn't tell me anything about you.
Prikaži ovu nit -
Novi razgovor -
-
-
3- usually qualifying questions (in my field) are plain useless « have you ever done that », yes I have check out my GitHub An HR process should be an exchange between a company and an individual not a one way effort from the individual
-
If I’m going to search basic things about companies I’m applying to, why doesn’t the company search basic things about the candidates? Sounds flawed
- Još 6 drugih odgovora
Novi razgovor -
-
-
Regarding point 3: I think linking your GitHub profile is fine, as long as you give some context beforehand for each project: “For this project, I did <description>, and used <languages/libraries> which helped the organisation <in that way>... For the full code see <github link>
-
Oh totally. That's the difference between answering the question and not. I have so many people respond with literally just a link to their github profile with zero explanation as to what's on there.
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.