← Navan Interview Insights

Navan·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Mar 2026

Summary

Navan system design round, one meaty OOD question that took the whole session. The problem sounds contained at first but the bulk update extension is where things get genuinely interesting.

Questions Asked (1)

Q1

Design a system that stores auxiliary comments (like 'room should be quiet') attached to either a specific booking or a recurring entity like a room or listing. Regular users can add comments to their own bookings, admins can update existing ones. As an extension: how would you support efficient bulk updates by admins, such as applying the same comment change across many bookings or rooms at once? Cover the entity model, ownership and permissions, persistence, indexing, and consistency.

System DesignData ModelingTechnical Trade-offs
Author's notes

I started with the entity model and that part went fine.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and defining a flexible entity model that supports comments on both bookings and recurring entities like rooms or listings. Then discuss ownership and permissions, persistence with indexing for efficient queries, and consistency guarantees. Finally, address the bulk update extension by proposing a scalable approach such as asynchronous batch processing with idempotency and conflict resolution.

Pro tip: Emphasize the importance of idempotency and auditability for bulk updates, and suggest a design that decouples the bulk operation from immediate consistency to avoid locking and performance issues.

1. Clarify Requirements and Scope

Ask questions to understand the expected scale, read/write patterns, and whether comments are mutable or immutable. Clarify if bulk updates should be atomic and how conflicts should be resolved.

2. Design Entity Model and Ownership

Define a polymorphic association for comments (e.g., commentable_type and commentable_id) to attach to bookings, rooms, or listings. Specify ownership rules: users can add comments to their own bookings, admins can update any comment.

3. Plan Persistence and Indexing

Choose a relational database for strong consistency and support for transactions. Create indexes on (commentable_type, commentable_id) for efficient retrieval, and on user_id for ownership checks. Consider partitioning for large tables.

4. Define Permissions and Consistency

Implement role-based access control (RBAC) to enforce who can create, read, update, or delete comments. Use transactions for atomic updates and consider optimistic concurrency control to handle concurrent modifications.

5. Address Bulk Updates Extension

Propose an asynchronous job queue for bulk updates: admins submit a bulk operation, which is processed in batches with idempotency keys. Use a staging table or change log to track progress and ensure eventual consistency, with notifications on completion.

Key Points to Mention

  • Polymorphic association for comments to support multiple entity types
  • Role-based access control (RBAC) for permissions (users vs admins)
  • Database indexing strategies for efficient querying by entity and user
  • Transaction management and optimistic locking for consistency
  • Asynchronous batch processing with idempotency for bulk updates
  • Audit logging and change tracking for bulk operations

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.