Senior Manager, Software Engineering

Foodsmart

32d•$200,000 - $235,000•Remote

About The Position

Foodsmart's Engineering, Product, and Design (EPD) team builds the telenutrition and foodcare platform used by members, providers, and partners. As a Senior Engineering Manager, you will lead and grow an engineering organization of approximately 16 engineers, setting technical direction and management practices that keep the team shipping reliable, high-quality software. You'll partner closely with product and design to translate roadmap priorities into well-architected systems, champion the adoption of AI throughout our engineering practices, and raise the bar on our full-stack web platform.

Requirements

10+ years of software engineering experience, including 5+ years managing engineering teams, with a track record leading 10+ engineers (startup or high-growth environment preferred).
Strong, hands-on AI-native development experience building products with agentic systems, LLM integrations, or AI-first architectures and a track record applying AI to both engineering workflows and product features.
A proven track record managing multiple engineering teams simultaneously, with clear accountability for delivery, quality, and velocity.
Experience managing cross-team dependencies and risk in a fast-moving, multi-pod environment.
Experience running engineering delivery with Agile/Lean practices (Scrum/Kanban) using tools like Jira and Confluence.
A track record of setting technical direction and making sound architecture decisions for scalable, full-stack web applications.
Deep working knowledge of our core stack: React.js, TypeScript, Node.js, JavaScript, AWS (Lambda, EC2, RDS, SQS, DynamoDB), PostgreSQL, and Redshift, along with Docker/Kubernetes for containerized, orchestrated deployments, and familiarity with GraphQL and RESTful API design.
A strong outcome/value-oriented mindset, with a track record of tying engineering work to business impact.
Excellent mentorship and coaching skills, with genuine investment in developing people.
Strong communication and collaboration skills across technical and non-technical stakeholders.

Nice To Haves

Experience in regulated environments (healthcare/digital health preferred), with HIPAA/SOC 2 awareness and audit-friendly change management, is a plus.

Responsibilities

Lead AI-native development: Bring strong, hands-on AI experience to guide teams building AI-native software products architected around AI from the ground up spanning agentic workflows, LLM-powered services, and AI-assisted engineering practices, not just AI-adjacent features.
Own four AI pods end to end: Directly manage four AI-focused pods, each accountable for delivering specific features and outcomes. You own execution, delivery, quality, and velocity across all four.
Manage cross-pod dependencies and risk: Identify where pods' roadmaps intersect, sequence work to avoid bottlenecks, and proactively surface and mitigate risks before they threaten delivery.
Shape architecture: Participate in and help drive architecture reviews across our React.js/TypeScript, Node.js, AWS, PostgreSQL, and Redshift stack, ensuring decisions hold up for scalability, reliability, security, and maintainability, including in a HIPAA/SOC 2-aware environment.
Stay outcome-focused: Keep teams anchored to member and business impact rather than pure output, helping them prioritize the work that moves the needle.
Champion AI adoption: Drive the practical use of AI across engineering from AI-assisted development tooling to AI-powered product features, keeping the org current with emerging tools and practices.
Drive engineering excellence: Raise the bar on code quality, testing, observability, incident response, and CI/CD practices across the pods.
Mentor and develop talent: Coach engineers and tech leads at all levels, building the next generation of technical leadership inside the org.
Communicate and collaborate: Act as a clear, consistent communicator and trusted partner across engineering, product, design, and leadership, translating technical realities for non-technical stakeholders and vice versa.