For business analysts, this question tests whether you know how your work lands with developers and stakeholders. A fresher can show sharp questioning from an internship, and pair it with a writing or communication weakness that has a visible fix, such as shorter specifications that draw fewer clarifications.
My strength is asking the question that turns a vague request into a measurable one. During my internship, a requirement simply said “approve claims faster”. I asked the operations team for the current average approval time and the target they had in mind, which changed the story into something the team could design and test. My weakness is that I write too much. My mentor told me developers were skimming my long specifications and missing key rules. Now I use tables, bullet points and acceptance criteria, and I move background notes into an appendix. My last specification was half the length of my first one, and it drew far fewer clarification questions in sprint planning.
Being detail-oriented is unproven and trusting people is vague. The rewrite gives a real conflict caught early and a workshop habit that changed how stakeholders treat the analyst.
For students, interns and your first job.
My strength is asking the question that turns a vague request into a measurable one. During my internship, a requirement simply said “approve claims faster”. I asked the operations team for the current average approval time and the target they had in mind, which changed the story into something the team could design and test. My weakness is that I write too much. My mentor told me developers were skimming my long specifications and missing key rules. Now I use tables, bullet points and acceptance criteria, and I move background notes into an appendix. My last specification was half the length of my first one, and it drew far fewer clarification questions in sprint planning.
One strength I have is learning a new domain quickly. In my postgraduate course I worked on projects in retail, healthcare and logistics, and each time I got comfortable with the basics within a week by reading process manuals and talking to the staff who actually did the work. My weakness is speaking up in large meetings. In my internship I once stayed silent while a stakeholder described a step I knew was wrong, and it surfaced later in testing. Now I prepare two or three questions before every meeting and make sure I raise at least one. My manager noticed the change within a month and started asking me to lead the recap at the end of workshops.
For roughly 3 to 8 years in the field.
My strength is checking requirements against real data before they reach developers. I write SQL queries to see whether a proposed rule or report is even possible. Once I found that a dashboard the business wanted was based on a table nobody had updated for months, which saved weeks of wasted development. My weakness is that I used to drift into solution design and suggest technical approaches in requirement meetings, which annoyed our architects. I now keep my documents focused on what the business needs and why, and I offer design ideas only when the architect asks. Our last two projects had much smoother hand-offs, and the lead architect now invites me to design reviews.
A strength I bring is running workshops that end with decisions. I can manage sessions with ten or twelve stakeholders from operations, finance and IT, keep the discussion on track and close with clear owners and dates. My weakness was that I used to accept every requirement people raised without questioning its value, which made our scope swell on a lending project. Now I ask each stakeholder to explain the business impact of their request and help the group rank them with a simple must, should and could list. On my last project we removed about a third of the original wish list in agreement with the business, and we still met the release goal.
For 10+ years, specialists and leaders.
My strength is developing other analysts. Over the last six years I’ve trained more than fifteen junior analysts in requirement gathering, documentation and stakeholder handling, and several of them now lead analysis on their own programmes. My weakness is that I found it hard to stop reviewing every document personally. It slowed my team down and kept me away from strategic work with business heads. I now assign senior analysts as reviewers for their own streams and only check high-risk documents, such as regulatory changes. Review turnaround has improved, my senior analysts have grown in confidence, and I finally have time to join portfolio planning meetings.
One strength I have is explaining complex change simply. I can take a messy system migration and present it to the leadership team in four slides that show options, costs and risks clearly enough for them to decide in one meeting. My weakness has been impatience with slow approvals. I used to push sponsors hard near deadlines, which created friction with a few senior people. I now map the approval path at the start of every programme, involve decision-makers earlier and send them short updates every fortnight, so nothing arrives as a surprise. Our most recent programme cleared its design approvals well ahead of plan, and one sponsor asked me to use the same approach elsewhere.
Written by the DigitalCVMaker team for business analysts applying in India. Every example is original — none is copied from a real person’s profile — and each is built around what employers and clients in this field look for: the role, a specialism, and proof you can back up. We revise the page when that changes; the date at the top shows the last update.
These are examples to adapt, not real people. Swap in your own numbers, specialisation, city and achievements — it only works when every word is true for you.
Yes, as long as you show steps you are taking, such as learning SQL to validate data or sitting with developers during design. Analysts are not expected to code, but they should understand enough to judge feasibility.
Avoid anything that suggests poor listening, careless documentation or avoiding stakeholders, since these are the core of the job. Choose something like public speaking, estimating analysis effort or over-detailed writing, and show the fix.
Add your headline, summary and skills to a personal website with your photo, work and contact form — free to start.
● Live in 5 minutes · free to start · no auto-renew
One strength I have is explaining complex change simply. I can take a messy system migration and present it to the leadership team in four slides that show options, costs and risks clearly enough for them to decide in one meeting. My weakness has been impatience with slow approvals. I used to push sponsors hard near deadlines, which created friction with a few senior people. I now map the approval path at the start of every programme, involve decision-makers earlier and send them short updates every fortnight, so nothing arrives as a surprise. Our most recent programme cleared its design approvals well ahead of plan, and one sponsor asked me to use the same approach elsewhere.