Product Manager (SaaS)

Holistics is on a mission to improve data teams' productivity by bringing software engineering best practices to Data Analytics. We are looking for relentless and passionate builders to join our team to drive Holistics towards that mission.

And as a Product Manager of Holistics, you will be able to learn and get involved in building a simple yet powerful high-tech product that is directly shaping the data industry.

How we build products

Product Culture

• Autonomous but aligned: We adapt the Spotify Squad Model. Our team is split into 4 Squads, each (5-7 members consists of PM, PD, and Engineers work autonomously together. Each has its own mission, strategy, and goals that contribute to our product's overall vision.
• We embrace transparency culture across the company. We make sure that everyone know what's going on and have access to any information they need to make informed decisions, whether it is a technical document, a revenue dashboard, or a strategy discussion.
• We have a strong writing (doc-first) culture. Documents create transparency and clarity of thought, almost everything in Holistics is communicated through written documents. Everybody has to learn the best practices in writing and note-taking such as (, , Zettelkasten, etc.)
• Customer-informed, not Customer-driven. We observe and listen carefully to our customers, but we don't try to build everything they ask for. We strive to empathize, learn their real needs, and figure out how they would fit into our vision.
• Data-informed, not Data-driven. Product management is an intersection of science and art, data are used to inform our decisions, strengthen our intuition rather than to be relied on.
• We maintain a problem-solving culture. Everyone is strongly encouraged to have rigorous understanding of a problem, separating as well as using to find the most important dimensions of a problem. Solutions are deliberated over with trade-offs explicitly listed in discussion documentation. Watch (Vietnamese) from our cofounder.
• We do not compromise product quality for artificial deadline. We find the balance between moving fast and thinking deeply about long-term product vision and architecture.
• Everyone is a builder, Experimentation Culture
• Continuous learning: We encourage people to learn and share, because each member is an atom of the product/company’s success: We have a where team members present about topics they are interested in; Engineering Team organizes as well as monthly technical workshops; Product Team has regular AMA events with external product experts, and Happy Sharing events to share what have we learn; We share what we learn in every meeting with have, and on every channel we communicate

‍

Product Principles

Product Principles inform how we build, design, and make decisions when developing products.

• Always start with problem: The key to success is identifying the right problem to solve. Always start everything with deeply understanding of the problems to be solved, be clearly aware of the problem and solution spaces.
• Customer-Centric: We build products to make our customers' lives better. Constantly talk to our customers and observe how they use product to understand deeply their challenges at work.
• Think Deep, Think Big, Start Small: Think in long-term, envision how the product will evolve and fit into the big picture. Then start with a smallest coherent solution. Always ask yourself how can you ship sooner and learn faster.
• Simple things should be simple, complex things should be possible: Data Analytics is huge space, and data tools are usually complex. We challenge ourselves to build a powerful analytics product that is also easy to use, allowing anyone to make data-informed decisions.
• Prioritize Ruthlessly: We must deprioritize a lot of things in order to do what we prioritize. Each feature increases maintenance cost, operational cost, and the product complexity. It is better to focus on doing a few things well than many things half-assed.
• Empowered Product Team: We always start with the problem, instead of a list of features, everyone is empowered to dig deeper into the problem space, define their own approach and strategy to solve the problem. - . We substantially invest in individuals to reach their potential, because we believe each individual's success generates compounding growth for the entire product.

What will you be doing & learning‍

Learn by doing, be the owner of what you build (Discover, Build, Launch, Measure, Learn, Lead)

• 🔍 Discover: Understand the market and users by leading user/market/competitive research to scope out the right problems, and formulate product strategy for Holistics.
• 🔨 Build: Translate product strategy to executable plans and objectives, collaborate with Engineering & Design teams to come up with the desirable solutions.
• 🚀 Launch: Launch the final features/products to the market, clearly communicate product values to users and internal stakeholders.
• 📐 Measure: Define success metrics, learn from numbers and customer feedback to improve the products.
• 🎓 Learn: Learn from what you built and shipped, continuously experiment and enhance the quality of the products.
• ⭐ Lead: Own the products/features, become a decision-maker, and inspire your teammates to achieve the missions together.

‍

We have a variety of challenging product areas where you can learn and grow:

• Analytics-as-code: Holistics allows you to define your analytics logic in code (DSL) and check it into Git version control. This makes the analytics process more maintainable and streamlined.
• Product Growth: Increasing the value proposition of Holistics to the existing target market by removing barriers to access and increasing product distribution.
• dbx (dbdiagram, dbdocs, and DBML): an open-source product line that aims to increase developer productivity by providing the best database tools.

Stories about how we build and launch products at Holistics

Interview Process

• Round 1: A chat with the Product team (Short chat to introduce Holistics, our product, discuss to understand your skills, experiences & past projects)
• ‍Round 2: Do take-home assignment (offline - deadline 3 days, will be sent after Round 1)
• ‍Round 3: Present assignment with our Product team