ezCater

Frontend Engineer

• Own front-end platform and architecture across Next.js (App Router), React, TypeScript, and Astro, including micro-frontend composition strategies, monorepo, shared design system, cross-MFE state management, and MFE shell orchestrator.
• Define the opinionated path for building and deploying front-end applications — CI/CD, observability, accessibility, performance budgets, and contract testing — across both the marketplace and internal tools channels.
• Own the full ordering experience from discovery, personalization, and menu browsing through cart, checkout, and payment, consuming headless backend APIs through BFF layers.
• Drive AI-native front-end development, including design-to-code pipelines (Figma, Claude Design, v0), AI-assisted development against organizational context, and AI-powered product experiences such as personalized recommendations, intelligent search, and conversational ordering.
• Ensure front ends are machine-readable and API-first to serve AI agents alongside human users, with awareness of emerging commerce protocols (MCP, Universal Commerce Protocol).
• Own the design system as infrastructure — design tokens, theming, cross-platform consistency — packaged and documented for both human engineers and AI code generation workflows.
• Lead and develop three engineering teams, scaling the organization as it grows; recruit and develop engineers and managers, including from minimal staffing.
• Hold a high technical bar: review front-end system designs, challenge architectural decisions, and identify performance issues from technical signals.

Director of Engineering, Front-end and Ordering Platform

Compliance

• Lead control program maturity
• Build continuous control monitoring and automation
• Expand data security policy and program quality
• Drive operational quality improvements
• Lead through influence and systems thinking

Staff GRC Engineer

Product Designer

• Lead design independently across large, complex projects: owning the work end-to-end from discovery and framing through execution and iteration.
• Partner closely with Product and Engineering to shape roadmaps and goals from the user's perspective, tying work to broader product and business outcomes.
• Define how products and experiences connect and work together across your area, ensuring coherence across surfaces, users, and use cases.
• Use data and research to drive decisions: define success metrics, partner with Research and Analytics to validate work, and socialize learnings across the team.
• Raise the bar on craft by setting the quality standard for your area, documenting and socializing new patterns, and contributing to the design system.
• Mentor and give regular, actionable feedback to designers around you, helping elevate the work across the team.
• Build and maintain strong relationships with cross-functional partners, bringing them along with clear storytelling and well-crafted artifacts.
• Integrate AI thoughtfully into your design workflow, knowing when it accelerates quality and when it doesn't, and share effective approaches with your team.

Staff Product Designer, Supply

• Define and drive the design strategy for the Supply ecosystem: setting a coherent, user-centered vision that spans multiple product areas and connects to ezCater's broader product and business goals.
• Co-create roadmaps with Product, Engineering, and Data leadership, grounding priorities in a deep understanding of catering partner needs, operational realities, and business health metrics.
• Lead cross-domain design initiatives with company-level impact, bringing clarity to ambiguous, multi-team efforts and earning alignment from senior stakeholders.
• Set the quality bar across UX, visual design, content, and interaction by establishing direction for other designers and advocating for the evolution of our design principles and systems as the Supply space grows.
• Set design direction for your cross-functional team, running critiques and design reviews, making a clear and defensible case for decisions, and creating clarity in ambiguous situations.
• Identify and frame high-leverage problem spaces before they're on the roadmap, shaping what teams work on, not just how it looks.
• Build a culture of data-informed design decisions: track record of using qualitative and quantitative data to drive impact, and holding the work accountable to measurable outcomes.
• Mentor and coach designers across the Supply org, elevating craft and strategic thinking across the team.
• Raise the bar for how design is communicated and documented: crafting narratives that land with senior leadership and setting the standard for how the team presents its work.
• Champion the responsible and high-quality use of AI in design workflows and helping shape how the Supply design team adopts AI capabilities.

Principal Product Designer, Supply

Full-stack Engineer

• Own the Search Engine architecture: technology direction (Vespa-based), document schema, query serving, and operational model
• Own and build the Indexing Pipeline: Temporal-orchestrated workflows that ingest, validate, transform, and write data into the search engine and availability store
• Own Availability: zone-based delivery filtering, schedule matching, and the data model that powers it- extracted from the legacy monolith and re-implemented.
• Own the Two-Stage Filtering Architecture: zone-based availability filtering followed by Vespa filtering and ranking
• Drive search relevance and ranking strategy across ordering contexts and customer types, in collaboration with product and data
• Define clear, well-versioned APIs and contracts for how search and availability are consumed across all channels
• Manage migration sequencing and risk across the phased rollout (Typeahead, Availability, Core Search)
• Build a measurement and experimentation foundation supporting full-funnel evaluation, from CTR through order fulfillment
• Lead through collaborative design: white-boarding, technical discussions, and aligning teams around clear architectural decisions
• Partner with Platform Engineering on shared service patterns, Temporal, observability, secrets, and CI/CD
• Partner with product, data, and downstream consumers on relevance, ranking signals, and API contracts
• Act as a technical multiplier through design reviews, code reviews, architectural guidance, and mentorship

Staff Software Engineer, Search Platform

Product Manager

• Drive the vision and develop a roadmap for the restaurant partner platform
• Expand reporting capabilities and provide insights to restaurant partners
• Tell a compelling story using research and data to evangelize the roadmap
• Build deep empathy for ezCater users and become their biggest champion
• Lead product initiatives with cross-functional teams
• Continuously identify areas for innovation and implement strategies
• Create and monitor ongoing metrics that measure success
• Travel to Boston quarterly for planning and business reviews
• Have fun building impactful software

Principal Product Manager, Supplier Platform

Onboarding Specialist

• Synthesize Information: You’ll work to onboard new and existing catering partners using our partner-facing Guided Onboarding tool as well as other automation tooling to translate data points into Freedom to create stores.
• Prioritize: You’ll juggle multiple work streams along with competing stakeholder priorities and SLAs.
• Uphold: We have onboarding requirements that are proven to set our partners up for success. We’ll need you to be well versed and comfortable with explaining “the why” behind the requirements and upholding them, both internally and externally.
• Communicate: You’ll work with restaurant partners directly; from those who want to expand their footprint on our Marketplace to new partners who are eager to join. You’ll need to go beyond helpful to make every catering partner’s experience easy and efficient.
• Collaborate: Solution-oriented feedback is our bread and butter. We’ll need your help in improving our process and tools.
• Make an Impact: You’ll make an immediate impact on our company goals and will be an essential part of the success of thousands of restaurant partners.
• Identify, test, and support the implementation of process improvements in our team tools.
• Get Scrappy: You’ll be at the forefront of the testing & implementation of new processes and we’ll need you to be nimble, solution-oriented, and vocal with feedback.

Technical Program Manager

• Drive each workstream through milestone planning, baseline, and replan cycles; ensure capability milestones, dependencies, and target dates are clearly documented and current.
• Manage the critical path and surface schedule risk early; partner with workstream tech leads to negotiate trade-offs when a milestone slips.
• Maintain the Work Breakdown Structure (WBS) from workstream → capability → milestone, and keep the program schedule and goals-to-milestones mapping in sync.
• Identify and track cross-workstream dependencies (e.g., User/Identity ↔ Payments on user-payment-method association; MDM ↔ User/Identity on user authority; Golden Path ↔ every downstream workstream on the cookie-cutter service template).
• Drive stub/contract-first patterns so workstreams can move in parallel rather than serially; escalate to the Core Team when a dependency becomes a blocker.
• Run the cadence (working sessions, design reviews, integration checkpoints) needed to keep dependencies from slipping.
• Maintain the program-wide view of resourcing across all workstreams — FTE allocations, contractor placements (BairesDev, Slalom, and others), and open roles — and keep the picture current as workstreams ramp.
• Surface resource bottlenecks early: where a workstream is under-resourced for its scope, where a critical hire is gating downstream velocity (e.g., AI DX Lead, Platform SEM, workstream tech leads), and where contractor capacity is outpacing the team’s ability to absorb it.
• Partner with workstream tech leads and the hiring side of the org to coordinate onboarding of new FTEs and contractors — ensuring access, ramp plans, and first assignments are in place so people are productive in weeks, not months.
• Track contractor engagements (start dates, end dates, scope, renewal decisions) and ensure transitions in and out of the program don’t leave knowledge gaps.
• Own the Nova program Heartbeat report (biweekly written status to stakeholders) and the weekly executive roll-up — assemble inputs from workstream leads, draft, and publish.
• Maintain the RAID log (Risks, Assumptions, Issues, Dependencies) and the risk register; ensure risk owners are named, mitigation plans are current, and escalations happen on time.
• Run the Core Team cadence: agendas, decisions, action items, follow-through; make sure decisions are documented and reachable.
• Communicate program status and risks honestly — to workstream leads, the Core Team, and (where appropriate) ELT stakeholders.
• Operate the scope and schedule change control process: classify changes (within-milestone, cross-workstream, program-level), route them to the right decision authority, and document outcomes.
• Maintain the program decision log; ensure architectural and program-level decisions are recorded and accessible.
• Steward the program-management artifacts (schedule, RAID, risk register, communications plan, stakeholder register) so they remain trustworthy operating tools rather than wallpaper.
• Coach new workstream tech leads through milestone planning and the Nova program rhythm; help them produce a credible baselined milestone plan within their first 4-6 weeks.
• Identify and fix friction in the program operating model — meeting overhead, status reporting load, tooling gaps — so workstreams spend their time building, not reporting.
• Facilitate planning and timing of transitions as Nova workstreams move from dedicated (or hybrid) program staffing back into the permanent Pillars and Pods organizational structure — typically once a workstream’s initial services are production-operational and out of intensive build.
• Partner with Pillar leadership to identify the right transition point per workstream, sequence transitions so they don’t collide with Pillar BAU commitments, and confirm receiving Pods are ready (capacity, on-call, ownership clarity).
• Coordinate the handoff itself: service ownership, documentation, on-call rotations, backlog transfer, and any residual Nova-program obligations — so nothing falls between Nova and the receiving Pillar.
• Maintain a forward view of upcoming transitions in the program schedule so they are planned for, not surprises.