Senior Engineer, Search
- Has owned a search index in production, not just queried one
- Understands relevance as a product problem
- Latency budgets in the tens of milliseconds
Before: Worked with Elasticsearch.
After: Owned the product search index: 40M documents, p99 under 45ms, reindexed without a read outage.
Why: "Worked with" does not distinguish you from someone who wrote one query. The numbers do.
Before: Participated in A/B tests.
After: Ran the relevance experiments that lifted add-to-cart from search by 6%.
Why: They frame relevance as a product problem. This is the only line on your resume that speaks to that.
Before: Maintained indexing pipelines.
After: Built the near-real-time indexing path; catalogue edits visible in under 30 seconds.
Why: Refresh lag is the hard part of search and the part they will ask about.
- No vector or semantic search on the resume; the posting mentions it as a "nice to have".
Gaps are shown rather than papered over. The assistant rewrites how something is said; it does not invent something you did not do.
