Back to jobs

AI Context & Data Infrastructure Engineer

San Francisco · San Francisco, California, United States

Live, first seen by us 84 days ago
Pay
Pay not listedSimilar roles state $127K–$189K
Work setting
On-site — work setting source
Location type: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
EPD — team source

What you’ll work on

Full posting

Town is building the most personalized, most capable AI assistant for everyone — and personalization at that level is a retrieval and data problem.

You'll build the foundation the whole product reasons over: the search and data infrastructure behind that context.

  • Build one shared search and retrieval layer the whole product pulls context from

  • Combine lexical and semantic search, including hybrid retrieval and ranking

  • Design the durable data model the assistant's work is built on

  • Build and operate realtime and batch pipelines that keep the index fresh and correct

  • Stand up indexing and storage that stay fast, reliable, and cost-effective at scale

From the employer’s posting
Town is building the most personalized, most capable AI assistant for everyone — and personalization at that level is a retrieval and data problem. The assistant is only as good as the context it can bring into the moment: the right memory, message, document, or relationship, pulled fast and related by meaning across everything a person and their team touch.
You'll build the foundation the whole product reasons over: the search and data infrastructure behind that context. One shared retrieval layer combining lexical and semantic search, the realtime and batch pipelines that keep it fresh and correct, and the durable data model everything else is built on.
Build the search and retrieval layer that puts the right context at every Townie's fingertips
Combine lexical and semantic search and own the tradeoffs between them
Design the durable data model the assistant's work is built on
Build and operate the pipelines behind it — realtime/streaming and batch — that keep the index fresh and correct as the underlying data changes.
Stand up the indexing and storage layer and keep it fast and reliable at scale

About Town.com

Town is building the AI coworker for every team.

In the employer’s words · Read in context · Company website ↗

Apply at Town.com

Posting record

Report an error
Status in our records
Live
First seen by us
Aug 30, 202684 days ago
Recorded sightings
49
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$127K–$189K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 2,448 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 84

Up longer than most. Similar jobs usually come down between day 6 and day 56.

From 14,766 similar postings that came down. Coming down is not always a hire.

See how this role fits your experience

Add your resume to compare the role’s scope, tools and requirements with your experience.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

About Town

Town is building the AI coworker for every team. Everyone gets their own Townie, an AI assistant that learns how you work (your voice, judgment, relationships, and priorities) and does real work on your behalf across email, calendar, docs, Slack, and CRM. Townies don't wait to be prompted. They observe, learn, and act. And because every teammate has one, Townies can ask each other questions and hand off work, so the whole team moves faster together.

Four months after our public launch, we became a $1B company. We recently raised a $108M Series B, co-led by Forerunner Ventures and Menlo Ventures, with continued support from Andreessen Horowitz, First Round Capital and angels such as Zach Perret, Soleio Cuervo, Scott Belsky, and more. Our founders, Jean-Denis and Tony, previously led EPD at Plaid and applied AI product at Google.

 

About the role

Town is building the most personalized, most capable AI assistant for everyone — and personalization at that level is a retrieval and data problem. The assistant is only as good as the context it can bring into the moment: the right memory, message, document, or relationship, pulled fast and related by meaning across everything a person and their team touch.

You'll build the foundation the whole product reasons over: the search and data infrastructure behind that context. One shared retrieval layer combining lexical and semantic search, the realtime and batch pipelines that keep it fresh and correct, and the durable data model everything else is built on.

This is greenfield and high-leverage: you'll be the first person building this layer.

 

What you'll do

  • Build the search and retrieval layer that puts the right context at every Townie's fingertips, the moment it's needed — one shared layer the whole product pulls from instead of refetching context on its own.

  • Combine lexical and semantic search and own the tradeoffs between them: vector vs. lexical, precompute vs. fetch, hybrid retrieval, and ranking.

  • Design the durable data model the assistant's work is built on, so context is relevant, fast, and cost-effective.

  • Build and operate the pipelines behind it — realtime/streaming and batch — that keep the index fresh and correct as the underlying data changes.

  • Stand up the indexing and storage layer and keep it fast and reliable at scale: latency, cost, freshness, and completeness.

  • Lay the groundwork for relating content by meaning across everything the assistant knows — the start of a knowledge graph of people, companies, projects, and how they connect.

 

You might thrive here if you...

  • Have significant, hands-on experience across lexical and semantic search components and approaches (BM25, embeddings, ANN/vector indexes, hybrid retrieval, ranking).

  • Have run large-scale data infrastructure, ideally both realtime/streaming and batch — pipelines, indexing, and storage.

  • Can make retrieval fast and cheap at scale, and reason about the latency, cost, and freshness tradeoffs cold.

  • Are a systems thinker comfortable in greenfield, where the foundation doesn't exist yet.

  • Are excited to take these systems from rapid prototype to production scale.

  • Bonus if you've worked on ranking/relevance, knowledge graphs, or retrieval for LLM or agentic systems.

 

Location

San Francisco, CA. Five days a week in person at our Financial District office.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

San Francisco, California, United States

- Build the search and retrieval layer that puts the right context at every Townie's fingertips, the moment it's needed — one shared layer the whole product pulls from instead of refetching context on its own. - Combine lexical and semantic search and own the tradeoffs between them: vector vs. lexical, precompute vs. fetch, hybrid retrieval, and ranking. - Design the durable data model the assistant's work is built on, so context is relevant, fast, and cost-effective.
More source context
You might thrive here if you... - Have significant, hands-on experience across lexical and semantic search components and approaches (BM25, embeddings, ANN/vector indexes, hybrid retrieval, ranking). - Have run large-scale data infrastructure, ideally both realtime/streaming and batch — pipelines, indexing, and storage.
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.