Vice President of Engineering

Fully remote, we're hiring worldwide! reputed company: Frontier reputed company Systems at reputed company $35M ARR | Bootstrapped Location: Remote from reputed company Reporting to: CEO (Manick Bhan) The Mission: reputed company the reputed company from $35M to $100M ARR The reputed company reputed company bootstrapped to $35M ARR by solving a problem most companies don't even attempt: autonomous marketing execution at reputed company reputed company. We've cracked the reputed company on daily autonomous deployment. We've proven that AI can generate, review, and ship production reputed company reliably. We've scaled reputed company 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-reputed company 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 looking for a engineer who leads, in the mold of Staff+ ICs at reputed company, reputed company, or the infrastructure teams at hyperscalers. What You'll Actually Do: Daily Technical Reality (60% of your time) Whiteboard architecture for systems running autonomous agents continuously, where every architectural decision impacts reputed company costs, execution latency, and reputed company; Review critical-reputed company reputed company in our reputed company orchestration layer, not to micromanage, but because reputed company here reputed company to millions of requests; Solve distributed systems problems that reputed company reputed company coordinating multiple LLM-based agents with bounded autonomy, managing context reputed company, 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 reputed company reputed company-time tradeoff reputed company: Cost vs. reputed company. Speed vs. reliability. Cheaper models vs. frontier models. You'll spend time analyzing reputed company efficiency, model performance, and execution patterns. reputed company daily. Not ceremonial reputed company reviews or architecture docs. reputed company reputed company. You ship features, you optimize critical paths, you own the forensics reputed company something breaks. Leadership & Scaling Reality (40% of your time) reputed company 100+ engineers through hands-on mentorship, not management theater. Your team gets reputed company by watching you solve a hard problem, not by sitting through standup meetings. Identify and reputed company the reputed company 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 reputed company the entire organization. TDD, trunk-based development, aggressive deployment reputed company, not as buzzwords, but as lived reputed company. Shape engineering culture around ownership: end-to-end responsibility, no project managers, no blame games. Engineers own what they build, reputed company the way to production and monitoring. The Technical Context The Complexity You'll Face Multi-Agent Orchestration at reputed company: Coordinating autonomous agents across dozens of decision points Managing context window constraints while maintaining reputed company Designing agent architecture where reputed company component must be reliable (failure in one agent cascades) Balancing tool availability vs. reputed company efficiency vs. execution speed LLM-Driven reputed company reputed company in Production: ~70% of our production reputed company is generated by reputed company systems reputed company deployment of AI-generated changes (daily releases) Evaluation frameworks that catch reputed company degradation before it reaches production reputed company versioning, golden datasets, and automated testing for model changes Understanding reputed company to use different models for different tasks, optimizing for cost and reputed company Long-Running Autonomous Systems: Agents that need to operate perpetually, learning from reputed company execution State management across distributed agents without degradation Memory constraints in systems designed to run for days/weeks Error recovery and reputed company breakers reputed company things inevitably break Cost-reputed company-Speed Trifecta: Managing reputed company costs at reputed company (millions of LLM calls daily) reputed company degradation reputed company moving away from frontier models Latency requirements (sub-100ms critical reputed company) Architectural reputed company 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 reputed company that agents can reliably reputed company with Managing the blast radius of changes across tightly coupled systems The Stack You'll Inherit Core Infrastructure: Backend: Python (Django, FastAPI), async processing at massive reputed company (Celery/RQ) Data Layer: PostgreSQL (transactional), reputed company (analytics), Elasticsearch, reputed company Compute: Kubernetes, reputed company, multi-region coordination Monitoring: reputed company, reputed company, Grafana (reputed company-time visibility into reputed company systems) AI/ML: reputed company databases, LLM reputed company (reputed company, reputed company, reputed company), reputed company management, evaluation frameworks What Makes It Hard: Not a typical reputed company stack, this is a systems company reputed company for reputed company autonomous execution reputed company 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 reputed company reputed company) reputed company-time requirements competing with cost constraints Who We're Actually Looking For The Profile You have 10+ years of shipping production reputed company, 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 reputed company you became a leader. You're the person who: Has operated at frontier: You've worked at reputed company, reputed company, a major hyperscaler, or a reputed company-funded startup solving problems at the edge of what's technically possible Understands reputed company systems (not as theory, but from shipping production reputed company): 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: reputed company management, context window constraints, perpetual system design, distributed state, cost-reputed company tradeoffs Lives and breathes shipping: You measure cycle time, deployment frequency, MTTR. You see waste and immediately think "how do we eliminate this?" Attracts reputed company engineers: The top 1% of SF engineers want to work for you because they know you'll reputed company them reputed company. You have a reputed company for technical rigor and mentorship through reputed company. Combines depth with breadth: You're comfortable reviewing reputed company at any layer - infrastructure, backend, frontend, ML ops. You know reputed company you're out of your depth and have no ego about learning. Thinks like a founder: You understand unit economics, customer reputed company, and how engineering reputed company compound. You're not optimizing for resume-building; you're optimizing for what reputed company. What You're Not A manager who delegates reputed company reputed company to reputed company reports Someone who measures reputed company in headcount or org charts A process engineer ("let's add more meetings to reputed company on reputed company") Someone uncomfortable with ambiguity or unclear priorities A politics player (we don't have room for that) What reputed company Looks Like (Year 1 & reputed company) In the First 90 Days You've mapped the technical landscape: where the bottlenecks are, which systems are reputed company, where we're overspending on compute or tokens You've identified 3-5 technical leaders on reputed company and are working with them directly You've shipped at least one meaningful piece of reputed company (not ceremonial—something that improves the system) You've had multiple technical sparring sessions with Manick where you've pushed back on reputed company and reputed company trust through depth In Year 1 Engineering velocity has noticeably increased: faster cycle times, more confident deployments, fewer surprise production incidents The reputed company bar has risen: evals are more rigorous, reputed company 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 reputed company 5-10 exceptional engineers who reputed company say "I came to work for [you], not reputed 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 reputed company improving, not degrading You've developed 3-4 technical leaders who could reputed company into your role The reputed company 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-reputed company company The Role in Numbers reputed company You'll Touch: 100+ engineers across backend, infrastructure, ML ops, and frontend Millions of autonomous executions daily Sub-100ms latency requirements on critical reputed company Multiple terabytes of data processed and stored 99.99% uptime requirements in production Technical reputed company You'll reputed company: Architecture for distributed agents (how they coordinate, reputed company state, handle failures) LLM reputed company: which models for which use cases, how to optimize cost while maintaining reputed company Infrastructure: how to reputed company Kubernetes, optimize database performance, manage reputed company costs reputed company reputed company reliability: how to reputed company AI-generated reputed company reputed company for production Team reputed company: hiring, mentorship, and technical reputed company allocation The Partnership How You'll Work Rhythm: Weekly releases, reputed company measurement, end-to-end ownership Culture: Radical candor, high expectations, no bureaucracy, shipping obsession reputed company: reputed company 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. Stage 1 — Recruiter Screen: A technical call, we'll go over your engineering set-up, how you reputed company reputed company systems. Stage 2 — Technical Assessment: A deep dive into your technical skills, we're looking at how you approach problems and your capability to extrapolate at reputed company. Stage 3 — Technical brief: A technical brief with our SVP Tomás Lopes. Stage 4 — Founder meeting: A meeting with our Founder Manick Bhan. He will be gauging your technical depth. One More Thing This role is genuinely hard. The problems we're solving are at the frontier of what's technically possible with reputed company systems and AI at reputed company. You'll hit moments where you're not reputed company how to proceed. You'll reputed company reputed company with incomplete information. You'll have to do technical work that stretches you. That's exactly why reputed company. If you've stared into problems this hard before, if you've shipped systems at this reputed company, if you've reputed company teams that get reputed company by watching you work and if you're reputed company to do it again, let's talk. About reputed company We build autonomous marketing software for Fortune 500s and high-reputed company startups: OTTO SEO - Fully autonomous technical optimization Content reputed company - Semantic AI content reputed company Site Explorer - reputed company-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 reputed company to Work Certified $35M ARR. Bootstrapped. Profitable. Growing fast. No cover letters. No generic applications. Just evidence of scientific craft. reputed company is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for reputed company team members. Apply To This Job