← Back to Jobs
Posted Jun 3, 2026

VP of Engineering (Venture Studio Team)

Engineering Lead - Attack Capital Core Requirements Experience: 6-8 years in fast-paced startups, with 2+ years leading teams • Managed 5-10 engineers (especially junior/mid-level developers) • Scaled products from 100 to 10,000+ customers • Worked in multi-product or platform companies Technical Skills Must-Have Stack: • Frontend: React, Next.js, TypeScript, Tailwind CSS • Backend: Node.js, Express, REST APIs, WebSockets • Database: PostgreSQL, Redis, query optimization • Cloud: GCP (Cloud Run, Cloud SQL, Pub/Sub, Cloud Functions) • DevOps: Docker, CI/CD pipelines, GitHub Actions AI/Automation Experience: • Integrated LLM APIs (OpenAI, Claude, Gemini) • Built Chrome extensions with real-time processing • Workflow automation (n8n, Zapier, or similar) • Experience with audio/video processing APIs Project Management Expertise Team Leadership: • Sprint planning and backlog grooming • Breaking down complex features into junior-friendly tasks • Code review processes that educate while maintaining velocity • 1:1 mentoring and skill development plans • Managing distributed/remote teams Productivity Systems: • Implemented engineering metrics (velocity, cycle time, PR turnaround) • Set up automated code quality gates (ESLint, Prettier, SonarQube) • Built documentation culture (ADRs, API docs, runbooks) • Experience with Linear/Jira, Notion, Slack workflows AI-Powered Development Practices Code Quality Automation: • GitHub Copilot/Cursor integration for team productivity • Automated PR reviews using AI tools • Set up automated testing (Jest, Cypress, Playwright) • Implemented error monitoring (Sentry, LogRocket) Reliability & Monitoring: • Built observability stack (Datadog, New Relic, or similar) • Implemented feature flags for safe rollouts • Zero-downtime deployment strategies • Incident response protocols and post-mortems Work Allocation Strategies For Junior Developers: • Created modular task structure (2-3 day deliverables) • Pair programming rotation schedules • Built internal tools/dashboards as learning projects • Established clear PR templates and review checklists Scaling Tactics: • Component library development for consistency • API standardization across products • Shared services architecture • Cross-product code reusability