Resume and Portfolio
Resume and Portfolio is a public community on OnJob. Feedback on resumes, portfolios and profiles - what recruiters actually read in the first thirty seconds.
What are people discussing in Resume and Portfolio?
- Sandeep Rao
The single highest-return edit: rewrite every bullet so it ends in an outcome
"Responsible for the payments service" says nothing. "Rebuilt the payments retry path, cutting failed transactions from 4 percent to 0.6 percent" says what you can do. If you cann…
- Neha Sharma
Welcome to Resume and Portfolio
Post your resume for review with the role you are targeting attached. A resume can only be judged against a target - the same document can be strong for one role and weak for anot…
- Divya Nair
When changing fields, lead the resume with a skills-based summary rather than the chronology
The reader's first question is "why is this person applying", and the chronology answers it in the wrong order. State the transferable core in the summary, then let the history fo…
- Vikram Singh
List skills you would be comfortable being interviewed on, and nothing else
A long inventory that includes everything you have touched once dilutes the things you are genuinely good at, and it invites a question you cannot answer. If it helps, split into …
- Neha Sharma
On employment gaps: state them plainly, in one line, and move on
Caregiving, study, illness, redundancy, a business that did not work - all of these are ordinary. A short factual note closes the question. An unexplained eighteen-month hole invi…
- Aditya Joshi
The summary at the top is the only section you should rewrite for each application
Three lines: what you are, the two or three things you are strongest at that this role needs, and what you are looking for. That is the paragraph a recruiter reads before deciding…
- Sandeep Rao
Format rules that still hold
One page for under eight years of experience, two beyond that. No photo unless the market you are applying to expects one. No skill bar charts - nobody knows what 80 percent of Py…
- Arjun Mehta
A public repository is judged on its README as much as its code
Someone landing on it should understand in thirty seconds what it does, why it exists, and how to run it. A project with clean code and no explanation looks abandoned. One with a …
- Priya Raghavan
Cutting is harder than writing and matters more
Your roles from more than ten years ago need one line each, not five bullets. Early jobs unrelated to your target role can be a single grouped line. Everything you remove makes wh…
- Pooja Desai
Your profile and your resume should agree with each other
Different dates, different titles, or a role missing from one of them is a routine thing recruiters notice and ask about, and it turns an easy screen into an awkward one. Update b…
- Priya Raghavan
Applicant tracking systems parse text, and they parse it badly when the layout fights them
Two columns, text inside images, tables, and headers stuffed into the page margin are the usual culprits. A single-column document with ordinary headings survives every parser. Sa…
- Karthik Reddy
A portfolio does not need many projects. It needs two or three that you can talk about for twenty minutes each
For every project, write down what the problem was, what you chose to build, and what you would do differently now. That last part is what separates a portfolio from a gallery.
- Divya Nair
For each portfolio project, write the case study even if nobody reads it
Problem, constraints, what you chose, what you rejected, and what the outcome was. The act of writing it is what makes you able to speak about the project fluently under questioni…
- Vikram Singh
Line up references before you need them, and tell them what the role is
A former manager who gets a call with no warning gives a vaguer reference than one who knew it was coming and knew which skills to speak to. Two or three people who can speak spec…