Position Details
Business Analyst
Business Analyst
Contract RemoteWe're looking for a thorough, adaptable, and analytically sharp Business Analyst to bridge the gap between what clients need and what our technical teams build. This role is ideal for someone who is comfortable sitting in ambiguous conversations with non-technical stakeholders, asking the right questions, and producing clear, structured documentation that technical teams can actually work from. You'll need to hold context across multiple active engagements and keep the work grounded in what clients are actually trying to accomplish.
| Engagement | Flexible scheduling with up to 15h per week |
| Compensation | $55-$70/h CAD |
| Duration | Initial 3–6 months, with strong likelihood of extension |
| Availability Requirements | Consistent overlap with Eastern Time (ET) business hours |
| Communication | Fluent English (spoken and written) |
About the Role
As our Business Analyst, you'll lead discovery and requirements-gathering work across client engagements, translating business problems — often vague, shifting, or incompletely defined — into clear specifications that technical teams can implement against. You'll work closely with both client stakeholders and internal technical contributors, and you'll need to be equally credible in both conversations. This is not a passive documentation role; it requires curiosity, persistence, and the ability to push back constructively when a problem isn't well enough defined to move forward.
What You'll Do
Lead discovery sessions with client stakeholders to understand business goals, pain points, and current-state processes
Translate business requirements into clear, structured documentation — user stories, process flows, functional specs, or whatever format best serves the engagement
Identify gaps, inconsistencies, and unstated assumptions in client requests before they become handoff problems
Work directly with technical teams to ensure specifications are understood and implementable
Document current-state workflows and map them against proposed changes or new system capabilities
Manage requirements across multiple simultaneous client engagements, keeping context clean and documentation current
Support QA and UAT by clarifying intent and verifying that delivered work meets the original requirements
Flag ambiguity, scope expansion, or conflicting stakeholder expectations early and clearly
What We're Looking For
3+ years of experience in a business analyst, systems analyst, or requirements-focused role
Strong documentation skills — you produce specs, process maps, and written summaries that are clear without being over-engineered
Proven ability to facilitate discovery conversations with non-technical stakeholders and extract actionable requirements
Comfort working across multiple engagements simultaneously, with different clients, contexts, and technical stacks
Experience handing off specifications to development or technical teams, and following through to ensure fidelity
Solid written communication and the ability to work effectively in an async/remote environment
Familiarity with process documentation tools or notation (e.g., flow diagrams, swimlane charts, or similar)
Nice to Have
Background working in a consulting, agency, or multi-client environment
Exposure to systems integration, workflow automation, or data/reporting projects
Experience with tools such as Confluence, Notion, Lucidchart, Miro, Jira, or similar
Familiarity with Agile or iterative delivery environments
Comfort reading or interpreting technical documentation, even without deep technical expertise
Who You Are
You're intellectually curious, structured in how you think, and patient with people who don't yet know how to articulate what they need. You ask good questions, listen carefully, and document with precision — not bureaucracy. You understand that your job is to reduce friction between clients and builders, and you take that responsibility seriously. You're comfortable saying "that's not defined clearly enough yet" and doing the work to fix it before it becomes someone else's problem downstream.