Engineering Manager, Apps & APIs

What you might do in your first 6 months:

• Grow and lead a team of 4-7 direct reports: dig in and understand their work, their goals, and what’s in their way
• Establish team norms and a working culture that sets people up to do their best work with clear expectations and honest feedback
• Improve how the team works: drive clarity on priorities, healthier processes, better cross-functional handoffs
• Own the team’s execution roadmap and delivery: scope and sequence work, unblocking your team early and often
• Partner with Product to align your team’s priorities and goals with the overall Product roadmap and initiatives
• Help shape and ship our MCP server from early-stage to production-grade
• Drive a public API strategy that prioritizes reliability and developer experience
• Support and strengthen the delivery team behind our web application and agentic apps

Things you have experience in:

• Managing a team of globally-distributed software engineers - mentoring, coaching, and occasionally having the hard conversations
• Staying technical enough to be useful in architecture discussions and code reviews without being the bottleneck
• Translating ambiguous product goals into concrete engineering deliverables
• Shipping in a fast-paced SaaS environment where "good enough to learn from" beats "perfect but late"
• A strong technical background in web and API development (our app stack is Ruby on Rails, with Rails & Python APIs)
• Designing and shipping production APIs with real external consumers - you think about DevEx, versioning and reliability as much as you think about feature delivery

Things that should excite you that might scare off other folks:

• Owning the full customer-facing surface of a product with technical users: your users are developers, marketing analysts and data scientists - they notice when something isn’t right
• Building with emerging tech like MCP and agentic AI: you’re willing to make opinionated architectural bets in a landscape that is continually evolving
• Helping shape what “effective” looks like for an AI-native engineering team: defining the tools, guardrails, and standards that actually help us go faster
• Managing a remote, async-first team spread across time zones where clear written communication is essential
• Growing a team that's medium-sized today but won't stay that way forever

Hiring Process:

• Hiring Screen - discuss Recast, your background, and questions you have
• Hiring Manager Interview - casual, mutual-fit conversation