Frontend Engineer (with passion for UIUX & Performance)

The position

We’re the team behind projects like BI tool , database diagram tool , and open-source project . 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.

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 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 decoupling 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.

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 plague 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.

What you’ll work on here

Here are some interesting engineering projects that have been going on inside Holistics

• Build a web-based IDE for data analysts to explore and develop analytics logic
• Build front-end components that can render hundreds of thousand of data points
• Build custom, interactive visualization components on top of open source technology
• Create a as part of a semantic layer to represent analytics logic
• Build a text-based database for analytics metadata on top of Git
• Create a that compiles to SQL
• Design and build a natural language interface for business users to explore data and view dashboards

The way we work

We follow Spotify squad model. Our team is split into 4 squads, each (5-7 members) consisting 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 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 .

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)

We avoid being a . 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:

• 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