Example Of A Basic College Grad Resume Your Name: Fill & Download for Free

This is a fascinating question.I'm a font guy. I love type and I love studying and using typefaces. "How do I choose the right font" is such a simple question yet there are so many ways to answer it.For one thing, I've been paying attention to fonts my whole life. Ever since my parents got me "The Print Shop" on my Commodore 64 when I was 13 years old, I've been aware of how typefaces have personality, and that personality is suitable for some uses and wildly improper for others.For instance, does this logo's typeface communicate the kind of things you'd go to a massage parlor for?I'd expect to walk out of there bruised and bloody. Is Agatha even a woman?Would you trust your financial well-being to a CPA with this logo?It's not even spelled correctly. Ashley must not be a "details person".Would you drop your children off here?"Leave your payment in a brown paper bag near the bench in the park. Cash only, nonsequential bills. We'll tell you where to collect your child."Here are a few more examples of these for further illustration.It helps to be aware of a lot of different kinds of fonts, and to be able to identify them by name. It does you little good for you to say, "You know I really like the font they use on Law & Order, I want to use that for my project." (Of course, something like that can probably be found quickly using a well-phrased Google search. And if you have a sample of the font you're looking for, you can upload it to WhatTheFont! and usually get a correct answer.)*Get one of these and put it on your office wall (or set it as your desktop background):All Popular Font Families in one Typeface Poster. Study it. Stare at it when you're meditating. Lose yourself in it when you're zoning out. It's awesome. Absorb the shapes and let yourself pair them with the names. It's not as great a resource as the huge poster I had on my office wall when I was first starting out—sadly, I can't seem to find it anywhere on the interwebs, or I'd show it to you**—but it's an excellent and handy resource to help familiarize yourself with the Greats. (And be sure to check out some of the links provided at the bottom of the poster, like this one.)A designer also has to be aware of the basics of type usage. Serifed type is often used for long copy, like books and magazines. This is because the serifs make the characters more recognizable, and the text easy to read in bulk at small sizes. Serif body copy usually pairs well with sans-serif display type. There are mountains of exceptions, but you have to understand the rules before you can effectively break them.I test a lot of fonts when I design a logo. I'll sometimes go through 20-30 different faces looking at how the characters relate to each other, the overall mood presented by the forms, readability at large and small sizes, how I might use color, how the letterforms create negative spaces and how I might use them, and so forth. I have to have a solid understanding of the attitude I want to project. For instance in the massage logo example above, the attitude communicated is strength, confidence, power, pride. A massage parlor should be welcoming, warm, relaxing and soothing. The typeface chosen must broadcast these attributes, or at least not be in conflict with them.Fonts, to me, can also be very personal. For a long time, I was a huge Apple fan. (I'm less of one now, but that's another story.) I used to collect Apple advertisements and brochures. All through the 80s and most of the 90s, Apple used a customized tooling of Garamond for all their marketing materials, called Apple Garamond. It looks like this.I loved that font. For a time, I wanted to use it on everything, like my college papers. It's beautiful, professional and so friendly (compared to, say, Times New Roman).Gag. What a boring, lifeless, colorless character set. It says, "I don't really care what typeface it is."I started to realize that while I loved Apple Garamond, it was not working in my favor. The characters are very narrow. When you're writing college papers, often assigned using page-count as a metric ("Turn in 5 pages about [whatever]"), a narrow character set makes more work for me. A font with a wider stance, say, Bookman...Now that's a font for term papers. And anyway, Apple Garamond is Apple. It screams "Apple". Apple used it for so long, so effectively, that they basically owned it (and they did, literally, own that face). As a professional, when I wanted to spec a font for a design project, and tested Apple Garamond, I had to be able to answer the question "does the use of this font say 'we wish we were Apple'?" Only if the answer was 'no', and the font was right on all the rest of the criteria, could I use it. I almost never did.A few years later, I discovered a font called Stone Print.Look at that!! I thought. It's a beautiful narrow serif face, with great professional personality, and it's not Apple Garamond! I fell in love with it, and at the same time, instantly knew I would never use it for anything else but my own personal stuff. My resume. My correspondence. Over the demands and threats of my grad school, I typeset my thesis in Stone Print and turned it in that way. That's my font, baby. None of my professional projects get to use it. I'm possessive about a handful of other fonts in the same way.Sometimes a font's established use really gets in the way of my wanting to use it, and makes it frustrating. A good example is a font called Gotham.Gotham is an amazing contemporary (2000) face. So modern, so strong, so accessible and welcoming, yet still confident and secure. Beautiful like Helvetica but definitely not Helvetica. I would love to use Gotham a lot more, but...That's a problem. Barack Obama's campaign used Gotham so extensively in 2008 and 2012 that the font became inextricably linked to him, like Apple Garamond blazes "Apple" even when it's not talking about computers. Gotham is the Obama Font, here in the US at least, so unless my target demographic is known to favor the guy, I have to avoid this font if I want to avoid the association.As a designer, you are (or should be) always paying attention to design in your environment and media. If you notice a cool typeface in something, like a movie poster or a billboard, see if you can track it down later using Google searches or WhatTheFont, so you can add it to your arsenal for future use. And be conscious of trends. In the 1990s, a font called Officina Sans was quite popular. It was used everywhere someone wanted to project "contemporary office chic".Today, I can't use it at all. It's worn out... it only projects "we think it's still the 90s." You can't pick up things like that if you aren't paying attention to the design world around you.Here's a fantastic and lighthearted primer on how to choose fonts. This is also a great jumping-off point for beginning graphic artists who don't know many fonts by name, and want to broaden their font horizons.So You Need A TypefaceAnd here is a brilliant article about fonts to avoid. It's long, but anyone serious about learning font usage (and misusage) should give it a read. (And note that while the article mentions Comic Sans, that typeface does not appear in the list.)The 8 Worst Fonts In The WorldIf you are looking for new, fresh typefaces and want to peek at the cutting edge once in a while, you should sign up for MyFonts email newsletters (no, I don't work for them in any way). I get a lot of bulk email every day (most of it is just spam) but when a MyFonts thing shows up, I stop and read it. They are excellent. And I've discovered some amazingly great typefaces through their Rising Stars one.MyFonts NewslettersFinally, here's the tool I use to manage my font libraries. As you can probably guess, I have quite a few fonts on tap.FontExplorer X Pro*Friz Quadrata** It bums me out that I can't seem to find that massive font poster anywhere. I know it was by Letraset, it just listed font after font after font, and right square in the middle of this sea of font names it had this great stone tablet with carved lettering, which was one of the foundational sources of the Trajan face. Surrounding the stone tablet, the fonts were all laid out like this:They went from Aachen to Zapf Dingbats. It was so awesome. And huge... easily 5' across, 3-4' tall. If anyone happens to know where I might get my hands on this, I'd pay cash money to acquire one again.

TL; DRGiven that you have really good CGPA and have applied in a big number of companies with no positive results - it's very likely you are doing the fundamental mistake : Poor presentation of yourself.The other reason is just a bad luck (which is probably a low probability)The one thing you must remember about job hunt is: It's you selling your skills.This happens in two phases:Résumé/CV is your 30 sec 1-2 page ad: This attracts or repel a potential employer to go furtherInterview(s) : This is your short demo / trial of what of you are capable of and how you can fit into the organisation.It's just like buying a car / electronic gadget: You get attracted to the ad - then go for a demo and when satisfied you pay out the cash to get it.Just think of this process being at other end: You and your skills are the car/ gadget and the employer is out there to buy a good one for his/her org.--- Long answer --While there are many great answers here ( I didn't read all of them) , most of them seem to diverge your attention to start your company, increase your network , be patient and do self projects.All the above advice is great and sensible. However, I would like to assume a fundamental flaw in your job application approach and try to solve the same.You have 3.5 / 4 CGPA : Indicates you are pretty good with your subjects. I can safely assume you are technically strong too (if not a super-star, at least on par with the engineering grad herd)You have applied with 35-40 companies. From this I can't infer what you exactly mean when you say "they rejected your application".Very likely there are two possibilities that could have happened. Each with its own set of solution. Let's break it down.1. You did't get any interviews scheduled (or fairly low number among those 35-40 companies).2. You got most of the interviews scheduled with the companies but it didn't convert into the next phase of interview / hiring.Case 1: Your job application didn't result in an interviewThere are two widely possible reasons for thisa> You have not written your résumé / CV properly -- > will discuss this in a while. keep reading.b> You have not submitted your résumé/ CV through proper channel. Most of big companies job portal is so full of applicants - it takes too long to trickle down to actual engineering team for an interview consideration. You would be really lucky to have got an interview scheduled through a job portal of a big company. Instead you should apply through personal network, direct messaging to HRs / managers of companies on LinkedIn, through recruiting agencies - all of these solution is well covered in many of the answers.Case 2: You did go through interview, but it didn't convert into next steps.Now - both Case 1.a and Case 2 are related to the same problem: Poor presentation skills.I have seen quite a number of really good engineers who had made very poor résumé/CV and/or didn't prepare enough for an interview.The one thing you must remember about job hunt is: It's you selling your skills.This happens in two phases:Résumé/CV is your 30 sec 1-2 page ad: This attracts or repel a potential employer to go furtherInterview(s) : This is your short demo / trial of what of you are capable of and how you can fit into the organisation.Neither résumé nor interview guarantees you would be a good fit in an org.It's just like buying a car / electronic gadget: You get attracted to the car - you go for a test drive - like it and pay out cash / loan it. But later you might find it unfit for your use or you may really like it - that's a different story.If case 1.a is the majority of cases with your application :--> you really need to look into your résumé / CV before applying any further. Stop whatever work you have, spend a couple days to refine your résumé. You can Google about résumé writing tips. One of good one with example résumé isExamples Of Good Resumes That Get JobsMy own tips (which I have learned from various sites, people and experience), My résumé (in case you find it interesting) Anshul_Ranjan_Resume.pdf - Google Drive> Remember: write it like it's a 30 sec text ad - in a newspaper. That 30 secs would compel or repel the résumé reader for the next step. Best practices say keep your résumé to 1 page (at max 2 page).> Don't waste real estate of a page: Don't use too big fonts, don't have too much white space at the cost of increased page count.> At the same time - think about aesthetic appearance of your résumé too. Untidy, ugly font, ugly use of whitespaces simply repels. You definitely don't like to know the details of an ugly looking ad in a newspaper - do you ? . As a tip - a consistent simple layout usually is good.> Highlight most impactful aspects about yourself early.>> Your name, contact (email, phone) number should be readily accessible : Put it at top of the page. At the same time - don't give away too much space in your contact info>> A short and brief section about your education background - highlight your college, CGPA, discipline>> A short and brief section about your skill set: This will be really important as many recruiting agencies and actual recruiters too use this to quickly filter out candidates. Highlight relevant technologies, skills you know (programming languages, operating systems, software tools and frameworks etc.)>> A good length section describing your real world experience: Projects, industrial experiences (internship, work history etc). This should be in reverse chronological order OR in order of significance of work/project (highest rated early).A good way to write project/work history is : (<place,title,duration> , <1 line summary of your role in the project>, <bullet points with first couple of bullets providing summary of project and it's importance> , <another couple of bullets summarizing your contribution and impact on the project>)This is the section actual recruiting manager/ engineers really read.This is also the section where most of 30 secs will be spent.This is also the section where many people make the fundamental mistake too:You wrote too much of a text with no clear point being driven ? You wrote too much about project but nothing about your contribution and impact on the project. You have written too little about project. You have used too much of non-industry-wide-standard acronyms and jargons. You have written in very poor English (or whatever language is the mainstream where you are applying for a job). You have too many spelling mistakes, grammatical errors - that is a big big repellent.>> Finally if you have page space left , highlight other things about you like interests, hobbies, relevant courses you might have takenFor Case 2: Failing to convert an interview into next stepsThis is somewhat more complex than writing a résumé/CV. There could be so many factors that can go wrong here. But still there are some basic guidelines which would go in your favor on an average (35-40 is a big number! Things would definitely go in your favor if you follow the guidelines)> Do the homework: read up about the companies' vision, mission and product pages. If you have time - dig up more information on both business and technologies> At companies: profit and business matters and takes highest precedence. It may be an engineering driven company or it may be an engineering supported company. Either way , business matters, profit matters - that's how the company is going to pay your salary (fat ones too)> The above two steps will lead you into answering the interview questions with more relevance.For example: if the interviewer asks "How do you build a file server ?"You can answer technically as : "We add a set of server nodes, store file on it, have some file name -> location database / lookup mechanism"OR you can answer technically with business in mind by asking few questions (remember few questions: don't bombard the interviewer with so many questions that s/he feels you are interviewing him/her)" What's the purpose of this file server ? What is the user base and traffic flow are we looking at ? Are we allowed to use some off the shelf service (say google cloud , amazon services, rackspace etc.) ? Or do you want me design it from scratch using basic component" --> these would give you more clarity on how you should solve the problem.Similar approach should be used for simpler questions( basic code implementation , algorithm) if the input is not clearly defined (many times this happens). You got to assume and validate your assumptions with the interviewer.Say for example, the company is primarily an internet / web tech company: you can think of the problems in that relevance - scale will be very important here. Instead if it's a desktop software company, importance will be shifted more on performance / machine - software boot time, interaction smoothness, load on CPU would take high precedence. Scale probably will not matter as single machine softwares are limited by the machine and designed for single user use.The same file server example can be addressed in a different way depending on if it's a large website problem or if it's a localized set of people who need to share files quickly.Again always remember: companies run for profit - if you can discuss your solution to include the cost of implementation factor, it will win your interviewer's attention and likely convert into a favorable decision.> Interviewers look for the way you approach a problem. Unless it's a very basic problem - not getting a perfect answer is usually fine up-to certain extent. Talk aloud about what you are thinking in your head- this might take some practice. This helps the interviewer track your approach to the solution and might provide you hints as well to arrive at a correct solution.Staring blankly at the interviewer while you are thinking of a solution is just rude, indicates that you might not be clear of what you want to do and above all - you are not a team player and you don't want to share what you think or how you solve the problem.> Companies run on the team: individuals are important but for long survival, companies need good teams. You will be a part of a team. If you can show / indicate with your behavior and talk that you are a good team player - you have higher chances of getting hired.> Be polite, jovial. Ultimately interviewers are humans and you would be working with humans. Being polite, jovial and watchful of others gives a positive vibe about you. That also increases chances of getting into the company.> While you are being interviewed, you should also assess your potential employer. At the end you don't want to get into a team which you don't find at all exciting and boring or unmatched to your expectations.> Finally if you reach a round with the HR - that's where you negotiate salary - not before that. Tech interviews stay technical - no salary negotiation there. With the HR - be courteous and relevant. You don't say you like Pepsi when you are with Coca Cola's HR. Be honest about your expectations (career, money, skill set, contribution to the company you would make, why you would be a good employee). This might result in you getting no job but more likely you would get a job.> Be prepared for common questions (the HR ones, it gets repeated at tech rounds too).All of the above is in addition to being technically and fundamentally strong - which you seem to be already.

Most people have done a phenomenal job answering your question, but here’s my two cents.As a freshman, I had no clue what I wanted to do or where I wanted to go with CS. To make matters worse, I had no significant dev experience on my resume and a quite mediocre GPA. The most rational and beneficial course of action for me was to get exposure to as many things as I could at the same time. I hounded Craigslist job postings in my area looking for companies that needed junior developers and sent them my resume. I played the cold email game and got a few offers for part time (basically contracting) internships, and accepted all of them. That summer, I did iOS dev, product management, QA, a bit of UI/UX, and a little computer science tutoring. This made for significant gains in breadth over depth, which is not great for an engineer in the long run, but invaluable to a freshman starting out.Most people don’t realize that a Top N internship isn’t really a solution to all problems. It’ll help you get an interview next summer, but so will any other decent experience that you learned from and made an impact with.But, if you are gunning for a competitive company (and you absolutely should), here’s the secret sauce.Disclaimer: There isn’t a formula in the world that will guarantee freshmen (or anyone) internships.You have to do 2 things: get interviews and get offers.To get interviews:Apply to Freshman focused internships. The big, well known SV companies have specific programs targeted towards nurturing freshman and helping them build their skills. This will always lead to better results than applying for stuff that third-years are looking at.Open source is awesome, but not ideal for beginners. If you’re up for the challenge, contribute to a Linux kernel. Check out Elementary OS if you want an example of a global team dedicated to an awesome mission that can use your help.Apply to as many things as you can. Broaden your horizons, and keep an open mind.Start a tech blog. Write about stuff you like. Ideally, this’ll be stuff related to the kinds of jobs you’re looking for. Then bring it up with recruiters and hiring managers.HACKATHONS. I networked the hell out of hackathons just by talking to all the judges and sponsors that came. Get a few business cards, write a few emails, and start a few conversations. You’d be surprised where a “Hey, my name is _______” with the right person can lead at a hackathon. (This is also true for life in general).Career Fairs. Don’t put your grad year on your resume and don’t make it part of your elevator pitch/introduction. If a recruiter asks, don’t lie and be honest. The goal is to wow them with experience and passion so that they don’t ask unless its company policy.Referrals. A referral guarantees your resume a look, and as a freshman, this is all you can really ask for in a world where most recruiters will see “1st year” and toss the CV in the shredder.To get offers:Coding interviews are a game. To play the game, you have to know the rules. The rules are:Pick a coding language. Python if you’re new to the grind, but interviewers are mostly agnostic.Become really familiar with shortcuts and neat things in that language.Spend your free time on LeetCode, CareerCup, and Hackerrank.See Step 3, until you get an offer.