Responsibilities
- Interfacing with users across all feedback channels in order to
- Report user issues to the engineering team
- Organize public facing user issues so that issues are
- Easy for users to find
- Easy for users to subscribe to
- Easy for users to give repro instructions on
- Easy for Warp engineers to repro
- Easy for Warp engineers to understand the impact of
- Respond to every user issue across all our feedback channels (not including public social posts)
- Discord
- GitHub
- Email
- Twitter DMs that are support/feedback related
- Responses should be as streamlined as possible and organized through a central system (e.g. Front)
- Sync public facing issues into our internal tracking system (linear) for Zach or a TPM to prioritize and assign
- Assign the correct project and labels, but leave priority empty
- When time allows, tries to repro issues before they make it to engineers — goals is for all new issues to have at least an attempted repro
- As much as possibly, automating the feedback collection and response process to make it more scalable (e.g. piping issues to Front app, discord bot, reporting top issues)
- Release management
- Run our weekly release process for both the desktop app and the server
- Work with engineers to compile and publish an accurate changelog
- Supporting the DA in keeping Documentation up-to-date
- Make sure our documentation is comprehensive and up to date
- Supporting the team on community efforts (i.e. community-ops)
- E.g. sourcing workflows, setting up orbit + other tools around community visibility
- Building discord bots
Not responsible for
- Social content (Twitter, YouTube, TikTok, etc)
- Writing code for the product, except possibly through our extension points
- Owning our developer community outside of user feedback (e.g. running Warp Ambassadors)
- Producing posts for content marketing
- Creating or running the overall bug triage process - this is for Zach or a PM or TPM