This position provides dedicated documentation, organization, and artifact production support to the Business Systems Analysis function. Working under the direction of the BSA Lead, this role owns the structured outputs that keep projects moving—meeting minutes, sprint presentation decks, JIRA ticket maintenance, user-facing documentation, and process diagrams. The role operates with increasing independence on defined deliverables while receiving guidance on priorities and scope from senior BSAs. This is an entry-level position that does not require prior experience in business analysis; success depends on precision, clear writing, and a strong instinct for organizing information. The position reports to the BSA Lead / Product Operations.

Responsibilities:

• Draft and distribute structured meeting minutes after client and internal meetings, capturing decisions, open items, owners, and next steps in a format that requires no follow-up to interpret
• Prepare sprint presentation decks using provided content and templates, ensuring visual consistency and readiness for BSA review before team walkthroughs
• Create and maintain process flow diagrams, hierarchy charts, and visual aids that translate complex logic into formats developers and QA can act on without additional explanation
• Write and update user guides and feature summaries for new functionality, written for non-technical readers but accurate enough for technical audiences
• Maintain JIRA tickets by updating acceptance criteria, adding clarification comments, linking related items, and flagging tickets where requirements have drifted from their documented state
• Tag and identify tickets with UI/UX impact based on requirement content, ensuring design reviews are triggered at the appropriate time without BSA prompting
• Review QA test scenarios for completeness, confirming that scenarios map to documented requirements and flagging gaps before testing begins
• Support sprint ceremonies (estimation, planning, readiness reviews) by taking structured notes, tracking open items, and ensuring relevant documentation is available before and after each session
• Prepare context documents for UI/UX meetings so designers have the business logic and requirement background they need before sessions begin
• Assist the data team with structured data pulls and analysis support, interpreting outputs in business terms and documenting findings in clear written summaries
• Respond to QA queries with documented requirement information, reducing the volume of ad-hoc interruptions to senior BSAs during active development cycles

Technical Qualifications:

• Working Knowledge of how to structure and organize business documents with clear sections, logical navigation, and cross-references using tools such as Confluence, Google Docs, or MS Word
• Understanding of basic requirements documentation concepts such as use cases, user stories, and acceptance criteria
• Basic understanding of the software development lifecycle (SDLC) and Agile or sprint-based methodologies
• Familiarity with project management and ticketing tools such as JIRA, including how to create, update, and maintain work items
• Familiarity with diagramming or visual documentation tools such as Lucid chart, Visio, Miro, or Figma for creating process flows and hierarchy charts
• Familiarity with AI tools for documentation tasks, including prompt construction, output evaluation, and quality judgment
• Exposure to SaaS product environments or web and mobile application concepts is a plus

Personal Skills:

• Natural inclination to organize, structure, and clarify messy or unstructured information—discomfort with disorder is an asset in this role
• Precision and accuracy as a default—treats a misquoted number or a wrong ticket status as a real error, not a minor slip, and checks work before sending
• Clear, concise written communication—can produce high-density summaries without redundancy or filler
• Ability to quickly comprehend and synthesize information from multiple sources into a coherent, navigable format at varying levels of detail
• Proactive follow-through—asks one clarifying question to unblock rather than waiting passively, flags blockers early, and delivers on time without reminders
• Contextual awareness—understands not just what was said but why it matters, and reflects that understanding in documentation so readers do not need the original source
• Eagerness to learn and adapt to new tools, processes, and domains quickly

Education and Work Experience:

• Background in CS, IT, Business, Communications, or a related discipline is preferred
• 0–2 years of relevant experience in documentation, business analysis support, or a related role; internship or academic project experience is considered