Building Engineering and Product Teams
Building Engineering and Product Teams analyzes the organizational structure and composition of modern-day engineering organizations in 2024. The report focuses on headcount ratios, the sequencing of key hires, workforce arrangements, talent attrition, and more.
How much of the R&D budget should be allocated to people?
- R&D typically comprises the largest portion of spend as companies scale to $25M. That plateaus to ~20-30% of revenue as companies reach critical scale
- Personnel costs comprise the largest portion (usually ~70-80% of total spend)
- For CTOs, setting up a strong organizational structure and operating model is a critical point of leverage
Engineering makes up ~80-90% of the total R&D headcount.
The remaining (~10-20%) goes to product.
How should CTOs negotiate engineering resources in a budget-constrained environment?
It's a tough problem, engineering can feel like a mysterious black box to the CEO/CFO. As the CTO, fostering discussions about engineering priorities and how that maps back to the broader goals of the organization is essential for building empathy and understanding of your resourcing needs. CTOs need to be the owner of engineering budget and understand how that maps back to business value, manage dependencies, and communicate how revenue maps back to resource allocation.
How should the make-up of product and engineering organizations evolve as organizations scale?
- Within the R&D organization, engineering makes up ~80-90% of the total R&D headcount. Product typically comprises ~10-20% (regardless of scale)
- Software engineers make up ~40% of R&D headcount
- As companies scale past $25M in revenue, they tend to invest more heavily in full-time employees (FTEs) dedicated to infrastructure
R&D usually represent the largest portion of spend as companies scale to $25M. Once they attain critical scale, these expenses level off to around ~20-30% of revenue
While the optimal time to hire the first dedicated FTE for key R&D roles will depend on business needs, hiring trends tend to converge around different inflection points of growth.
- Software Engineers make up ~40% of R&D headcount, regardless of scale, with the make-up of other IC roles staying relatively consistent as companies scale
- As companies scale past $25M in revenue, they tend to invest more heavily in FTEs dedicated to infrastructure; In addition, Leadership roles make up ~20% of the R&D organization, regardless of scale
- Although team composition and headcount ratios vary based on a company's strategic and operational objectives, our survey data offers a benchmark for what constitutes a healthy range for R&D ratios.
Our hiring philosophy is quite contrarian. We hire everyone as a “Member of the Technical Staff” with no specified level and title. We have a Technical Committee that observes them during the first 6-10 months, assesses their level of contributions and skills, and decides on their title based on that assessment. This has been perceived as very fair by employees, and as a result we see an attrition rate of that is lower than the industry average.
Spotlight: Building a Customer-Centric Engineering Culture
- At my previous company Nutanix and now at DevRev, we want to ensure that our developers interact with customers on a regular basis. As such, we have them visit customer sites with our sales team and sit in with customer support during calls, or occasionally, even to look at and respond to customer support tickets
- This approach allows our engineers to truly empathize with our customers. As a result of our customer-centric culture., we have achieved a 90+ Net Promoter Score (NPS)
- In addition, because the engineers are in such close contact with customer problems, they end up knowing the impact of their work and feeling motivated by that as opposed to feeling detached from the core problems they have to build for
- We want engineers to always ask themselves: “Is what I’m working on good for our customers?” If the answer is not “Yes”, that means that they are not prioritizing their work correctly
Related Reports
.png)
.png)
Other Reports
.png)
Disclaimer
Unless otherwise indicated, the views expressed in this presentation are those of ICONIQ Growth (“ICONIQ" or the “Firm"), are the result of proprietary research, may be subjective, and may not be relied upon in making an investment decision. Information used in this presentation was obtained from numerous sources. Certain of these companies are portfolio companies of ICONIQ Growth. ICONIQ Growth does not make any representations or warranties as to the accuracy of the information obtained from these sources.
This presentation is for general information purposes only and does not constitute investment advice. This presentation must not be relied upon in connection with any investment decision. The information in this presentation is not intended to and does not constitute financial, accounting, tax, legal, investment, consulting or other professional advice or services. Nothing in this presentation is or should be construed as an offer, invitation or solicitation to engage in any investment activity or transaction, including an offer to sell or a solicitation of an offer to buy any securities which should only be made pursuant to definitive offering documents and subscription agreements, including without limitation, any investment fund or investment product referenced herein.
Any reproduction or distribution of this presentation in whole or in part, or the disclosure of any of its contents, without the prior consent of ICONIQ, is strictly unauthorized.
This presentation may contain forward-looking statements based on current plans, estimates and projections. The recipient of this presentation ("you") are cautioned that a number of important factors could cause actual results or outcomes to differ materially from those expressed in, or implied by, the forward-looking statements. The numbers, figures and case studies included in this presentation have been included for purposes of illustration only, and no assurance can be given that the actual results of ICONIQ or any of its partners and affiliates will correspond with the results contemplated in the presentation. No information is contained herein with respect to conflicts of interest, which may be significant. The portfolio companies and other parties mentioned herein may reflect a selective list of the prior investments made by ICONIQ.
Certain of the economic and market information contained herein may have been obtained from published sources and/or prepared by other parties. While such sources are believed to be reliable, none of ICONIQ or any of its affiliates and partners, employees and representatives assume any responsibility for the accuracy of such information.
All of the information in the presentation is presented as of the date made available to you (except as otherwise specified), and is subject to change without notice, and may not be current or may have changed (possibly materially) between the date made available to you and the date actually received or reviewed by you. ICONIQ assumes no obligation to update or otherwise revise any information, projections, forecasts or estimates contained in the presentation, including any revisions to reflect changes in economic or market conditions or other circumstances arising after the date the items were made available to you or to reflect the occurrence of unanticipated events. Numbers or amounts herein may increase or decrease as a result of currency fluctuations.