3 ms·

Expand on the line items under work experience and reduce the skills/interest. You need info on what you did during the position. > Web application development

• nikkwong 9y ago
  Interesting—my general belief always was that those kind of details would be disclosed later in the interview process (as to not 'crowd out' the resume). But that makes sense–I guess I'll have to give that belief a revisiting. Thank you!
  • znpy 9y ago
    Think about it: you are explicitly saying what you are using on the front-end (React, Vue) but you skip doing the same for the back-end. That does not make sense.
  • lykr0n 9y ago
    For Resumes, this is what I've been told by multiple people. - One page for cold or warm leads, such as whose hiring threads or online application. Two pages at most, for familiar leads (such as 2nd day interviews), such as "hey, we're looking for someone like you, if you shoot me your resume I can pass it on". The difference here is detail on positions. - Keep education short and to the point. School, degree, program, and anything of note. GPA if it matters (say Business and Accounting) or is of note (3.5+) - Highlight competent skills. Angular JS implies Javascript. Only list stuff that you are fine jumping into doing. I can do networking, but at a Jr. level. It's not on highlighted on my resume. Nobody cares about something you can kinda do well. You're not being hired on that. - Buzzwords, in moderation, are your friend. People, myself included, will scan until something pops out. - Focus on work experience. Describe what you did at the role. Describe your responsibilities. Describe your performance and accomplishments. Describe why you remained employed. Think of this as the 30 seconds to pickup someone at a bar. Give information, but leave room for them to be able to ask you about yourself. This is what you will be interviewed off of. When you are talking to someone- they have seen your resume and think you can work for them- they are trying to figure out if you have what they need. If your resume doesn't appear to be what they are looking for, they will move on. "Java?" "API Development?" "Spring Framework?" "Increased application performance by 20% in some cases while rewriting ORM" will not only be impressive, but the person reading will want to know more, like how and what you did. The previous statement shows an impressive accomplishment, while implying you know what you are doing and you can bring it to them, and also brings a tangible number. Follow ups could be, "What did you do to increase performance?" "How did you rewrite the ORM?" "How did you measure the performance increase?" "What cases did you see a performance increase?" "Build a Java API" leaves too much to question and doesn't tell much about what you did. There is too much to follow up on, and there is a good chance that they won't waste the effort. A better line would be "Implemented a high performance Java API using the Spring framework on top of an existing application for internal customers." That gives more information, some details, and leaves room for the interviewer to ask questions.