Engineering at Frappe
summary
Frappe runs engineering with about 30 developers, juggling ERPNext, Frappe Cloud, Marketplace and new products while avoiding heavy process. A Kanban and a separate Solutions team both fail; custom work gets outsourced and teams merge back into product focus. Engineers gain wide autonomy so outcomes matter: a BI tool ships in three months, the stock module is refactored to much higher stability, and hiring favors strong GitHub histories or a take-home project. Mentors support, unblock and hire or fire.
AI-written summary Β· about
chapters (9)
- 0:00Introduction
- 0:37Scope of Work
- 1:37Activities
- 5:35Product Management
- 8:32Solution Culture
- 9:30Agency
- 10:36Freedom
- 13:32Mentor
- 15:10How do we find them
related talks
02mInterview with Vinay Kumar
27mScaling Engineering & Product Teams
10mKeynote: Frappe Lending
15mEngineering Culture and Developer Productivity
34mAn Engineering Team Where Everyone is a Leader
16mEngineering the Future with the Reliable Delivery Management
33mAn Engineering Team Where Everyone is a Leader
48mPanel Discusson: Road To Staff/Principal Engineer
