We are hiring a Tech Lead Manager to build and lead our Context team in San Francisco. Context owns everything Profound knows about a customer and everything our agents reach for when they do work. Every integration a customer connects, every document and page we ingest, every entity we resolve, and every piece of durable memory an agent carries between sessions runs through this team. If our agents are the hands, Context is the memory and the senses. The quality of what we ship is bounded by the quality of the context we retrieve.
This is a hybrid role. You’ll spend roughly half your time on technical leadership and architecture, and half on people management, hiring, and execution. We expect you to write code, review PRs, and be in the details on critical decisions. We also expect you to grow engineers, run a tight planning process, and own outcomes for the team.
The Context team owns the integration service (the shared substrate for connecting to third-party systems: OAuth flows and token lifecycle, API key management, MCP servers and clients, credential storage and rotation, webhook ingestion, and per-provider rate limiting and backoff); the integration catalog itself (CMS platforms, analytics and search consoles, CRMs, document stores, support desks, and commerce systems, each with its own auth model, pagination quirks, and failure modes); knowledge base storage and retrieval (ingestion and chunking, embeddings, hybrid keyword and vector search, reranking, freshness, and strict tenant isolation across a store handling billions of documents); data synchronization (incremental sync, backfills, change detection, deduplication, conflict resolution, and the observability that tells us a customer’s data is current before they notice it isn’t); and context management (the knowledge graph that resolves brands, products, competitors, topics, and pages into a coherent model of a customer’s world, plus the long-term memory service that lets agents accumulate and reuse what they learn).