Skip to content
Bitfocus

Product Manager

Remote; RemoteRemote · region unclear
Product
POSTED 21 OCTVERIFIED 22H AGO
Apply Ask
Role
18 days opentrue age
Posted 21 Oct
CompanyBitfocus →
7open roles
Opened · 30d
+0
Closed · 30d
−0
30d window
Market
4,005open · Product
All product
8,165open
All tracked boards · live 8 Nov · n=4,005
Figma

About Bitfocus

At Bitfocus, our mission is simple but ambitious: help end homelessness. We build and support Clarity Human Services, the technology that powers communities across the country in connecting people experiencing homelessness with the resources they need.

We lead with care, innovate with insider knowledge, and believe deeply in the power of community. We know strong candidates don't always look the same on paper, so if you're excited about this role, we'd love to hear from you. People with lived experience of homelessness are strongly encouraged to apply.

About the role

Your work decides what gets built next in the software that homelessness response systems rely on every day. You'll turn what communities need into clear requirements and thoughtful designs, so Engineering can build with confidence and the right features reach the people doing this work. As you grow, you'll take on larger features and a wider share of the product, with a defined career path to help you get there.

About the Product team

The Product team defines, documents, and designs the features that Engineering builds into Clarity Human Services and our data products. We work closely with Engineering, customer-facing teams, and the communities we serve.

Solutions analysis and business process mapping

Technical writing: requirements, specifications, and process documentation

User experience design: workflows, wireframes, and prototypes

Usability testing and customer feedback

HMIS data standards and interoperability

Cross-team prioritization and planning with Engineering

What you'll do

Shape the product. Define, prioritize, and drive enhancements based on user needs, market trends, and what the system can do today.

Write requirements Engineering can build from. Produce clear, structured requirements and specifications, supported by flowcharts and basic UML diagrams where they help, and keep them current as requirements and project goals change.

Design with users in mind. Create and refine user workflows, wireframes, and prototypes, then test them before they reach development.

Listen to customers. Take part in customer onboarding, usability testing, user interviews, and our Feature Focus Q&A rotation, and turn what you hear into product decisions.

Partner across teams. Work with Engineering, customer-facing teams, and senior stakeholders to align on priorities, adjusting how you explain complex topics to each audience.

Keep the backlog ready. Get documentation and design done ahead of engineering capacity so the teams you support always have meaningful work queued.

Spot risks early. Identify gaps, dependencies, and unclear requirements before they slow a release, and use data and stakeholder input to make the call on what to do about them.

Work with modern tools. Use Jira, Confluence, Figma, Claude, Gemini, and similar tools to track, document, and design your work.

You'll know you're succeeding when...

Within your first 90 days, small and medium features reach Engineering ready to build, and large features do with support. You can explain Clarity and HUD data standards in your own words.

Engineering accepts your documents without rework and builds without repeated clarification, and you deliver against agreed timelines, raising risks before they affect release plans.

By month 6, large features go from idea to ready for Engineering on your own, and you're taking part in Feature Focus Q&A, customer onboarding, and usability testing.

Customer and usability feedback is documented, reflected in design changes before release, and traceable to the enhancements you prioritize.

Stakeholders across Product, Engineering, and customer-facing teams can explain current priorities and the reasoning behind them.

By month 12, you're carrying a full product manager workload across all engineering teams, and each team's backlog stays stocked with ready work.

What you bring

Product or analysis experience. At least 3 years in product management, business analysis, or a related role.

Requirements writing. Experience documenting software requirements and producing structured technical documentation.

Source · BitfocusFirst seen 4 NovOriginal ↗