Corporate GitHub Activity
Most Active Corporations on GitHub, 02 2023
Ranking companies with employees who, during 02 2023, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 39% 39% (n=226) of all SUSE engineers (n=5751) were active on GitHub. | 9% 9% (n=226) of all SUSE employees (n=2,4002) were active on GitHub. | 226 226 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Grafana Labs | 35% 35% (n=181) of all Grafana Labs engineers (n=5163) were active on GitHub. | 15% 15% (n=181) of all Grafana Labs employees (n=1,2174) were active on GitHub. | 181 181 Grafana Labs employees were active on GitHub. | 
| 3. Automattic | 32% 32% (n=275) of all Automattic engineers (n=8665) were active on GitHub. | 14% 14% (n=275) of all Automattic employees (n=1,9306) were active on GitHub. | 275 275 Automattic employees were active on GitHub. | 
| 4. Mozilla | 30% 30% (n=174) of all Mozilla engineers (n=5857) were active on GitHub. | 10% 10% (n=174) of all Mozilla employees (n=1,7458) were active on GitHub. | 174 174 Mozilla employees were active on GitHub. | 
| 5. HashiCorp | 28% 28% (n=187) of all HashiCorp engineers (n=6809) were active on GitHub. | 9% 9% (n=187) of all HashiCorp employees (n=2,20010) were active on GitHub. | 187 187 HashiCorp employees were active on GitHub. | 
| 6. Elastic | 26% 26% (n=267) of all Elastic engineers (n=1,02211) were active on GitHub. | 8% 8% (n=267) of all Elastic employees (n=3,18712) were active on GitHub. | 267 267 Elastic employees were active on GitHub. | 
| 7. The Guardian | 21% 21% (n=30) of all The Guardian engineers (n=14413) were active on GitHub. | 1% 1% (n=30) of all The Guardian employees (n=2,50114) were active on GitHub. | 30 30 The Guardian employees were active on GitHub. | 
| 8. JetBrains | 17% 17% (n=169) of all JetBrains engineers (n=97215) were active on GitHub. | 9% 9% (n=169) of all JetBrains employees (n=1,80016) were active on GitHub. | 169 169 JetBrains employees were active on GitHub. | 
| 9. Docker | 17% 17% (n=29) of all Docker engineers (n=16717) were active on GitHub. | 4% 4% (n=29) of all Docker employees (n=76718) were active on GitHub. | 29 29 Docker employees were active on GitHub. | 
| 10. Mapbox | 12% 12% (n=29) of all Mapbox engineers (n=24019) were active on GitHub. | 4% 4% (n=29) of all Mapbox employees (n=65420) were active on GitHub. | 29 29 Mapbox employees were active on GitHub. | 
| 11. WikiMedia Foundation | 12% 12% (n=24) of all WikiMedia Foundation engineers (n=20421) were active on GitHub. | 3% 3% (n=24) of all WikiMedia Foundation employees (n=70022) were active on GitHub. | 24 24 WikiMedia Foundation employees were active on GitHub. | 
| 12. WSO2 | 11% 11% (n=73) of all WSO2 engineers (n=66423) were active on GitHub. | 7% 7% (n=73) of all WSO2 employees (n=1,02024) were active on GitHub. | 73 73 WSO2 employees were active on GitHub. | 
| 13. DataDog | 9% 9% (n=220) of all DataDog engineers (n=2,40025) were active on GitHub. | 4% 4% (n=220) of all DataDog employees (n=5,20026) were active on GitHub. | 220 220 DataDog employees were active on GitHub. | 
| 14. MongoDB | 9% 9% (n=108) of all MongoDB engineers (n=1,22627) were active on GitHub. | 2% 2% (n=108) of all MongoDB employees (n=5,03728) were active on GitHub. | 108 108 MongoDB employees were active on GitHub. | 
| 15. Cloudflare | 8% 8% (n=70) of all Cloudflare engineers (n=83029) were active on GitHub. | 2% 2% (n=70) of all Cloudflare employees (n=3,68230) were active on GitHub. | 70 70 Cloudflare employees were active on GitHub. | 
| 16. New Relic | 8% 8% (n=67) of all New Relic engineers (n=88431) were active on GitHub. | 3% 3% (n=67) of all New Relic employees (n=2,58432) were active on GitHub. | 67 67 New Relic employees were active on GitHub. | 
| 17. Twitter | 6% 6% (n=34) of all Twitter engineers (n=54933) were active on GitHub. | 2% 2% (n=34) of all Twitter employees (n=2,14034) were active on GitHub. | 34 34 Twitter employees were active on GitHub. | 
| 18. Shopify | 6% 6% (n=207) of all Shopify engineers (n=3,56435) were active on GitHub. | 2% 2% (n=207) of all Shopify employees (n=8,30036) were active on GitHub. | 207 207 Shopify employees were active on GitHub. | 
| 19. Liferay | 5% 5% (n=24) of all Liferay engineers (n=46037) were active on GitHub. | 2% 2% (n=24) of all Liferay employees (n=1,37538) were active on GitHub. | 24 24 Liferay employees were active on GitHub. | 
| 20. Confluent | 5% 5% (n=52) of all Confluent engineers (n=1,03439) were active on GitHub. | 2% 2% (n=52) of all Confluent employees (n=2,74440) were active on GitHub. | 52 52 Confluent employees were active on GitHub. | 
| 21. Odoo | 4% 4% (n=27) of all Odoo engineers (n=64541) were active on GitHub. | 2% 2% (n=27) of all Odoo employees (n=1,70042) were active on GitHub. | 27 27 Odoo employees were active on GitHub. | 
| 22. Microsoft | 4% 4% (n=2,968) of all Microsoft engineers (n=72,00043) were active on GitHub. | 1% 1% (n=2,968) of all Microsoft employees (n=221,00044) were active on GitHub. | 2,968 2,968 Microsoft employees were active on GitHub. | 
| 23. ESRI | 4% 4% (n=81) of all ESRI engineers (n=2,07445) were active on GitHub. | 1% 1% (n=81) of all ESRI employees (n=6,44746) were active on GitHub. | 81 81 ESRI employees were active on GitHub. | 
| 24. Square, Inc. | 3% 3% (n=67) of all Square, Inc. engineers (n=2,06047) were active on GitHub. | 1% 1% (n=67) of all Square, Inc. employees (n=12,98548) were active on GitHub. | 67 67 Square, Inc. employees were active on GitHub. | 
| 25. Alibaba | 3% 3% (n=324) of all Alibaba engineers (n=10,02549) were active on GitHub. | 0% 0% (n=324) of all Alibaba employees (n=224,95550) were active on GitHub. | 324 324 Alibaba employees were active on GitHub. | 
| 26. VMWare | 3% 3% (n=390) of all VMWare engineers (n=12,94451) were active on GitHub. | 1% 1% (n=390) of all VMWare employees (n=38,30052) were active on GitHub. | 390 390 VMWare employees were active on GitHub. | 
| 27. Progress Software | 3% 3% (n=26) of all Progress Software engineers (n=88653) were active on GitHub. | 1% 1% (n=26) of all Progress Software employees (n=2,28454) were active on GitHub. | 26 26 Progress Software employees were active on GitHub. | 
| 28. ThoughtWorks | 3% 3% (n=103) of all ThoughtWorks engineers (n=3,76555) were active on GitHub. | 1% 1% (n=103) of all ThoughtWorks employees (n=10,50056) were active on GitHub. | 103 103 ThoughtWorks employees were active on GitHub. | 
| 29. Okta | 3% 3% (n=40) of all Okta engineers (n=1,57057) were active on GitHub. | 1% 1% (n=40) of all Okta employees (n=5,90858) were active on GitHub. | 40 40 Okta employees were active on GitHub. | 
| 30. Netflix | 3% 3% (n=61) of all Netflix engineers (n=2,40959) were active on GitHub. | 0% 0% (n=61) of all Netflix employees (n=13,00060) were active on GitHub. | 61 61 Netflix employees were active on GitHub. | 
| 31. Amazon | 2% 2% (n=1,044) of all Amazon engineers (n=43,60561) were active on GitHub. | 1% 1% (n=1,044) of all Amazon employees (n=125,34562) were active on GitHub. | 1,044 1,044 Amazon employees were active on GitHub. | 
| 32. Arm Ltd | 2% 2% (n=104) of all Arm Ltd engineers (n=4,75363) were active on GitHub. | 2% 2% (n=104) of all Arm Ltd employees (n=5,96364) were active on GitHub. | 104 104 Arm Ltd employees were active on GitHub. | 
| 33. Twilio | 2% 2% (n=54) of all Twilio engineers (n=2,56365) were active on GitHub. | 1% 1% (n=54) of all Twilio employees (n=5,86766) were active on GitHub. | 54 54 Twilio employees were active on GitHub. | 
| 34. Snowflake, Inc. | 2% 2% (n=41) of all Snowflake, Inc. engineers (n=2,00267) were active on GitHub. | 1% 1% (n=41) of all Snowflake, Inc. employees (n=7,00468) were active on GitHub. | 41 41 Snowflake, Inc. employees were active on GitHub. | 
| 35. Zendesk | 2% 2% (n=30) of all Zendesk engineers (n=1,48169) were active on GitHub. | 0% 0% (n=30) of all Zendesk employees (n=6,17970) were active on GitHub. | 30 30 Zendesk employees were active on GitHub. | 
| 36. Lyft | 2% 2% (n=26) of all Lyft engineers (n=1,28471) were active on GitHub. | 1% 1% (n=26) of all Lyft employees (n=2,94572) were active on GitHub. | 26 26 Lyft employees were active on GitHub. | 
| 37. Stripe | 2% 2% (n=59) of all Stripe engineers (n=2,95273) were active on GitHub. | 1% 1% (n=59) of all Stripe employees (n=8,40974) were active on GitHub. | 59 59 Stripe employees were active on GitHub. | 
| 38. Adobe | 2% 2% (n=198) of all Adobe engineers (n=10,24775) were active on GitHub. | 1% 1% (n=198) of all Adobe employees (n=29,94576) were active on GitHub. | 198 198 Adobe employees were active on GitHub. | 
| 39. Zalando DE | 2% 2% (n=33) of all Zalando DE engineers (n=1,72277) were active on GitHub. | 0% 0% (n=33) of all Zalando DE employees (n=15,79378) were active on GitHub. | 33 33 Zalando DE employees were active on GitHub. | 
| 40. Unity Technologies | 2% 2% (n=70) of all Unity Technologies engineers (n=3,84479) were active on GitHub. | 1% 1% (n=70) of all Unity Technologies employees (n=6,74880) were active on GitHub. | 70 70 Unity Technologies employees were active on GitHub. | 
| 41. Tencent | 2% 2% (n=242) of all Tencent engineers (n=13,64281) were active on GitHub. | 0% 0% (n=242) of all Tencent employees (n=105,41782) were active on GitHub. | 242 242 Tencent employees were active on GitHub. | 
| 42. Google | 2% 2% (n=1,319) of all Google engineers (n=75,57183) were active on GitHub. | 1% 1% (n=1,319) of all Google employees (n=182,50284) were active on GitHub. | 1,319 1,319 Google employees were active on GitHub. | 
| 43. WIX | 2% 2% (n=36) of all WIX engineers (n=2,30185) were active on GitHub. | 1% 1% (n=36) of all WIX employees (n=4,60086) were active on GitHub. | 36 36 WIX employees were active on GitHub. | 
| 44. Splunk | 1% 1% (n=34) of all Splunk engineers (n=2,38787) were active on GitHub. | 0% 0% (n=34) of all Splunk employees (n=8,00088) were active on GitHub. | 34 34 Splunk employees were active on GitHub. | 
| 45. Spotify | 1% 1% (n=63) of all Spotify engineers (n=4,71989) were active on GitHub. | 1% 1% (n=63) of all Spotify employees (n=9,12390) were active on GitHub. | 63 63 Spotify employees were active on GitHub. | 
| 46. BBC | 1% 1% (n=24) of all BBC engineers (n=1,82291) were active on GitHub. | 0% 0% (n=24) of all BBC employees (n=21,63192) were active on GitHub. | 24 24 BBC employees were active on GitHub. | 
| 47. NVIDIA | 1% 1% (n=259) of all NVIDIA engineers (n=22,20093) were active on GitHub. | 1% 1% (n=259) of all NVIDIA employees (n=29,60094) were active on GitHub. | 259 259 NVIDIA employees were active on GitHub. | 
| 48. Autodesk | 1% 1% (n=41) of all Autodesk engineers (n=4,20995) were active on GitHub. | 0% 0% (n=41) of all Autodesk employees (n=14,10096) were active on GitHub. | 41 41 Autodesk employees were active on GitHub. | 
| 49. Atlassian | 1% 1% (n=47) of all Atlassian engineers (n=5,36397) were active on GitHub. | 0% 0% (n=47) of all Atlassian employees (n=10,72698) were active on GitHub. | 47 47 Atlassian employees were active on GitHub. | 
| 50. Meta | 1% 1% (n=274) of all Meta engineers (n=31,33899) were active on GitHub. | 0% 0% (n=274) of all Meta employees (n=67,317100) were active on GitHub. | 274 274 Meta employees were active on GitHub. | 
| 51. Salesforce | 1% 1% (n=154) of all Salesforce engineers (n=19,483101) were active on GitHub. | 0% 0% (n=154) of all Salesforce employees (n=72,682102) were active on GitHub. | 154 154 Salesforce employees were active on GitHub. | 
| 52. SAP SE | 1% 1% (n=263) of all SAP SE engineers (n=33,377103) were active on GitHub. | 0% 0% (n=263) of all SAP SE employees (n=107,602104) were active on GitHub. | 263 263 SAP SE employees were active on GitHub. | 
| 53. Intel | 1% 1% (n=434) of all Intel engineers (n=57,201105) were active on GitHub. | 0% 0% (n=434) of all Intel employees (n=124,800106) were active on GitHub. | 434 434 Intel employees were active on GitHub. | 
| 54. Uber | 1% 1% (n=48) of all Uber engineers (n=6,426107) were active on GitHub. | 0% 0% (n=48) of all Uber employees (n=30,400108) were active on GitHub. | 48 48 Uber employees were active on GitHub. | 
| 55. Yandex | 1% 1% (n=81) of all Yandex engineers (n=13,003109) were active on GitHub. | 0% 0% (n=81) of all Yandex employees (n=26,361110) were active on GitHub. | 81 81 Yandex employees were active on GitHub. | 
| 56. Bloomberg | 1% 1% (n=39) of all Bloomberg engineers (n=7,328111) were active on GitHub. | 0% 0% (n=39) of all Bloomberg employees (n=25,923112) were active on GitHub. | 39 39 Bloomberg employees were active on GitHub. | 
| 57. AMD | 1% 1% (n=81) of all AMD engineers (n=15,606113) were active on GitHub. | 0% 0% (n=81) of all AMD employees (n=26,000114) were active on GitHub. | 81 81 AMD employees were active on GitHub. | 
| 58. Baidu | 0% 0% (n=106) of all Baidu engineers (n=21,800115) were active on GitHub. | 0% 0% (n=106) of all Baidu employees (n=39,800116) were active on GitHub. | 106 106 Baidu employees were active on GitHub. | 
| 59. Cisco Systems | 0% 0% (n=109) of all Cisco Systems engineers (n=23,772117) were active on GitHub. | 0% 0% (n=109) of all Cisco Systems employees (n=84,900118) were active on GitHub. | 109 109 Cisco Systems employees were active on GitHub. | 
| 60. NetEase | 0% 0% (n=54) of all NetEase engineers (n=14,855119) were active on GitHub. | 0% 0% (n=54) of all NetEase employees (n=29,128120) were active on GitHub. | 54 54 NetEase employees were active on GitHub. | 
| 61. PayPal | 0% 0% (n=31) of all PayPal engineers (n=8,658121) were active on GitHub. | 0% 0% (n=31) of all PayPal employees (n=27,200122) were active on GitHub. | 31 31 PayPal employees were active on GitHub. | 
| 62. Apple | 0% 0% (n=160) of all Apple engineers (n=46,752123) were active on GitHub. | 0% 0% (n=160) of all Apple employees (n=161,000124) were active on GitHub. | 160 160 Apple employees were active on GitHub. | 
| 63. Oracle | 0% 0% (n=152) of all Oracle engineers (n=47,000125) were active on GitHub. | 0% 0% (n=152) of all Oracle employees (n=164,000126) were active on GitHub. | 152 152 Oracle employees were active on GitHub. | 
| 64. EPAM Systems | 0% 0% (n=113) of all EPAM Systems engineers (n=47,350127) were active on GitHub. | 0% 0% (n=113) of all EPAM Systems employees (n=53,150128) were active on GitHub. | 113 113 EPAM Systems employees were active on GitHub. | 
| 65. Ericsson | 0% 0% (n=37) of all Ericsson engineers (n=28,219129) were active on GitHub. | 0% 0% (n=37) of all Ericsson employees (n=99,952130) were active on GitHub. | 37 37 Ericsson employees were active on GitHub. | 
| 66. Nokia | 0% 0% (n=33) of all Nokia engineers (n=26,395131) were active on GitHub. | 0% 0% (n=33) of all Nokia employees (n=86,689132) were active on GitHub. | 33 33 Nokia employees were active on GitHub. | 
| 67. Samsung | 0% 0% (n=74) of all Samsung engineers (n=83,729133) were active on GitHub. | 0% 0% (n=74) of all Samsung employees (n=267,860134) were active on GitHub. | 74 74 Samsung employees were active on GitHub. | 
| 68. Capgemini | 0% 0% (n=59) of all Capgemini engineers (n=69,796135) were active on GitHub. | 0% 0% (n=59) of all Capgemini employees (n=340,400136) were active on GitHub. | 59 59 Capgemini employees were active on GitHub. | 
| 69. Huawei | 0% 0% (n=82) of all Huawei engineers (n=114,000137) were active on GitHub. | 0% 0% (n=82) of all Huawei employees (n=207,000138) were active on GitHub. | 82 82 Huawei employees were active on GitHub. | 
| 70. IBM | (n=1,759) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,759) of all IBM employees (n=282,200139) were active on GitHub. | 1,759 1,759 IBM employees were active on GitHub. | 
| 71. Canonical | (n=103) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=103) of all Canonical employees (n=NaN0) were active on GitHub. | 103 103 Canonical employees were active on GitHub. | 
| 72. ByteDance | (n=90) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=90) of all ByteDance employees (n=NaN0) were active on GitHub. | 90 90 ByteDance employees were active on GitHub. | 
| 73. Accenture | (n=63) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=63) of all Accenture employees (n=733,000140) were active on GitHub. | 63 63 Accenture employees were active on GitHub. | 
| 74. Sentry.io | (n=62) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 16% 16% (n=62) of all Sentry.io employees (n=378141) were active on GitHub. | 62 62 Sentry.io employees were active on GitHub. | 
| 75. Yahoo! | (n=55) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=55) of all Yahoo! employees (n=NaN0) were active on GitHub. | 55 55 Yahoo! employees were active on GitHub. | 
| 76. Databricks | (n=51) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=51) of all Databricks employees (n=7,211142) were active on GitHub. | 51 51 Databricks employees were active on GitHub. | 
| 77. PingCAP | (n=51) of all PingCAP engineers (n=NaN0) were active on GitHub. | 12% 12% (n=51) of all PingCAP employees (n=410143) were active on GitHub. | 51 51 PingCAP employees were active on GitHub. | 
| 78. Software Mansion | (n=46) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=46) of all Software Mansion employees (n=NaN0) were active on GitHub. | 46 46 Software Mansion employees were active on GitHub. | 
| 79. Posit | (n=41) of all Posit engineers (n=NaN0) were active on GitHub. | (n=41) of all Posit employees (n=NaN0) were active on GitHub. | 41 41 Posit employees were active on GitHub. | 
| 80. Snyk | (n=40) of all Snyk engineers (n=NaN0) were active on GitHub. | 3% 3% (n=40) of all Snyk employees (n=1,171144) were active on GitHub. | 40 40 Snyk employees were active on GitHub. | 
| 81. @bytedance | (n=36) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=36) of all @bytedance employees (n=NaN0) were active on GitHub. | 36 36 @bytedance employees were active on GitHub. | 
| 82. Masai | (n=35) of all Masai engineers (n=NaN0) were active on GitHub. | (n=35) of all Masai employees (n=NaN0) were active on GitHub. | 35 35 Masai employees were active on GitHub. | 
| 83. R3 | (n=35) of all R3 engineers (n=NaN0) were active on GitHub. | (n=35) of all R3 employees (n=NaN0) were active on GitHub. | 35 35 R3 employees were active on GitHub. | 
| 84. Palo Alto Networks | (n=33) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=33) of all Palo Alto Networks employees (n=13,948145) were active on GitHub. | 33 33 Palo Alto Networks employees were active on GitHub. | 
| 85. Kitware | (n=33) of all Kitware engineers (n=NaN0) were active on GitHub. | 19% 19% (n=33) of all Kitware employees (n=171146) were active on GitHub. | 33 33 Kitware employees were active on GitHub. | 
| 86. Harness | (n=30) of all Harness engineers (n=NaN0) were active on GitHub. | (n=30) of all Harness employees (n=NaN0) were active on GitHub. | 30 30 Harness employees were active on GitHub. | 
| 87. TU Delft | (n=30) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=30) of all TU Delft employees (n=NaN0) were active on GitHub. | 30 30 TU Delft employees were active on GitHub. | 
| 88. Epitech | (n=30) of all Epitech engineers (n=NaN0) were active on GitHub. | (n=30) of all Epitech employees (n=NaN0) were active on GitHub. | 30 30 Epitech employees were active on GitHub. | 
| 89. Cloudera | (n=30) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=30) of all Cloudera employees (n=NaN0) were active on GitHub. | 30 30 Cloudera employees were active on GitHub. | 
| 90. @vercel | (n=27) of all @vercel engineers (n=NaN0) were active on GitHub. | (n=27) of all @vercel employees (n=NaN0) were active on GitHub. | 27 27 @vercel employees were active on GitHub. | 
| 91. @MathWorks | (n=27) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=27) of all @MathWorks employees (n=NaN0) were active on GitHub. | 27 27 @MathWorks employees were active on GitHub. | 
| 92. Protocol Labs | (n=26) of all Protocol Labs engineers (n=NaN0) were active on GitHub. | (n=26) of all Protocol Labs employees (n=NaN0) were active on GitHub. | 26 26 Protocol Labs employees were active on GitHub. | 
| 93. Broad Institute | (n=25) of all Broad Institute engineers (n=NaN0) were active on GitHub. | (n=25) of all Broad Institute employees (n=NaN0) were active on GitHub. | 25 25 Broad Institute employees were active on GitHub. | 
| 94. Trybe | (n=25) of all Trybe engineers (n=NaN0) were active on GitHub. | (n=25) of all Trybe employees (n=NaN0) were active on GitHub. | 25 25 Trybe employees were active on GitHub. | 
| 95. Dynatrace | (n=25) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=25) of all Dynatrace employees (n=NaN0) were active on GitHub. | 25 25 Dynatrace employees were active on GitHub. | 
| 96. @apache | (n=25) of all @apache engineers (n=NaN0) were active on GitHub. | (n=25) of all @apache employees (n=NaN0) were active on GitHub. | 25 25 @apache employees were active on GitHub. | 
| 97. DigitalOcean | (n=24) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 2% 2% (n=24) of all DigitalOcean employees (n=1,156147) were active on GitHub. | 24 24 DigitalOcean employees were active on GitHub. | 
| 98. Intuit | (n=24) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=24) of all Intuit employees (n=18,200148) were active on GitHub. | 24 24 Intuit employees were active on GitHub. | 
| 99. CircleCI | (n=24) of all CircleCI engineers (n=NaN0) were active on GitHub. | 5% 5% (n=24) of all CircleCI employees (n=492149) were active on GitHub. | 24 24 CircleCI employees were active on GitHub. | 
| 100. Talend | (n=24) of all Talend engineers (n=NaN0) were active on GitHub. | (n=24) of all Talend employees (n=NaN0) were active on GitHub. | 24 24 Talend employees were active on GitHub. | 
References
- SUSE engineer count: linkedin.com
- SUSE employee count: links.imagerelay.com (page 10)
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved December 2023)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 13)
- Elastic engineer count: linkedin.com (retrieved Dec 2023)
- Elastic employee count: sec.gov (page 15)
- The Guardian engineer count: linkedin.com (retrieved Dec 2023)
- The Guardian employee count: linkedin.com (retrieved Dec 2023)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- WikiMedia Foundation employee count: wikimediafoundation.org
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- DataDog engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 11)
- MongoDB engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 9)
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- New Relic engineer count: linkedin.com (Retrieved December 2023)
- New Relic employee count: linkedin.com (Retrieved December 2023)
- Twitter engineer count: linkedin.com
- Twitter employee count: linkedin.com
- Shopify engineer count: linkedin.com (retrieved Dec 2023)
- Shopify employee count: s27.q4cdn.com (page 22)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 20)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Interim Report, page 15)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 16)
- Progress Software engineer count: sec.gov (page 7, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 7)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 14)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Twilio engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 17)
- Zendesk engineer count: linkedin.com (retrieved Dec 2023)
- Zendesk employee count: linkedin.com (retrieved Dec 2023)
- Lyft engineer count: linkedin.com
- Lyft employee count: sec.gov (page 10)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 18)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Tencent engineer count: linkedin.com (retrieved Dec 2023)
- Tencent employee count: static.tencent.com (page 56)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 10)
- WIX engineer count: sec.gov (page 89, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 149)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Spotify engineer count: sec.gov (page 68, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 68)
- BBC engineer count: linkedin.com
- BBC employee count: bbc.co.uk (page 59)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Autodesk engineer count: linkedin.com (retrieved Dec 2023)
- Autodesk employee count: sec.gov (page 13)
- Atlassian engineer count: sec.gov (page 9, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 12)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 60)
- Salesforce engineer count: linkedin.com (retrieved Dec 2023)
- Salesforce employee count: sec.gov (page 10)
- SAP SE engineer count: sec.gov (page F-23, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 102)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 7)
- Yandex engineer count: sec.gov (page 54, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 54)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 12)
- Baidu engineer count: sec.gov (page 196, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 196)
- Cisco Systems engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 10)
- NetEase engineer count: sec.gov (page 156, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 156)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- EPAM Systems engineer count: sec.gov (page 5, referred to as 'delivery professionals')
- EPAM Systems employee count: sec.gov (page 5)
- Ericsson engineer count: sec.gov (page 6, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- Nokia engineer count: linkedin.com (retrieved Dec 2023)
- Nokia employee count: sec.gov (page 105)
- Samsung engineer count: samsung.com (page 58, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 58)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 4)
- Huawei engineer count: www-file.huawei.com (page 67, referred to as employees in 'R&D')
- Huawei employee count: www-file.huawei.com (page 1)
- IBM employee count: sec.gov (page 16)
- Accenture employee count: sec.gov (page 25)
- Sentry.io employee count: linkedin.com
- Databricks employee count: linkedin.com
- PingCAP employee count: linkedin.com
- Snyk employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- Kitware employee count: linkedin.com
- DigitalOcean employee count: sec.gov (page 15)
- Intuit employee count: sec.gov (page 12)
- CircleCI employee count: linkedin.com