As the Spring semester approaches, seniors start attending job fairs and submitting resumes to the Word-parsing, keyword-detecting machines of industry HR giants. In the seemingly few years since I completed my bachelors, Iâ€™ve been through the motions enough to have learned a great deal in the process. Hereâ€™s some advice for seniors trying to land sweet engineering or IT gigs.
The â€œitâ€™s who you know, not what you knowâ€ principle is not bullshit. For better or worse, many things just work this way, and the tech industry is no exception. Almost every job Iâ€™ve had has been landed in part because of inside connections. Building these contacts is difficult for someone without industry experience, but can be overcome by involvement in student clubs, professional organizations, and other social activities. In my experience, involvement in mailing lists and local geek clubs has been the easiest and most beneficial means of networking. All the jobs fairs I’ve been to were a waste of time; most of the big companies just put your resume in a stack and direct you their HR website for further information.
One of the best things you can have when approaching a company is a pre-existing positive relationship with an inside contact. The better your relationship with your contact, the more theyâ€™ll sell you up before introductions are done or resumes passed. They will build good vibes for your interview, and generate internal momentum to push the process forward from the inside. A simple, â€œHey, Jim, I just wanted to give you a heads-up that thereâ€™s a really bright guy named Bob thatâ€™ll be submitting a resume todayâ€ can build a valuable pre-conception with the evaluator that gives you an advantage over other applicants, if not land you the job before the interview even starts.
When submitting cover letters and conversing with potential employers, donâ€™t send form letters. Show them youâ€™re genuinely pumped about the job and company, and that youâ€™re human by using real names instead of â€œTo Whom It May Concernâ€. Know your audience and write to their tastes. If you know senior industry people, kindly ask them to review your writing before submission.
Do your research on a companies projects before talking to representatives, and be sure to come up with things youâ€™ve done that could directly bring value to them. They donâ€™t care that you have three dogs and that your catâ€™s name is Mittens, but theyâ€™ll find it intriguing that youâ€™ve completed projects using Spring, Hibernate etc. If youâ€™re talking to a non-tech person, just point out that youâ€™re already familiar with what theyâ€™re doing and youâ€™d love to talk to the project manager to see if you’d be a good fit. Also remember that what you what now and what you can know by your interview are two different sets of knowledge.
Honesty & Confidence
If youâ€™re speaking to a technical interviewer, be honest about what you know. Theyâ€™ll easily see through dodged answers and weak responses. With practice, however, you can easily turn many negatives into positives. For example, if asked â€œ[a]re you familiar with Plajax: the AJAX for plague victimsâ€, donâ€™t say â€œNo.â€ Instead, say â€œIâ€™m familiar with Blajax: the AJAX for blind people, and have lots of experience handling server-side requests.â€ Always emphasise the positive. Practice in your next team meeting by using the word â€œandâ€ instead of â€œhoweverâ€ and â€œbutâ€. Speaking this way is an extremely valuable general-purpose skill, especially when youâ€™re in discussions with people you donâ€™t agree with.