> Markdown version of [/jobs/ext/4619082-vp-engineering](https://www.wearedevelopers.com/jobs/ext/4619082-vp-engineering). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # VP, Engineering - **Company:** Franchise World Headquarters, LLC - **Location:** Shelton, CT, United States - **Experience:** Expert - **Contract:** Franchise - **Skills:** Amazon Web Services, Microsoft Azure, Software as a Service, Cloud Computing, Code Review, Amazon DynamoDB, Mobile Application Software, SQL Azure, Release Management, Data Streaming, Delivery Pipeline, Technical Debt, AWS Fargate, React Native, Functional Programming, Serverless Computing - **Published:** November 7, 2026 - **Apply:** https://www.juju.com/job/28_25304_cc07d96f6ca475932b601e87e74e0ed7 ## About the Role * 10+ years in engineering leadership, including 5+ years managing managers within an organization of comparable scale (40+ engineers, including technical support). * Direct ownership of an engineering budget - headcount, tooling, and cloud spend - with a track record of running it like a P&L rather than a cost center. * Experience designing and evolving org structure as a team scales, not just operating within a structure someone else built. * Direct experience delivering consumer-facing mobile applications; React Native experience strongly preferred. * Hands-on architecture experience on AWS, including serverless and containerized services such as Lambda, Fargate, and DynamoDB. * Experience leading engineering for multi-unit retail or restaurant scale. * A demonstrated track record on the people side of engineering - hiring, developing, and holding a performance bar, including making the hard calls when someone isn't meeting it. * Strong partnership instincts - comfortable operating as a peer to product, marketing, and business stakeholders, and defending engineering's cost and priorities in those conversations. ## Description Subway is looking for a Vice President of Engineering to lead the engineering organization behind our franchisee-facing in-restaurant experience - the Point-of-sale, Menu management, Payments and other applications that connect them. This leader is accountable for the outcomes of that organization: what it ships, what it costs, how reliable it is, and how well it develops and retains its people. You'll own technical strategy, the engineering budget, and org design for a team of roughly 50, partnering closely with the Chief Technology Officer and product leadership to turn roadmap into results guests can feel., * POS: deployed in 39 countries, including release quality, performance, and store configuration with peripherals including Kitchen Display Systems, Printers, Cash Drawers. * Menu Management: the menu platform that feeds POS and other channels. * Payments applications for both in-store payments and digital payments * A number of applications that support franchisees including restaurant management, learning platform, etc. * The engineering relationship with our digital and corporates systems, including integration, data flow, and roadmap delivery. * Cloud infrastructure: our AWS and Azure environments - Lambda, Fargate, DynamoDB, Azure SQL - including architecture decisions on scalability, resilience, and cost. * Technical support: the team and processes that keep franchisee-facing properties running, including incident response and escalation., * Set technical strategy and architecture direction across the franchisee engineering teams - and own what it delivers, not just how it's staffed. * Own the roadmap-to-delivery pipeline: planning, prioritization, release management, and the tradeoffs between feature work, reliability, and technical debt. * Make and defend build-vs-buy and platform decisions across the AWS stack, balancing scalability, resilience, security, and cost. Budget & Cost Management * Own the engineering budget end to end - headcount cost, tooling and SaaS spend, and Azure/AWS cloud spend - and run it like a P&L, not a request line. * Own vendor economics for Azure, AWS, and other engineering tools: negotiate, benchmark, and cut what isn't earning its cost. * Build the annual headcount and budget plan with the Chief Technology Officer, and re-forecast it as priorities shift. * Know your unit economics - cost per release, cost per engineer, cloud cost per active user - and use them to make decisions, not just report them., * Design and evolve the org structure as the team scales - spans of control, management layers, when to split or merge teams - rather than defaulting to the structure you inherit. * Own the full people lifecycle for your organization: hiring, onboarding, career development and promotion, performance management, and retention of your best people. * Build a culture of ownership and accountability, where engineers and managers own outcomes rather than tickets, and problems surface early rather than late. * Directly manage and develop your engineering managers and directors; own their growth and the health of their teams. Engineering Practices & Reliability * Own incident management and on-call: response, escalation, postmortems, and the follow-through that prevents repeat incidents. * Set and hold the bar on code review, testing, documentation, and security practices across the organization. * Own capacity planning and technical debt - make the tradeoff between roadmap and system health explicit and defensible, rather than letting debt accumulate by default. * Establish the SLAs/SLOs that matter for a guest-facing digital platform, and own the outcome when they're missed. Executive Partnership * Partner with the Chief Technology Officer and product leadership to translate business goals into engineering OKRs, and report against them in business terms, not activity terms. * Represent engineering in executive conversations - including tradeoffs, risk, and cost - with the same rigor you'd expect from a peer running a P&L.