What you'll do- Own important product problems end-to-end, from understanding the business and user problem through building and shipping the solution
- Immerse yourself in Clutch's operations, customers, systems, processes, and data to understand how things actually work
- Challenge requests and assumptions to make sure we're solving the right problem rather than simply building what was asked for
- Shape product solutions and design elegant, intuitive experiences users enjoy using
- Use AI and agentic development tools to build working products across the front end and back end
- Work with APIs, business logic, data, and existing Clutch systems to turn ideas into functioning software
- Put working products in front of stakeholders and users early rather than relying solely on specs, mockups, or prototypes
- Test against realistic scenarios and data to uncover edge cases before launch
- Ship quickly, learn from real usage, and continuously improve what you've built
- Run experiments and measure whether your work is actually solving the problem
- Work directly with operators, designers, engineers, marketers, and other specialists when their expertise improves the outcome
- Improve our product-development practices as the tools and capabilities available to builders continue to evolve
Minimum requirements- 4+ years of experience building digital products in product design, product management, software engineering, or a similarly hands-on product role
- Strong product sense - you think about the product and business as a whole rather than as a collection of features or screens
- Demonstrated ability to take ambiguous problems and turn them into thoughtful, practical solutions
- Strong UX instincts and a high bar for making products intuitive and enjoyable to use
- Curiosity about users and a willingness to spend time understanding how they actually work
- Comfort using AI-assisted or agentic tools to build software, or a strong desire to become highly proficient with them
- Willingness to work outside the traditional boundaries of your discipline
- Ability to learn unfamiliar technical or business domains quickly
- Bias toward shipping, testing, learning, and iterating
You do
not need to be an expert designer, product manager, and software engineer at the same time. You do need to be willing and able to move beyond your existing specialty when the problem requires it.
Preferred qualifications- Experience at a startup, either as an early employee or founder
- Experience owning products from problem discovery through launch and iteration
- Experience working directly with engineers or contributing to production code
- Experience building with modern AI coding or agentic development tools
- Experience with experimentation, A/B testing, analytics, or product-led growth
- Experience building internal tools or software for operationally complex businesses
- Comfort working with APIs, data, and unfamiliar systems
- Ability to work on multiple projects in parallel and prioritize based on business impact
- Evidence of having taught yourself skills outside your formal discipline
You WILL NOT enjoy this role if- You want your responsibilities to stay strictly within the boundaries of design, product management, or engineering
- You prefer handing work off to another function once your part is complete
- You want to spend most of your time producing specifications, presentations, or Figma files rather than working software
- You are uncomfortable touching code because you don't consider yourself a developer
- You prefer firm processes over adaptive ones
- You need every problem to be clearly defined before you begin
- You don't like being scrappy
- You don't like small, agile teams
- You optimize primarily for how much you can build rather than whether something should be built
What makes a great builder at ClutchGreat builders are curious.
They want to understand the business logic underneath the thing they're working on. They talk to users. They inspect the data. They challenge assumptions. They ask why a problem exists before deciding how to solve it.
They have judgment.
When building becomes dramatically easier, choosing what to build - and what
not to build - becomes even more important. Great builders care about solving meaningful problems and measuring whether their solution actually worked.
They have taste.
They care whether a product feels elegant, intuitive, and complete. They sweat the details and cover the edge cases rather than treating quality as something to address later.
And they build.
They are excited to use new tools, learn unfamiliar skills, move quickly from an idea to working software, sit beside the people using it, and change it again.
Why you'll love it at Clutch- Autonomy & ownership - own meaningful problems from beginning to end
- A new way of building - work at the intersection of product, design, engineering, and AI
- Fast feedback loops - put working software in front of users and improve it quickly
- High impact - solve problems across a complex, rapidly changing business
- Competitive compensation and equity incentives
- Generous time off program
- Health & dental benefits
