Holistics

Overview of job

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

Our application’s architecture

To get a taste of how working with us is like, here are some insights into how our application has been built so far.

The Holistics app works by allowing data analysts to connect to their data warehouses and develop reusable “data models”. This allows non-technical users to use a friendly drag-and-drop interface to explore the data and build dashboards, without the need to bother their technical colleagues.

On the backend side, Holistics is built using Ruby on Rails as the main web framework. Unlike standard Rails project structure, we modularize the code base into local gems and to improve maintainability and extensibility, following . This also follows the pattern of " with the gems being mostly functional/stateless code and engines handle the imperative/stateful part of the app.

By using to add static typing on top of Ruby, we ensure that most of our Ruby code has annotated type signature. This not only reduces a whole swath of common bugs that plagues Ruby codebases but also significantly improves developer productivity through IDE/editor integrations.

We use PostgreSQL for our main production database due to its reliability and rich feature-set. We have built a , which are then executed using Sidekiq on top of Redis.

Vue.js 3.0 with TypeScript is our framework of choice for front-end development. To deal with displaying huge amount of data, we build sophisticated, custom Vue components that lazily render the data. Since many complex computation are done on the front-end, we also use Web workers to decouple those computation from the main rendering thread. This enables smoother user experience while also decouples computation from rendering logic.

The way we work

We follow Spotify squad model. Our team is split into 4 squads, each (5-7 members) consists of engineers, product managers & designers working closely together.

How we work on a new feature:

• Product & Design Team spends time research the problem, talk to customers and prepare Product Discovery Doc (PDD) and Product Requirement Doc (PRD).
• Engineering Team then performs a Technical Research. When we have a fairly good picture of the complexity and impact, we’ll start with the implementation.

We avoid being a . We’re aware more features do not equal better product.

We do not compromise product and code quality for artificial deadline. We refactor and think about code optimization regularly. We understand the good and bad of technical debt and use them to our advantages.

We employ “pair programming” practices regularly where two team members work on a task together in one workstation. This brings a great deal of benefits, among which are faster knowledge transfer, reduced bus factor, better team cohesion and improved code quality.

We have a strong writing culture: Almost everything is communicated through written documents. Just as our developers write reusable codes, we write .

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 that our cofounder gave (in Vietnamese)

Our culture stimulates continuous learning:

• We let team members rotate every 3-6 months. This allows them to try new things and learn different aspects of the business.
• We have a where team members present topics they are interested in.
• Engineering Team organizes as well as monthly technical workshops.
• Product Team has regular AMA events with external product experts

Benefits:

👨🏼‍💼 Training & career developments

• Weekly TED talks to expand skills and knowledge.
• Yearly budget to support personal and professional growth, well-beings and interest cultivations.

🌏 Competitive salary and benefits

• 24/7 Healthcare Insurance, Periodic Medical Checkup.
• Salary regular reviews, 13-month Bonus.
• Stock Options for high-contributing individuals.

💕 Awesome company policies

• A flexible work culture, Regular reviews, Remote policy.
• 14 Annual leaves/year, 14 Sick leaves/year, Children care leave policy.
• Weekly happy hours. Company trip and company-organized events.

🏢 Workstations provided for maximum productivity

• MacBook (or Laptop) Grant
• Mechanical Keyboard + Razer Mouse
• Big-screen monitor(s)

🌐 Working time: From Monday – Friday, from 9.00 a.m. to 6.00 p.m.

We’re looking for a Product Manager who’s excited by this vision to join us on this ambitious product.

• You love problem-solving, you find it unpleasant when a problem goes unsolved, you want to figure out the root cause to come up with a proper solution.
• You have entrepreneurial spirit. You want to learn how a business or startup operates so that you can eventually start your own.
• You are a lifelong learner, who are curious how the everything works and strive to grow yourself everyday.
• You treat yourselves like a product, always iterating and improving to deliver more value.
• You believe and want to prove that a Vietnam-based Product & Engineering Team can build a world-class product.
• Genuine interest in the space: We’d love to work with people who are genuinely interested in the product and the space we’re in.
• Great English writing and communication skills.
• Bonus - You are a builder: You have built and launched your own product, or you have a plan to do so.
• You are welcome if you believe you are good at at least 3 of the skills listed in our competency model, we will help you develop the rest: Fluency with Data, Customer Interview and Qualitative Research, User Experience, Market and Competitive Research, Product Design, Writing Feature Specs, Product Delivery, Product Vision, Strategy and Roadmapping, Business Outcome Ownership, Managing up, Team Leadership, Stakeholder Management