Office hours
AW-fis owrz
Regularly scheduled sessions where developers can ask questions and get live help from the product team or DevRel.
Office hours are scheduled times when developers can drop in and ask questions. A DevRel team member or engineer hosts the session (usually via video call) and answers questions live. Topics range from 'How do I set up authentication?' to 'What is the best architecture for my use case?'
Office hours build trust by making the team accessible. Developers feel supported knowing they can get live help if they are stuck. Even developers who never attend appreciate that the option exists.
The sessions also surface product issues in real-time. When a developer shares their screen and shows where they are stuck, the team sees the product through fresh eyes. This direct feedback is more valuable than any survey.
Examples
A company runs weekly developer office hours.
Every Thursday at 2pm ET, a DevRel engineer hosts a Zoom session. Developers join with questions. Attendance averages 15-25 people. Sessions are recorded and published. Some recordings get 500+ views from developers who could not attend live.
Office hours catch a usability issue.
A developer shares their screen during office hours. They cannot find the 'Create API key' button. The DevRel host realizes the button is hidden behind a dropdown that 5 other developers have also struggled with. They file a bug. The button is moved to a visible location.
Office hours build community connections.
Regular attendees start answering each other's questions. A senior developer mentors a junior one. The office hours become a micro-community. Two attendees even collaborate on an open source project related to the product.
In practice
Read more on the blog
Frequently asked questions
How often should you hold office hours?
Weekly is ideal. Biweekly works if the team is small. Less than biweekly and it does not become a habit for developers. Keep a consistent schedule (same day, same time) so developers can plan around it.
What if nobody shows up to office hours?
This is common early on. Promote it consistently. Use the time to create content (record a tutorial, answer common questions on camera). As the community grows, attendance will follow. Cancel only after 3+ months of consistent zero attendance.
Related terms
A group of developers who use a product and connect with each other to share knowledge, solve problems, and provide feedback.
The practice of building relationships between a company and its developer community through advocacy, content, and support.
How easy, productive, and enjoyable it is for developers to use a product, from documentation to API design to error messages.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.