Vice President of Engineering at Search Atlas

Position Vice President of Engineering
Posted 19 May 2026
Expired 18 Jun 2026
Company Search Atlas
Location United States | US
Job Type Full Time

Job Description:

Latest job information from Search Atlas for the position of Vice President of Engineering. If the Vice President of Engineering vacancy in United States matches your qualifications, please submit your latest application or CV directly through the updated Jobkos job portal.

Please note that applying for a job may not always be easy, as new candidates must meet certain qualifications and requirements set by the company. We hope the career opportunity at Search Atlas for the position of Vice President of Engineering below matches your qualifications.

Search Atlas: Frontier Agentic Systems at Scale

$34M ARR | Bootstrapped | Elite Technical Operator

Location: San Francisco, CA (In-Person/Hybrid – Non-Negotiable)

Reports to: CEO (Manick Bhan)

The Mission: Scale the Engine from $34M to $100M ARR


The Moment

Search Atlas bootstrapped to $34M ARR by solving a problem most companies don't even attempt: autonomous marketing execution at enterprise scale.

We've cracked the code on daily autonomous deployment. We've proven that AI can generate, review, and ship production code reliably. We've scaled agentic systems to orchestrate hundreds of integrated services.

Now we're hitting the walls that only frontier companies face. The problems we're solving, perpetual agent coordination, cost-quality tradeoffs in LLM orchestration, distributed state management in autonomous systems, aren't taught in universities or discussed in most engineering organizations.

You're the person who's stared into these kinds of problems before.

We're not hiring a traditional VP. We're hiring an engineer who happens to lead, in the mold of Staff+ ICs at Anthropic, OpenAI, or the infrastructure teams at hyperscalers.


What You'll Actually Do (The Reality, Not the Fantasy)Daily Technical Reality (60% of your time)
  • Whiteboard architecture for systems running autonomous agents continuously, where every architectural decision impacts token costs, execution latency, and quality;
  • Review critical-path code in our agentic orchestration layer, not to micromanage, but because decisions here ripple to millions of requests;
  • Solve distributed systems problems that arise when coordinating multiple LLM-based agents with bounded autonomy, managing context windows, and optimizing state persistence;
  • Unblock engineers by doing hands-on technical work: refactoring a bottleneck, designing a new subsystem, debugging a production incident that requires deep systems thinking
  • Make real-time tradeoff decisions: Cost vs. quality. Speed vs. reliability. Cheaper models vs. frontier models. You'll spend time analyzing token efficiency, model performance, and execution patterns.
  • Code daily. Not ceremonial code reviews or architecture docs. Real code. You ship features, you optimize critical paths, you own the forensics when something breaks.
Leadership & Scaling Reality (40% of your time)
  • Lead 100+ engineers through hands-on mentorship, not management theater. Your team gets better by watching you solve a hard problem, not by sitting through standup meetings.
  • Identify and develop the next generation of technical leaders. You know how to spot an operator in 15 minutes and distinguish them from someone who looks good in meetings.
  • Set technical standards that elevate the entire organization. TDD, trunk-based development, aggressive deployment cadence, not as buzzwords, but as lived practice.
  • Shape engineering culture around ownership: end-to-end responsibility, no project managers, no blame games. Engineers own what they build, all the way to production and monitoring.

The Technical Context (What You're Walking Into)The Complexity You'll FaceMulti-Agent Orchestration at Scale:
  • Coordinating autonomous agents across dozens of decision points
  • Managing context window constraints while maintaining quality
  • Designing agent architecture where each component must be reliable (failure in one agent cascades)
  • Balancing tool availability vs. token efficiency vs. execution speed
LLM-Driven Code Generation in Production:
  • ~70% of our production code is generated by agentic systems
  • Continuous deployment of AI-generated changes (daily releases)
  • Evaluation frameworks that catch quality degradation before it reaches production
  • Prompt versioning, golden datasets, and automated testing for model changes
  • Understanding when to use different models for different tasks, optimizing for cost and quality
Long-Running Autonomous Systems:
  • Agents that need to operate perpetually, learning from each execution
  • State management across distributed agents without degradation
  • Memory constraints in systems designed to run for days/weeks
  • Error recovery and circuit breakers when things inevitably break
Cost-Quality-Speed Trifecta:
  • Managing token costs at scale (millions of LLM calls daily)
  • Quality degradation when moving away from frontier models
  • Latency requirements (sub-100ms critical path)
  • Architectural decisions that compound costs: choosing the wrong model, over-contextualizing agents, or poor tool management can cost millions monthly
Integration Complexity:
  • Orchestrating dozens of microservices as "tools" available to agents
  • Handling microservice reliability, failures, and inconsistent responses
  • Designing APIs that agents can reliably interact with
  • Managing the blast radius of changes across tightly coupled systems
The Stack You'll InheritCore Infrastructure:
  • Backend: Python (Django, FastAPI), async processing at massive scale (Celery/RQ)
  • Data Layer: PostgreSQL (transactional), ClickHouse (analytics), Elasticsearch, Redis
  • Compute: Kubernetes, Docker, multi-region coordination
  • Monitoring: Datadog, Sentry, Grafana (real-time visibility into agentic systems)
  • AI/ML: Vector databases, LLM APIs (Anthropic, OpenAI, Google), prompt management, evaluation frameworks
What Makes It Hard:
  • Not a typical SaaS stack, this is a systems company built for continuous autonomous execution
  • Scale you can't think your way out of; you have to engineer solutions
  • Tight coupling between business logic, AI systems, and infrastructure (changes in one layer affect all)
  • Real-time requirements competing with cost constraints

Who We're Actually Looking ForThe Profile

You have 10+ years of shipping production code, with 3+ years of hands-on technical leadership scaling engineering organizations from 30-100+ people. But here's the catch: you didn't stop coding when you became a leader. You're the person who:

  • Has operated at frontier: You've worked at Anthropic, OpenAI, a major hyperscaler, or a well-funded startup solving problems at the edge of what's technically possible
  • Understands agentic systems (not as theory, but from shipping production code): Multi-agent orchestration, LLM integration, reliability under uncertainty, cost optimization in AI systems
  • Has hit scaling walls you had to engineer your way out of: Token management, context window constraints, perpetual system design, distributed state, cost-quality tradeoffs
  • Lives and breathes shipping: You measure cycle time, deployment frequency, MTTR. You see waste and immediately think "how do we eliminate this?"
  • Attracts elite engineers: The top 1% of SF engineers want to work for you because they know you'll make them better. You have a reputation for technical rigor and mentorship through action.
  • Combines depth with breadth: You're comfortable reviewing code at any layer - infrastructure, backend, frontend, ML ops. You know when you're out of your depth and have no ego about learning.
  • Thinks like a founder: You understand unit economics, customer impact, and how engineering decisions compound. You're not optimizing for resume-building; you're optimizing for what matters.
What You're Not
  • A manager who delegates all code to direct reports
  • Someone who measures success in headcount or org charts
  • A process engineer ("let's add more meetings to align on decisions")
  • A person who needs a big title to feel important
  • Someone uncomfortable with ambiguity or unclear priorities
  • A politics player (we don't have room for that)

What Success Looks Like (Year 1 & Beyond)In the First 90 Days
  • You've mapped the technical landscape: where the bottlenecks are, which systems are fragile, where we're overspending on compute or tokens
  • You've identified 3-5 technical leaders on the team and are working with them directly
  • You've shipped at least one meaningful piece of code (not ceremonial—something that improves the system)
  • You've had "technical sparring" sessions with Manick where you've pushed back on decisions and earned trust through depth
In Year 1
  • Engineering velocity has noticeably increased: faster cycle times, more confident deployments, fewer surprise production incidents
  • The quality bar has risen: evals are more rigorous, code reviews are sharper, but you've done this through mentorship, not rules
  • You've solved at least one major technical problem that was blocking the organization: a scaling bottleneck, a reliability issue, a cost problem
  • You've hired 5-10 exceptional engineers who all say "I came to work for (you), not the company"
  • You've reduced technical debt in critical systems while shipping features
  • The organization runs tighter, faster, with less friction
In Years 2-3
  • We've scaled to $75-100M ARR with engineering quality improving, not degrading
  • You've developed 3-4 technical leaders who could step into your role
  • The agentic systems we've pioneered are industry-leading—harder to copy than our product features
  • We've solved the hard technical problems that are currently blocking us, and we're now solving the next level of hard problems
  • You own a significant piece of equity in a profitable, high-growth company


The Role in NumbersScale You'll Touch:

  • 100+ engineers across backend, infrastructure, ML ops, and frontend
  • Millions of autonomous executions daily
  • Sub-100ms latency requirements on critical path
  • Multiple terabytes of data processed and stored
  • 99.99% uptime requirements in production
Technical Decisions You'll Make:
  • Architecture for distributed agents (how they coordinate, share state, handle failures)
  • LLM strategy: which models for which use cases, how to optimize cost while maintaining quality
  • Infrastructure: how to scale Kubernetes, optimize database performance, manage cloud costs
  • Code generation reliability: how to make AI-generated code safe for production
  • Team growth: hiring, mentorship, and technical track allocation

The PartnershipCompensation & Benefits
  • Base: $200,000–$500,000+ (based on technical depth, leadership track record, and frontier experience)
  • Equity: Meaningful ownership stake in a profitable, bootstrapped, high-growth company (this is real equity, not water-downed stock options)
  • Benefits: 100% medical, 99% dental/vision, unlimited PTO, paid parental leave, 401(k), pet insurance, wellness stipend
  • The Edge: Company-paid professional development ($500/quarter), zero-politics environment, direct access to CEO/founders
How You'll Work
  • Location: San Francisco-based, hybrid (2-3 days/week in-office for whiteboarding, collaboration; flexible remote for focused technical work)
  • Rhythm: Weekly releases, continuous measurement, end-to-end ownership
  • Culture: Radical candor, high expectations, no bureaucracy, shipping obsession
  • Access: Direct to founders, executive team, and decision-makers (no middle management filtering)

The Interview Process

This isn't a typical hiring funnel. We're looking for mutual fit, and we move fast with the right person.

Round 1: Technical Depth
  • 90 minutes of deep technical discussion
  • We discuss distributed systems, agentic architecture, scaling challenges, and the tradeoffs you'd make
  • Be prepared to discuss hard problems you've solved (not case studies, but real problems from your career)
  • We want to hear about failures and what you learned
Round 2: Leadership & Vision
  • Conversation about how you lead, how you build teams, and how you think about scaling organizations
  • Discussion about what kind of culture and engineering practices you'd bring
  • What would you change about our engineering organization if you could start tomorrow?
  • What constraints would make you uncomfortable, and what would excite you?
Round 3: Founder Session (Technical Sparring)
  • Direct conversation with Manick about the future of agentic AI, technical strategy, and product vision
  • This is where mutual fit gets tested: Can you debate with him? Do you push back when you disagree? Do you understand the tradeoffs?
  • No performance theater here—just technical depth and strategic thinking

Timeline: If we find the right fit, we move fast. We've been known to move from first conversation to offer in 2-3 weeks.


One More Thing

This role is genuinely hard. The problems we're solving are at the frontier of what's technically possible with agentic systems and AI at scale. You'll hit moments where you're not sure how to proceed. You'll make decisions with incomplete information. You'll have to do technical work that stretches you.

That's exactly why we need you.

If you've stared into problems this hard before, if you've shipped systems at this scale, if you've built teams that get better by watching you work and if you're ready to do it again, let's talk.


About Search Atlas

We build autonomous marketing software for Fortune 500s and high-growth startups:

OTTO SEO - Fully autonomous technical optimization

Content Genius - Semantic AI content generation

Site Explorer - Real-time search intelligence

BrandVault - AI-driven knowledge graphs

GBP Galactic - Local SEO automation

Smart Ads - Autonomous PPC management

Recognition: Inc. 5000, Nevada's #1 Small Business Workplace, Great Place to Work Certified

$34M ARR. Bootstrapped. Profitable. Growing fast.


Apply with evidence of craft. No cover letters. Just systems, code, and results.

Search Atlas is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all team members.

Must be currently authorized to work in the US without future sponsorship.

Job Info:

  • Company: Search Atlas
  • Position: Vice President of Engineering
  • Work Location: United States
  • Country: US

How to Submit an Application:

After reading and understanding the criteria and minimum qualification requirements explained in the job information Vice President of Engineering at the office United States above, immediately complete the job application files such as a job application letter, CV, photocopy of diploma, transcript, and other supplements as explained above. Submit via the Next Page link below.

THIS JOB POSTING HAS EXPIRED (Over 30 days ago).
Please search for the latest job opportunities on our Homepage.

Similar Job Vacancies