Skills: Jira, Confluence, Visio, Lucidchart, Balsamiq,
Figma, Excel, Power BI, Tableau, SQL, Python, Agile,
Scrum, Kanban, SAFe, BRD, FRD, User Stories, Use Cases,
BPMN, Wireframes, UAT, Traceability, CBAP, PMP.

Core stack:
• Jira + Confluence (4 yrs) — epics, stories, ACs,
  traceability for a 6-squad programme
• BPMN + Lucidchart — as-is/to-be for 14 processes;
  exception paths covered end-to-end
• BRD/FRD — 22 documents shipped; sign-off from 3
  business owners per release
• SQL — ad-hoc queries on a 40M-row analytics schema
  for metric validation

- Wrote business requirement documents.

- Authored 22 BRDs (avg 20-40 pages) across 6 domains;
  each shipped with a 1-page exec summary and an
  explicit "out of scope" section that cut scope
  clarifications by ~50%.

- Documented business processes.

- Modelled 14 processes in BPMN (as-is + to-be); the
  to-be model removed 3 redundant approval steps and
  cut average cycle time by 18% in the pilot team.

- Worked with data teams.

- Defined 18 metrics with explicit SQL definitions;
  reconciled numbers between the app DB and the
  warehouse monthly; ended a 3-quarter dispute about
  "the real" activation rate.

3 years in customer support, then 2 years as a BA.

Customer-support (3 yrs) → BA (2 yrs) in fintech.
Deep on the onboarding flow I used to support daily;
now own its requirements, ACs, and post-launch metrics.

Objective:
Seeking a Business Analyst role where I can leverage my
requirements-gathering and stakeholder-management skills.

Business Analyst · 4 yrs
Fintech · Jira · BPMN · SQL
Led discovery for a checkout redesign that lifted
conversion 2.1% → 2.4% in 6 weeks; cut sprint rework 40%
by tightening ACs across 3 squads.

Business Analyst — Nimbus Fintech (2022-2024)
- Gathered requirements from stakeholders.
- Wrote user stories and BRDs.
- Worked with developers and QA teams.
- Created wireframes in Balsamiq.
- Used Jira and Confluence.
- Participated in UAT.

Projects
- E-commerce requirements project.
- CRM migration documentation.

Business Analyst — Nimbus Fintech (2022-2024)
- Led discovery for a checkout redesign on a fintech
  onboarding flow (~45k monthly signups); reframed
  "slow checkout" as a 4-step drop-off problem and
  prioritised the 3 highest-loss steps.
- Wrote 120 user stories across 6 epics with Given/
  When/Then ACs; 0 stories reworked for missing scope
  in 3 sprints; cut sprint rework ~40%.
- Authored 22 BRDs (20-40 pages each) with explicit
  out-of-scope sections; scope clarifications cut ~50%.
- Modelled 14 processes in BPMN (as-is + to-be); to-be
  removed 3 approval steps and cut average cycle time
  18% in the pilot team.
- Produced low-fi wireframes in Balsamiq for 3 onboarding
  screens; design iteration cycles 4 → 2.
- Owned UAT for the checkout release; defined 48 test
  scenarios and 12 go/no-go criteria; released with
  0 SEV-1 issues.
- Defined 18 metrics with SQL definitions; reconciled
  app DB vs warehouse monthly and ended a 3-quarter
  dispute about activation rate.

Result: conversion 2.1% → 2.4% (+15% relative) in the
first 6 weeks post-launch.

Projects
- Checkout redesign case study (public write-up with
  redacted BRD + BPMN + ACs) — used as an internal
  onboarding artefact.

Content (1-6):
☐ Tools list is 3-5 items with real use.
☐ One domain named (fintech, health, SaaS, retail).
☐ Every project starts with a problem statement.
☐ Stakeholders named (who you worked with).
☐ One requirements technique named (stories, BRD, BPMN).
☐ Business impact on 2+ bullets.

Artefacts (7-11):
☐ One BRD/FRD mentioned with scope + sign-off.
☐ One wireframe or prototype line.
☐ One BPMN / process model line.
☐ One AC example (format + outcome).
☐ At least one real project (not just process).

Tooling (12-15):
☐ Jira + Confluence with a specific use.
☐ Agile depth (squad size, sprint cadence).
☐ SQL / data literacy line.
☐ One prototyping tool named.

Positioning (16-20):
☐ Stakeholder outcomes named (who decided what).
☐ No bullet copied from a JD.
☐ One career-arc line (if you pivoted in).
☐ Certifications below experience, with context.
☐ Opening line = role + stack + one impact number.
☐ One page for 2-5 years of experience.
☐ Filename: Firstname-Lastname-BA-Resume.pdf