# Software Engineer, Superhuman Database Infrastructure at Grammarly

- Company: Grammarly
- What the company does: Grammarly makes AI writing convenient. Work smarter with personalized AI guidance and text generation on any app or website. Backed by IVP.
- Company website: https://www.grammarly.com
- Type: Startups (AI role)
- Level: Mid level
- Location: Hub - Seattle
- Work setup: Remote
- Pay: $164K to $284K base salary per year (USD)
- Posted: 2026-05-29
- Apply by: 2026-10-08
- Apply: https://jobs.ashbyhq.com/Superhuman%20Platform%20Inc/b572ecd7-8405-4f08-8999-62e551787474
- Page: https://www.1752.vc/careers/jobs/grammarly-software-engineer-superhuman-database-infrastructure/

## About the role

We're looking for a Software Engineer to join the Platform team within Superhuman Docs. This is an opportunity to work on and grow into a technical leadership role on the foundation that powers every table, grid, and view on the platform.

## What they're looking for

- 8+ years of industry experience and at least 5 of those working on relevant technologies
- Understands the tradeoffs in data layout, serialization formats, and access patterns at a level that goes beyond API usage — you've made decisions about how data is actually stored and retrieved under the hood
- Has shipped and operated storage-layer systems where correctness under concurrency is non-negotiable — you understand read/write ordering, invalidation hazards, and what "consistent" actually means in a distributed setting
- Understands write-ahead logging, crash recovery, and checkpoint strategies — and the tradeoffs between write amplification, recovery time, and storage overhead when designing for durability
- Brings strong instincts for performance engineering and cost-aware design: profiling storage operations, reasoning about cache behavior, identifying hot paths, and making principled tradeoffs between performance and operational cost at scale
- Can work across a large, complex system — the tables layer touches the sync engine, the formula runtime, the client-side rendering layer, and external APIs, you're comfortable reasoning about correctness and performance across those boundaries

Tags: Engineering, Product, Design, and...