Product Lead

:Selector; New York (NY); On-site; USD 180,000 - 260,000; Full time

Job summary

Selector is an AI-native transformation company helping enterprises turn evidence into measurable outcomes. The Product Lead in a Selector pod partners with a Tech Lead and Principal to define product direction, run experiments, and deliver usable capabilities that move business metrics.

This hands-on role requires turning ambiguous problems into concrete requirements, guiding execution, validating with users, and communicating decisions to executives.

Qualifications

• Experience leading software products or technology-enabled services through ambiguity to real use.
• Ability to define product thesis, priorities, and success measures from customer evidence.

Responsibilities

• Lead product discovery and define the product direction with client impact.
• Co-lead the pod with the Tech Lead and drive requirements, testing, adoption, and measurement.
• Write clear product definitions, memos, and executive updates; communicate tradeoffs.

Skills

Product leadership

Ambiguity to tested answers

Cross-functional collaboration

Executive stakeholder management

AI-enabled product development

Job description

Selector is an AI-native transformation company. We help companies understand consequential business and technology problems, decide what should change, and carry the answer through product definition, implementation, and adoption.

Our teams combine product, engineering, data, operating, and commercial judgment. We work directly with executives and operating teams, stay close to primary evidence, and use AI to move from ambiguity to tested answers much faster than a conventional consulting or product organization.

The role

The Product Lead is one of the two accountable leaders in a Selector pod, working alongside a Tech Lead and under the overall leadership of a Principal.

Your job is to turn an important but poorly defined problem into a product or capability that people use and that improves a measurable business outcome. You will move directly from customer evidence and operating data through product strategy, prototypes, requirements, implementation decisions, testing, adoption, and measurement.

This is a hands-on role. You will not hand research to a strategist, requirements to an analyst, delivery to a project manager, and feedback to someone else. You will use AI to compress those activities while remaining accountable for the judgment and the result.

What you own

The problem. Establish what the client is actually trying to change, who experiences the problem, why it matters, and which business measure should improve.

The evidence. Work directly with users, executives, operating teams, product data, workflows, documents, and technical systems. Separate observed behavior from assumptions and turn uncertainty into specific questions or tests.

The product direction. Define the product thesis, target user, value proposition, scope, priorities, success measures, and important tradeoffs. Make decisions when the evidence is incomplete.

The fastest useful proof. Determine the smallest prototype, workflow, analysis, or production capability that can test the important assumption. Avoid both premature platform building and disposable demos that teach us nothing.

Product execution. Co-lead the pod with the Tech Lead. Maintain a clear decision sequence, shape requirements and acceptance criteria, inspect implementation, resolve ambiguity quickly, and keep the team oriented toward the outcome rather than the ticket queue.

Quality and adoption. Put the product in front of real users early. Define how it will be evaluated, learn from actual use, and stay involved through rollout, operating change, and measurement. Shipping is not success if the product is not trusted or used.

Client communication. Lead product discovery, working sessions, demonstrations, and decision reviews. Write clear product definitions, decision memos, requirements, and executive updates. Make complicated work understandable without flattening it.

Productization. Identify what can repeat across clients. Work with the team to turn successful methods, workflows, and technical components into SelectorOS capabilities, reusable tools, managed capabilities, or commercial products when the evidence and intellectual-property rights support it.

Commercial support. Help the Principal scope new work, assess feasibility, explain the product opportunity, and recognize logical expansions. The Principal owns the account and commercial decision. You supply the product judgment that makes those decisions credible.

How we work

Selector does not treat AI as an assistant added to a conventional product process. We reconsider the process around what a capable product leader, engineering partner, and AI systems can now do together.

You will use AI as a primary production instrument for research, synthesis, data analysis, prototyping, product definition, requirements, testing, evaluation, and communication. You will build repeatable workflows for yourself and contribute useful methods to SelectorOS.

AI increases your reach, but it does not own the decision. You are responsible for understanding the sources, inspecting the evidence, recognizing weak outputs, making the tradeoff, and standing behind the result.

Who will thrive

You have led meaningful software products, operating systems, or technology-enabled services through ambiguity and into real use. Your experience might come from product leadership, a founder role, an operating company, a product studio, or a consulting environment where you personally carried work into implementation.

• Connect product decisions to revenue, retention, margin, cost, risk, or operating performance.
• Earn credibility with an executive, understand an operator’s workflow, and make decisions with an engineer in the same day.
• Conduct discovery without turning it into months of research.
• Write clearly enough that a team can act without another translation layer.
• Prototype and test ideas with modern AI tools.
• Understand technical architecture, data, APIs, and implementation constraints well enough to make sound product decisions.
• Tell a client that the requested feature will not solve the problem.
• Tell a team when the evidence is sufficient and it is time to ship.
• Work with limited supervision and create clarity where no established process exists.

You do not need to be the strongest engineer in the room. You must be technically fluent, intensely curious, and willing to inspect the actual product rather than manage it through reports.

What this role is not

This is not a Scrum Master, backlog administrator, requirements coordinator, or project manager role. It is not a strategy position that ends with a recommendation. It is not a conventional product-owner role in which someone else owns discovery, design, implementation, adoption, or results.

It is also not the Principal role. You will contribute to client trust and account expansion, but you will not initially own the complete commercial relationship, engagement portfolio, or client P&L.