8 months ago
Responsibilities
- Design and own the semantic layer powering Netic’s system of record and AI products.
- Build internal platform primitives, abstractions, and APIs for product and engineering teams.
- Partner with internal teams to make platform systems intuitive, well-documented, and difficult to misuse.
- Architect systems spanning data warehouses, OLTP databases, streaming systems, and vector stores.
- Make tradeoffs involving latency, throughput, consistency, and access patterns.
- Define long-term platform architecture, including build-versus-buy decisions and semantic-layer evolution.
Requirements
- 5+ years of experience building and operating distributed systems.
- Experience owning a platform or core abstraction used by multiple teams is preferred.
- Deep understanding of data warehouses, transactional databases, and other storage systems.
- Ability to design durable schemas, contracts, and semantic models that support rapid product iteration.
- Experience with observability, migrations, backfills, incident response, and high-uptime systems.
- Strong ownership of long-term technical outcomes, platform leverage, and system reliability.
About Netic
Netic builds an AI-driven revenue platform for large enterprises in essential service industries, automating customer acquisition, booking, and repeat work. The company sells enterprise software (SaaS) used across service verticals in North America and reports helping customers book hundreds of thousands of jobs. Headquartered in San Francisco, it is privately held and backed by investors including Founders Fund, Greylock, Hanabi, and Figma cofounder Dylan Field.