Technical Product Owner, HRS SF424

Huron helps its clients drive growth, enhance performance and sustain leadership in the markets they serve. We collaborate with education organizations to develop strategies and implement solutions that enable the transformative change our clients need to own their future. Together, we empower clients to drive innovation, create sustainable funding streams and deliver better student outcomes.

Today, leaders of higher education institutions and academic medical centers are spending too much time reacting to market forces, rather than focusing on the essential priorities that help students, faculty and staff thrive. The most productive path forward requires an intentional approach and innovative thinking, whereby stakeholders across the entire institution rally around a shared vision and embrace the hard work of effecting change.

You’ll help our clients to achieve organizational effectiveness, improve student outcomes, implement new technologies and align resources and investments to ensure long-term sustainability.

Join our team as the expert you are now and create your future.

The SF424 Technical Product Owner is responsible for supporting the product team through detailed requirements analysis, mapping validation, requirements workbook preparation, status tracking, release validation, and cross-functional communication for the HRS SF424 product area. This role provides the structure and execution support needed to move SF-424 forms from analysis and generated outputs into validated work products that engineering teams can implement and test.

The role requires a strong analytical orientation and the ability to learn a complex intersection of federal grants administration, Grants.gov system-to-system submission requirements, HRS Grants workflows, form engines, field mappings, XML schemas, validation rules, attachment handling, and agency-specific form behavior. The ideal candidate is comfortable working close to technical detail without needing to be a software engineer.

This Technical Product Owner will work in close partnership with the HRS SF424 Product Owner and HRS Product Management. The role supports requirements of clarity, validation throughput, engineering readiness, and product continuity while Product Management and the Product Owner retain final roadmap, prioritization, and product decision authority.

SF424 Forms, Grants.gov & Research Administration Domain Support Expectation: Build enough SF424, Grants.gov, and research administration knowledge to support accurate product analysis and informed decision-making.

• Develop strong working knowledge of SF-424, SF-424 R&R, mandatory, individual, short organization, budget, subaward, and agency-specific form families used in federal grant application packages.
• Understand how HRS Grants supports proposal development, institutional routing and approvals, sponsor opportunity packages, Grants.gov submissions, attachments, budgets, subawards, certifications, and related research administration workflows.
• Analyze federal form instructions, business rules, form versions, schema changes, agency-specific requirements, and customer workflow expectations to determine product and implementation impact.
• Support the Product Owner and subject matter experts by preparing structured analysis, surfacing decision points, documenting rationale, and reducing dependency on a single product lead for detailed operational product support.
• Pay particular attention to complex budget-related forms and subaward forms, where calculations, repeats, attachments, cross-form dependencies, and HRS implementation logic may require deeper manual analysis and validation.

Requirements, Mapping, Validation & Engineering Readiness Expectation: Turn SF424 source materials, mappings, and technical inputs into clear, validated requirements that engineering and QA can act on.

• Create and validate SF424 requirements workbooks from Grants.gov instructions, schemas, HRS Grants logic, field-level rules, and product priorities.
• Analyze key form details, including field definitions, versions, display and required rules, validation rules, list values, help text, repeatable sections, attachments, and budget logic.
• Review generated workbooks, scorecards, mappings, and inferencing outputs to identify gaps, incorrect assumptions, rule issues, and missing requirements.
• Translate ambiguous input into clear requirements, assumptions, op…