Probridge- Technical Business Systems Analyst

Trellance Cooperative Holdings, Inc. is a company that evolved from Trellance’s Talent Line of Solutions, providing organizations with access to skilled technology and finance professionals. The Technical Business Systems Analyst (TBSA) serves as a client advocate, managing project delivery and translating business requirements into testable specifications while ensuring alignment between business, UX, and engineering teams.

Responsibilities:

• Develop an understanding of the client’s business model, solutions offered, and program lifecycle in order to effectively translate requirements and provide meaningful recommendations
• Provide proactive recommendations on system behavior, workflows, and user experience based on industry best practices
• Plan, facilitate, and document structured working sessions with client stakeholders, advisors, and subject matter experts with the goal to align on requirements and make decisions
• Surface assumptions, dependencies, and decision points during sessions
• Distribute session summaries with decisions, open items, and owners within one business day
• Author and maintain project-level requirements documents that define scope, business rules, and functional specifications aligned to waterfall phase gates and client sign-off milestones, while ensuring that all documentation is purpose-driven and right-sized for its audience
• Decompose project-level requirements into page-component user stories—each scoped to a discrete UI element (a form section, data table, navigation step, or workflow action within a page)—so that every story is independently implementable in a single sprint
• Write acceptance criteria for each page-component story in a Given/When/Then or equivalent format so they are directly testable by development and QA
• Maintain traceability from project-level requirement to page-component story to UX design artifact, ensuring no logic is lost in decomposition
• Flag conflicting, incomplete, or cross-cutting requirements before they reach development; coordinate with UX when a page-component story spans multiple design states
• Own the decision log: record every decision within 24 hours of the session where it was made
• Track client feedback through its full lifecycle; escalate any item that remains unresolved for more than five business days
• Communicate outcomes and rationale back to stakeholders in writing; do not rely on verbal confirmation alone
• Incorporate decisions directly into the relevant requirements and user stories so documented intent and implementation artifacts remain fully aligned
• Review wireframes and prototypes (e.g., in Figma) against documented requirements before client walkthroughs
• Convert UX decisions into updated functional requirements or acceptance criteria
• Consolidate scattered design-tool feedback into the central feedback tracker
• Validate data fields and database sources referenced in page-component stories with engineering; clarify display rules, validation logic, and data-freshness expectations where sync timing matters
• Document conditional logic, business rules, and workflow branching in a format engineering can implement directly (decision tables, pseudocode, or flowcharts)
• Identify integration points with internal or third-party systems and document expected inputs, outputs, and error handling
• Serve as the functional reference during development and testing, answer developer and QA questions with documented rationale, not ad hoc opinion
• Own and maintain a centralized, structured source of truth for all requirements, feedback, decisions, changes, and approved designs – organized in a way that allows stakeholders to easily reference prior discussions, options considered, and final decisions (by page and functionality)
• Ensure only one active version of working documents is in circulation at any time; manage updates through controlled iterations to avoid mid-cycle changes and rework
• Ensure materials are complete and decision-ready before scheduling review meetings
• Reduce meeting dependency by producing documentation clear enough to replace status calls where possible

Requirements:

• Minimum Bachelor's degree with IT related focus, preferably information systems or systems analysis and design with 5–7+ years as a Business Analyst or Technical Business Analyst, with at least 3 years in a client-facing capacity working with senior business or advisory stakeholders OR a High School diploma or equivalent plus 10+ years as a Business Analyst or Technical Business Analyst, with at least 3 years in a client-facing capacity working with senior business or advisory stakeholders
• Demonstrated ability to translate consultative, domain-heavy discussions into structured, testable system requirements
• Hands-on experience with web-based platforms or enterprise portals and data-driven or rules-based applications
• Strong facilitation skills: able to run a room, keep discussions on track, and drive to decisions
• Strong presentation skills with proven ability to interface with senior executives to explain UX and technology design concepts to drive consensus on design and/or functionality decisions
• Proficiency writing acceptance criteria and business rules at the UI page-component level; experience decomposing project-level requirements into granular, sprint-ready user stories
• Experience working in a hybrid SDLC: waterfall-style project planning with agile sprint execution and user-story-driven development
• Domain experience in financial services, executive benefits, life insurance, or advisory platforms
• Background in data mapping and complex business-rule documentation (decision tables, conditional workflows, lifecycle-based logic)
• Experience working with distributed or cross-functional delivery teams across multiple time zones
• Comfort working across collaboration tools (e.g., Jira, Confluence, Figma, Teams) while keeping a single governed source of truth