Principal Business Analyst

About Prenosis

Prenosis Inc. is an artificial intelligence company pioneering precision medicine in acute care. Our Immunix™ precision medicine platform drives the development of precision products and enables real-time delivery of optimal therapy. We've created and validated the first FDA-authorized AI biomarker for sepsis, the Sepsis ImmunoScore®.

At Prenosis, we:

• Put patients first

• Disrupt with evidence

• Excel with integrity

• Go far together

Our staff collectively defined these corporate values to demonstrate how our teams contribute to meaningful and authentic change in U.S. healthcare. We value our diverse talent, strive to foster a culture of continuous learning, and aim to maintain a feeling of belonging and shared sense of purpose.

Prenosis is headquartered in Chicago Illinois and generally operates on Central Time Zone.

Position Summary

We're looking for someone to own the software requirements process end-to-end, from initial elicitation through to sign-off, traceability, and change control. This person is the connective tissue between business stakeholders, product management, and engineering, ensuring that what gets built is well-understood, well-documented, and well-governed before a single line of code is written, and stays accurate as the product evolves.

This is not a “write user stories and move on” role. It's a process-ownership role: you'll define how requirements are gathered, documented, reviewed, approved, versioned, and traced across the organization, and you'll hold others accountable to that process

Responsibilities

• Requirements process design: Define and continuously improve the end-to-end lifecycle: elicitation, analysis, specification, validation, approval, baselining, and change management. Develop and maintain the processes in the QMS.

• Elicitation & stakeholder alignment: Run structured interviews, workshops, and working sessions with business stakeholders, customers, and SMEs to surface functional and non-functional requirements.

• Documentation standards: Establish templates and quality bars for requirements artifacts (PRDs, use cases, user stories, acceptance criteria, SRS documents) and enforce consistency across teams.

• Hands-on requirements authoring: Personally author, not just template, the artifacts for key initiatives: user stories with acceptance criteria, functional requirements specifications (FRS), configuration specs, use case documents, and interface/data requirements, written to a standard clear enough for engineering and QA to work from without follow-up clarification.

• Traceability: Maintain a requirements traceability matrix (RTM) linking business needs → requirements → design → test cases → release, so every requirement can be traced forward and backward.

• Review & approval governance: Run requirements review boards / walkthroughs; manage formal sign-off from business and technical stakeholders.

• Change control: Own the change request process for requirements after baseline: impact analysis, approval routing, versioning, and communication of changes to affected teams.

• Quality & ambiguity reduction: Identify gaps, conflicts, and ambiguities in requirements before they reach engineering; ensure requirements are testable, unambiguous, and prioritized.

• Compliance & audit readiness — For regulated software environments, ensure requirements documentation meets audit and compliance standards (e.g., 21 CFR 820, IEC 62304, SOC 2, HIPAA, ISO 27001, as applicable).

Expected frequency and duration of travel: 2- 3 times a year