It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Another point that bears mentioning is that tailoring your resume to individual job openings takes a fairly substantial amount of time. It might be worth doing if you're being extremely selective and want to maximize your chances at a position you really, really want. But I feel like "you should always tailor your resume for each job you're applying to!" is a recruiter's ideal, not an applicant's. There's no shortage of tech jobs in general and for most people, quantity is a quality all its own. The same resume landing on thirty desks has at least as much a chance of getting you somewhere as five painstakingly tuned resumes landing on five desks. Addressing the specific job is why we haven't ditched cover letters.
That’s a good point, but I still think it depends on the situation. It’s true that having a generic resume will save you time, but trying to stand out can only improve your chances, e.g. if you are applying to a Rails job, move your Rails experience to the top, reorganize your projects so these kinds are more prominently displayed. That shouldn't take longer than 10 minutes.
It’s also true that there is an abundance of job opportunities in tech, which gives us the luxury to be more picky. Aim for the job you’d love to have, don’t settle for the first one that will take you. (Of course this depends on your particular financial situation)
Also, like I mention in the post, cover letters are another way for you to stand out. A good cover letter gets you in the door, and probably into the short pile, but that pile will most likely only contain your resume (specially if they don't use any recruiting software to keep all documents in a single place). By then only your resume will get you further.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Another point that bears mentioning is that tailoring your resume to individual job openings takes a fairly substantial amount of time. It might be worth doing if you're being extremely selective and want to maximize your chances at a position you really, really want. But I feel like "you should always tailor your resume for each job you're applying to!" is a recruiter's ideal, not an applicant's. There's no shortage of tech jobs in general and for most people, quantity is a quality all its own. The same resume landing on thirty desks has at least as much a chance of getting you somewhere as five painstakingly tuned resumes landing on five desks. Addressing the specific job is why we haven't ditched cover letters.
That’s a good point, but I still think it depends on the situation. It’s true that having a generic resume will save you time, but trying to stand out can only improve your chances, e.g. if you are applying to a Rails job, move your Rails experience to the top, reorganize your projects so these kinds are more prominently displayed. That shouldn't take longer than 10 minutes.
It’s also true that there is an abundance of job opportunities in tech, which gives us the luxury to be more picky. Aim for the job you’d love to have, don’t settle for the first one that will take you. (Of course this depends on your particular financial situation)
Also, like I mention in the post, cover letters are another way for you to stand out. A good cover letter gets you in the door, and probably into the short pile, but that pile will most likely only contain your resume (specially if they don't use any recruiting software to keep all documents in a single place). By then only your resume will get you further.