Senior Business Analyst

Svitla Systems Inc. is looking for a Senior Business Analyst for a full-time on-site position (40 hours per week) in New York, USA. Our client is a finance company and an alternative lending platform focused on providing capital access to small and medium-sized businesses.

The office is based in NYC's Financial District in downtown Manhattan. The role requires working on-site Monday through Friday during standard business hours. The interview will happen on-site.

The Senior Business Analyst is the primary driver of discovery, process understanding, and requirements clarity for a software delivery engagement supported by a remote offshore engineering team. This role is accountable for building and maintaining a deep, working understanding of the client’s existing business processes through daily stakeholder conversations, structured walkthroughs, and ongoing validation of assumptions. The Senior Business Analyst translates current-state workflows, sign-off paths, exception handling, and operational dependencies into implementation-ready requirements and documentation that leaves minimal room for interpretation.

Success requires a disciplined approach to eliciting detail, reducing ambiguity, and producing exhaustive written artifacts, including step-by-step guides, process manuals, how-to documentation, and decision logs that enable engineering and QA teams to build and validate functionality with predictability and minimal rework. While project coordination responsibilities may support delivery flow, the core value of this role is senior-level business analysis, process modeling, and documentation rigor that withstands scrutiny from both business stakeholders and technical teams.

REQUIREMENTS

• Extensive experience in a Senior Business Analyst role on software delivery initiatives, with direct ownership of discovery, workflow analysis, and requirements definition.
• Direct experience working with fintech companies, banks, credit bureaus (Experian, TransUnion, Equifax) or third-party credit data providers.
• Strong financial background.
• Demonstrated ability to conduct frequent, high-touch stakeholder engagement and maintain daily communication rhythms that continuously validate understanding of business operations and approvals.
• Proven track record of producing highly detailed documentation, including process guides, operational manuals, step-by-step how-to documentation, and implementation-ready handoff artifacts for engineering teams.
• Strong facilitation skills with the ability to drive meetings to outcomes, resolve ambiguity, manage competing stakeholder priorities, and enforce clarity through structured follow-through.
• Experience working with fully remote software engineering teams, including nearshore and offshore team members, with a strong understanding of what level of specificity is required for accurate distributed execution.
• Experience working in environments with sensitive data, confidentiality constraints, or regulated business processes.
• Strong knowledge of Agile delivery practices, including backlog management, requirements decomposition, sprint readiness, and UAT planning support.
• Experience creating process maps and workflow diagrams using tools such as Visio, Lucidchart, Miro, FigJam, or similar platforms.
• Familiarity with delivery and documentation tooling such as Jira, AWS, DevOps, Confluence, SharePoint, or similar systems.
• Exceptional English communication skills, including the ability to lead structured discussions, ask precise probing questions, and document complex workflows in a way that withstands executive and technical scrutiny.

NICE TO HAVE

• PMI certification or comparable project management training, especially where it supports disciplined scope control and stakeholder governance without diluting the primary Senior Business Analyst function.

RESPONSIBILITIES

• Lead daily stakeholder engagement with the client to understand existing business processes in full depth, including end-to-end workflows, handoffs, approvals, signoff mechanisms, exceptions, edge cases, and operational constraints.
• Facilitate process walkthroughs, working sessions, and on-site interviews that uncover how work is performed today, why those steps exist, and what risks or compliance factors shape the workflow.
• Capture and document current state processes with extreme precision, including role-based responsibilities, triggers, inputs, outputs, decision points, escalation paths, SLAs, and dependencies on people, systems, and external vendors.
• Define future state workflows in collaboration with stakeholders, ensuring the target operating model is realistic, testable, and aligned with delivery constraints and sequencing.
• Produce high-quality analysis artifacts, including business requirements, functional requirements, user stories, acceptance criteria, workflow diagrams, process narratives, data definitions, exception catalogs, and end-to-end traceability between business intent and delivered functionality.
• Maintain an authoritative documentation set that is continuously updated as learning occurs, including detailed guides, training materials, how-to manuals, playbooks, SOP-style documentation, and UAT reference materials.
• Drive formal signoff processes with the client by establishing clear approval steps, managing review cycles, collecting written confirmations, and ensuring requirements baselines are controlled and auditable.
• Translate business intent into unambiguous, implementation-ready requirements for a remote engineering team, ensuring stories are testable, edge cases are captured, and acceptance criteria are measurable.
• Serve as the primary clarifier for the engineering and QA teams by answering questions quickly, validating interpretations with stakeholders, and preventing rework caused by missing or vague requirements.
• Partner with delivery leadership to support sprint readiness through backlog refinement, scope boundary clarification, dependency identification, and release planning inputs, while keeping the requirements baseline stable and well governed.
• Maintain decision logs and change-impact documentation that clearly explain what changed, why it changed, who approved it, and how it affects scope, timeline, and downstream workflows.
• Provide precise, professional written follow-ups after stakeholder discussions that document outcomes, open questions, action items, and next steps, ensuring nothing is left untracked.