I led the effort to build a feature that allows users to easily keep track of business expenses. So, I would change it to the following: I was in the team that was responsible for Microsoft Dynamics CRM, which is a piece of customer relationship management software. In the above description, I mentioned Microsoft Dynamics CRM, but many people are not familiar with it. When you write your résumé, don’t necessarily assume that the reader knows all the technical terms, especially company-specific ones. My responsibilities included the initial research, planning the project, designing the product, creating wireframes, and writing and executing on a spec. Then, below it, I have a description of what I did: I was responsible for designing and implementing a specific feature within Microsoft Dynamics CRM with developers and other PM’s. Program Manager Intern at Microsoft, Redmond, WA, 5/2015–8/2015 The headline has the following structure: Let’s take a look at the first position as an example. Software Development Intern at Moneytree (a startup in Japan).Founder and President at Data Science Club at UBC (University of British Columbia).I have four positions in my experience section: You could also include it in the project section, but it will stand out more in the experience section. For example, if you led a team for a coding competition, you might want to include it here. If you have significant non-work experience that’s relevant, you can also include it here. It’s less relevant than my other, more technical positions. That’s why I didn’t include my math tutoring position. You don’t have to include every single position you’ve ever held. This is the part where you include the work experience you want to show. Then, we’ll go over each of them in turn to talk about them in more detail. The Structureįirst of all, let’s quickly go over what sections I have on my résumé. If you’d like, you can download my résumé here as you follow along with this article. I don’t really consider myself an expert on résumé writing, but hopefully I’ll be able to provide some insights based on my personal experience, as well as some research I’ve done to write this article. I’m also going to give you some general tips and advice on how to build your own software engineer résumé. Then, I’m going to show you how I would change it today based on what I’ve learned since then. In this article, I’m going to first walk you through the résumé I personally used to get a software engineer job at Google. On my programming-education YouTube channel called CS Dojo, many people have asked me to explain how I would go about writing a résumé for software engineer positions. By YK Sugi Here’s the résumé I used to get a job at Google as a software engineer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |