Senior Software Engineer, Guest Acquisition

Owner.com is an AI-native system designed to help local business owners, particularly in the restaurant industry, succeed through a comprehensive platform that integrates various business tools. The Senior Software Engineer for Guest Acquisition will own the technical strategy for SEO/AEO systems at scale and lead initiatives to attract consumer demand for restaurant customers through innovative technology solutions.

Responsibilities:

• Own the technical strategy for SEO/AEO systems at scale, translating ambiguous growth goals into a prioritized roadmap, clear metrics, and durable system architecture
• Lead end-to-end delivery of major initiatives such as new ingestion sources, indexing and serving improvements, or content generation workflows, from design through launch and operational readiness
• Raise the bar on reliability, quality, and observability across pipelines and services, building guardrails, alerting, dashboards, and incident-ready runbooks that enable sustained iteration
• Drive a rigorous experimentation and measurement loop, partnering with product, data, and cross-functional teams to validate impact, diagnose regressions, and continuously improve performance
• Mentor and multiply the team, setting engineering standards, reviewing designs, coaching other engineers, and aligning across teams where changes require shared ownership

Requirements:

• Strong technical leadership and end-to-end ownership
• Ability to set direction, drive alignment, and deliver multi-quarter initiatives from design through launch and iteration
• Familiarity with SEO systems at scale
• Experience with crawling and indexing, content generation, templating, structured data, internal linking, canonicalization, and internationalization is a plus
• Data and experimentation rigor
• Comfort defining success metrics, running controlled experiments, analyzing results, and debugging performance changes (rankings, traffic, conversion)
• Operational excellence
• Experience building reliable pipelines and services with strong observability, alerting, and incident-ready runbooks
• Systems thinking across the stack
• Able to reason about tradeoffs across ingestion, storage, serving, and quality controls, and to design durable architectures
• Cross-functional partnership
• Able to collaborate tightly with Product, Data, and Design, and influence decisions without authority