We’re the team behind projects like BI tool Holistics, database diagram tool dbdiagram.io, and open-source project dbml.org. We’re looking for another front-end engineer to help us build more awesome tools for data teams and developers.
This is a full-time position based in Ho Chi Minh City with flexible, hybrid WFH/WFO setup.
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 frontend side, 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.
Most of our “as-code” features operate in dual modes: code-mode and UI-mode. The code is for technical-savvy users, while the UI mode is for those who prefer a more intuitive start. To support these features, we have developed our own compiler and a web-based editor, similar to a lightweight version of VSCode, both of which are optimized for performance in the browser environment.
While we use the word frontend, it encompasses both the conventional frontend aspects as well as the “backend of the frontend”. This includes elements like frontend architecture, designing data structures to enable complex visualizations, and packaging components to reuse them across various product lines.
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 engines to improve maintainability and extensibility, following modular monolith pattern. This also follows the pattern of “Functional core, imperative shell with the gems being mostly functional/stateless code and engines handle the imperative/stateful part of the app.
By using Sorbet 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 custom job queue system on top of Postgres, which are then executed using Sidekiq on top of Redis.
Here are some interesting frontend projects that have been going on inside Holistics:
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:
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 advantage.
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 evergreen notes.
We maintain a problem-solving culture. Everyone is strongly encouraged to have rigorous understanding of a problem, separating Problem Space vs Solution Space as well as using Eigenquestions to find the most important dimensions of a problem. Solutions are deliberated over with trade-offs explicitly listed in discussion documentation. Watch this talk about problem-solving for engineers that our cofounder gave (in Vietnamese)
We avoid being a feature factory. We’re aware more features do not equal better product.
We let team members rotate every 3-6 months. This allows them to try new things and learn different aspects of the business.
Our culture stimulates continuous learning:
Here’s our idea of a good team member fit:
Workstation: Macbook/Laptop Grant, Mechanical Keyboard, 27-inch monitors
Working Time: from Monday – Friday, from 9.00 a.m. to 6.00 p.m.
Work Location: 457 Nguyen Dinh Chieu, District 3, Ho Chi Minh City