Seeker | Core AI product, confidential (PropTech, AdTech, MarTech)
We’re building what happens next in multifamily technology.
Our core product is an AI-powered system designed to connect the work that drives property performance.
To get it to market, it takes more than impressive technology. It takes someone who knows this industry well enough to challenge how its software works.
We’re looking for aFounding Product Managerwho can turn a bold vision into a product people understand, trust, and use. Someone who can move between the big picture and the smallest interaction without losing sight of either.
You must have at least five years of experience working in product specifically within the multifamily industry. Similar industries will be considered.
Seeker is a fast-growing, multifamily-focused performance marketing and technology company—and the parent company behind our core AI product, whose name we’re keeping confidential for this search.
Our work sits where renter behavior, property operations, creative, technology, and business performance meet. We help multifamily operators create qualified demand and improve leasing outcomes.
The role:
As our Founding Product Manager, you will help define what we build, why it matters, how it works, and what success looks like.
You will work directly alongside ourCEO and Founder, Co-Founder and CTO partnering closely with engineering, media, analytics and creativeto bring the product to life.
You’ll connect the founders’ vision with customer needs, technical realities, thoughtful design, and a roadmap the team can execute.
This is a senior, hands‑on role. You will lead discovery, establish priorities, write requirements, work through prototypes, resolve trade‑offs, support releases, and study what happens after launch. You will also help build the product function itself: how we make decisions, capture learning, define quality, and keep a growing team aligned.
The backlog is part of the job. Knowing what deserves to be in it is the bigger part.
What you’ll own:
- Shape the product strategy.Translate the company’s vision into clear customer problems, product priorities, and measurable outcomes. Help the founding team distinguish what is essential now, what comes next, and what should not be built.
- Own the roadmap and its trade‑offs.Prioritize across customer value, business impact, technical dependencies, effort, and risk. Make decisions explicit, keep the team focused, and protect the product from becoming a collection of unrelated requests.
- Stay close to the people doing the work.Lead discovery with multifamily owners, operators, marketing leaders, regional teams, and on‑site staff. Observe actual workflows, test assumptions, and uncover the problems that rarely make it into a feature request.
- Turn ambiguity into buildable work.Create product briefs, requirements, user stories, workflow maps, and acceptance criteria that give engineering and creative a clear direction. Think through permissions, exceptions, dependencies, and failure states—not just the ideal experience.
- Partner deeply with the CTO and engineering.Work through architecture implications, integrations, data requirements, feasibility, and delivery sequencing. Make informed scope decisions and balance speed with the reliability the product will need as it grows.
- Build a product that feels considered.Collaborate with creative and design on information architecture, prototypes, interfaces, onboarding, and product language. Make sophisticated capabilities understandable without making them simplistic.
- Connect the customer journey.Help shape workflows across demand generation, prospect engagement, leasing, resident experience, retention, and property performance. Ensure capabilities work together rather than recreating the disconnected tools we’re trying to improve.
- Make integrations useful, not merely functional.Define how the product connects with property management systems, leasing platforms, advertising channels, and other relevant tools. Account for data quality, synchronization, permissions, and what happens when information is incomplete.
- Turn AI capability into customer value.Identify where intelligence, recommendations, and automation genuinely improve a workflow. Define the controls, explanations, human oversight, and success criteria needed for users to trust what the system does.
- Lead pilots, releases, and adoption.Establish learning objectives, coordinate testing, manage feedback, and help determine when a capability is ready for broader use. Partner on onboarding, documentation, and release communications so shipping becomes the beginning of adoption—not the end of the assignment.
- Measure what changes.Define and monitor product adoption, task completion, time saved, workflow quality, and relevant business outcomes. Separate what the product can demonstrate from what we still need to validate, then use that evidence to improve priorities.
- Build the habits of a strong product organization.Establish practical processes for discovery, planning, documentation, quality assurance, and decision‑making. Keep leadership, engineering, and creative aligned without turning every decision into another meeting.
What you must bring:
- At least five years of professional experience in product roles specifically within the multifamily industry.Your background must include meaningful responsibility for building, managing, or scaling multifamily software. General software experience, adjacent proptech experience, or multifamily operating experience without the required product background does not satisfy this requirement.
- A record of shipping products people use.You can clearly explain the problem, your contribution, the decisions you made, and what happened after launch. We’re interested in outcomes, including what you learned when the first version was wrong.
- A working understanding of multifamily operations.You understand the relationships among owners, operators, regional leadership, marketing teams, leasing teams, and residents—and how their needs, incentives, and workflows differ.
- Strong product judgment.You can prioritize with incomplete information, challenge assumptions constructively, and decide when a request points to a real problem versus a one‑off preference.
- Technical fluency.You are comfortable discussing APIs, integrations, data flows, platform constraints, and automation with engineers. You do not need to write production code. You do need to understand the implications of what you ask the team to build.
- Strong design instincts.You recognize that usability, language, interaction quality, and visual clarity are part of product performance. "It technically works" is not your definition of finished.
- Clear communication and genuine ownership.You can write precise requirements, explain a difficult trade-off, and keep different disciplines moving toward the