The Blogrammer

Today we had a session in A2SV about getting internships in those big companies from someone who got accepted into Bloomberg. I'll share what I learned from them in two posts below. 1. Resume Don't be lazy to slowly and smartly craft it. Because there's a big chance you will get rejected before it even reaches the recruiter's table because of something called an ATS (Applicant Tracking System), basically a system that reviews resumes in bulk and chooses the best possible candidates. On the header next to your full name, email and phone number, it's considered good to include links to your GitHub, LinkedIn, and Portfolio. As for profile and talking about yourself, when you apply to these top companies, you will probably write a cover letter as well, so not mandatory to fill this part out unless you have little content in it and wanna fill some space with it. On the education section, it's recommended to include your CGPA only if it's good (>=3.5). One important thing to not forget is if you graduated with something related with Software Engineering, mention the relevant course works. It's good showing familiarity with significant topics (OOP, C++, Embedded Systems, etc.) For A2SV peeps, when you include your journey put a description about it followed by relevant course work again, don't hold back to mention all those advanced topics you covered (advanced data structures, dynamic programming, etc.), and the project phase actually counts as an internship. So you can put that on the experienced section. Professional Experience. ATS rates higher for resumes that has numbers. So try to include more quantitative data. Like saying you built a project that has 500 active users or saying you improved the efficiency of this company's system by 60% or some numerical data like that. This is the section where you have the chance to talk about a complex project you worked on. Where you can brag by throwing those complex sounding technical words. If you don't have a lot of work and internship experience, make up for it on the Project Section. Project Section: Include projects that are based on at least 1 one of these concepts. 1. Impact for environment - A problem you saw around you, and that genuinely got fixed by the project you built. 2. Impact for self - A project that fixed a you problem that could possibly lead to fixing others' problem. 3. Technically difficult project - To show that you've worked with difficult and complex projects. It says that you can handle anything they throw at you. You can mention projects you built all by yourself or in teams. Teams is considered better since you're gonna be working in teams if you actually get hired and it implies you're comfortable with that. And don't put all the projects you got there. Quality over quantity. Sorry but image sliders and weather apps are not gonna do it. After including all these, if you still think your CV is under packed, you can add sections like Leadership and Extracurricular: if you were a class rep, or a club leader or so. Maybe even an achievements section, if you've ever been a part of a hackathon or something like that. Participating in hackathons is a great way to showcase your skills since it implies that you have done a project in a tight schedule so mention it even if you stood up to 10th place. And at last, Skills section. Only put the ones you focus on and are actually good at. Just because you heard about a language or framework doesn't mean it should be included there. A little tip when applying for specific companies is to shape your resume in a way that says I am a perfect fit in your company by mentioning programming languages or frameworks that the company focuses on (Bloomberg uses C++ as backend for example). Making the resume personally tailored to the specific company says that you put care and thought into making it so go ahead and do that. I'll send the resume template as soon as I have my hands on it. #blog #internships @the_blogrammer

2. Interviews Here you passed the ATS and the recruiter decided to talk to you and see what you got. First impressions matter a lot. Getting interviewed is a skill. Story telling is a skill. Not being like everybody else is a skill. Practice for the question "Tell me about yourself" in a way that can give a great overview about you and all the accomplishments, communities and work you did in just 5 minutes without making it sound memorized. Write down all the things you ever did. All the things that makes you proud and practice until it sounds natural. Before doing an actual interview, make sure you know in detail, about the company. About what they do, about their culture and so on. "Why our company?" is a tough question to get through. Don't ruin your chance thinking you can freestyle this question. See their values and try to relate what the company does into your achievements. Last but not least, English language skills. It matters! Knowing how to explain technical terms, problems, solutions, etc. Get used to it and become comfortable with it. Practice communicating with English as part of your day today life. Practice explaining different algorithms as well. In general, work on your Communication skills. This is just a blog I wrote by editing the notes I took while listening to him give us the session. #Blog #Internships @the_blogrammer

When they decide to offend you with memes. P.S It worked! #memes #random @the_blogrammer

My search history when I type 'hub' Vs yours 😎

Brought to you by boredom in Eco class #memes @the_blogrammer

LinkedIn is and has always been a social media that feels like it was made by aliens attempting to simulate human behavior

▓▓▓▓▓▓▓▓▓▓▓▓░░░░ ፷፱% (69%)

Lmfao #random

Gonna be preaching the Linux gospel, if anyone here in ASTU be sure to come by and say hi https://t.me/CSEC_ASTU/1763

POV: you write a lot of python