BSA Product Development

Business Systems Analyst, Product Development

 

About us:  At Spin, recruitment is about more than filling roles;  it’s about creating real human connections. We partner with leading U.S. companies to help them hire exceptional talent through a true direct-hire process, ensuring candidates join our clients’ teams directly while we support them throughout the journey.

About our partner: Join a team that operates at the intersection of AI and modern marketing, building a smarter, more agile operating model for go-to-market teams. With a growing portfolio of companies, they empower organizations to make better decisions earlier, connect audience intelligence to execution, and move faster with greater clarity.

As the company continues to scale, they are building a dynamic, always-on content engine that powers the full brand narrative—spanning executive voice, social, web, PR, events, sales enablement, investor communications, and portfolio storytelling.

About the role: This is an opportunity to join a fast-growing, high-impact environment as a Business Systems Analyst, Product Development. You own the translation of business and product intent into clear, build-ready specifications that engineering can execute against without guessing. You sit at the seam between product, engineering, and the operating-company stakeholders who actually have the problem, and your job is to make sure the thing that gets built is the thing that was meant. 

When a requirement you wrote ships, no one should have had to come back to you mid-sprint to ask what a given screen, rule, or edge case was supposed to do. The ambiguity gets resolved on paper, before code, by you.

What You'll Do

• Run discovery and intake. Turn vague, conflicting, or half-formed asks from stakeholders into validated, scoped requirements.


• Write the specs: PRDs, user stories, acceptance criteria, business rules, process and data flows, and the non-functional requirements (performance, security, reliability) that usually get skipped until they hurt.


• Make assumptions explicit. Name dependencies, edge cases, and the load-bearing decisions a requirement rests on — rather than burying them.


• Partner with pod leads to scope, sequence, and size work, and feed the inputs that drive prioritization.


• Maintain traceability from business need → requirement → build → acceptance, so changes can be reasoned about instead of rediscovered.


• Write testable acceptance criteria and support QA/UAT through to sign-off.


• Keep the backlog build-ready: groom, clarify, and close gaps ahead of sprint planning so engineering time isn't spent on archaeology.


• Flag conflicts and trade-offs early and directly, to whoever needs to hear them.

What You Bring

• 3–5+ years as a Business Systems Analyst, Product Analyst, or equivalent on a software product development team.


• A real track record of writing requirements that engineering teams built from — be ready to walk through examples.


• Fluency with user stories and acceptance criteria; comfort with Given/When/Then or equivalent structured formats.


• Enough technical literacy to read a data schema, understand how APIs and integrations work conceptually, and write basic SQL to validate your own assumptions.


• Working command of the toolchain: an issue tracker (Jira, Linear), a docs/wiki surface (Confluence, Notion), the ability to read Figma, and a diagramming tool for flows.


• Agile/Scrum experience and the discipline to keep a backlog genuinely ready.


• Strong written communication. This role lives or dies on the clarity of your writing.


• Nice to have


• Background in SaaS, platform, or data products.


• Exposure to analytics or AI/ML-adjacent products, where requirements have to account for probabilistic behavior and data quality.


• Experience operating across multiple products or business units in a holding-company or portfolio structure.

What success looks like

A requirement is done when an engineer who has never spoken to the stakeholder can build the right thing from it, a tester can verify it without asking you, and a reader can tell what was deliberately excluded. We care less about template compliance and more about that bar being met every time.

First 90 days

You'll have shipped at least one substantial spec end to end, established a requirements quality bar the pods trust, and become the person stakeholders come to when they need a fuzzy idea turned into something buildable.

Salary & Benefits

• Location: Remote in Canada or USA 


• Salary: $120k - $135k / Year


• This is a full-time, long-term position.


•  The position is immediately available.


• Work from home.


• Monday through Friday - EST.

Ready to apply? We'd love to hear your story. The next step is a short application where you can share more about your background and upload your resume. Take your time — we read every response carefully.