Corporate GitHub Activity
Most Active Corporations on GitHub, Q3 2023
Ranking companies with employees who, during Q3 2023, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 54% 54% (n=313) of all SUSE engineers (n=5751) were active on GitHub. | 13% 13% (n=313) of all SUSE employees (n=2,4002) were active on GitHub. | 313 313 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Vercel | 51% 51% (n=78) of all Vercel engineers (n=1543) were active on GitHub. | 16% 16% (n=78) of all Vercel employees (n=4734) were active on GitHub. | 78 78 Vercel employees were active on GitHub. | 
| 3. Grafana Labs | 47% 47% (n=243) of all Grafana Labs engineers (n=5165) were active on GitHub. | 20% 20% (n=243) of all Grafana Labs employees (n=1,2176) were active on GitHub. | 243 243 Grafana Labs employees were active on GitHub. | 
| 4. Automattic | 41% 41% (n=358) of all Automattic engineers (n=8667) were active on GitHub. | 19% 19% (n=358) of all Automattic employees (n=1,9308) were active on GitHub. | 358 358 Automattic employees were active on GitHub. | 
| 5. HashiCorp | 36% 36% (n=246) of all HashiCorp engineers (n=6809) were active on GitHub. | 11% 11% (n=246) of all HashiCorp employees (n=2,20010) were active on GitHub. | 246 246 HashiCorp employees were active on GitHub. | 
| 6. Mozilla | 35% 35% (n=204) of all Mozilla engineers (n=58511) were active on GitHub. | 12% 12% (n=204) of all Mozilla employees (n=1,74512) were active on GitHub. | 204 204 Mozilla employees were active on GitHub. | 
| 7. Elastic | 34% 34% (n=347) of all Elastic engineers (n=1,02213) were active on GitHub. | 11% 11% (n=347) of all Elastic employees (n=3,18714) were active on GitHub. | 347 347 Elastic employees were active on GitHub. | 
| 8. The Guardian | 28% 28% (n=40) of all The Guardian engineers (n=14415) were active on GitHub. | 2% 2% (n=40) of all The Guardian employees (n=2,50116) were active on GitHub. | 40 40 The Guardian employees were active on GitHub. | 
| 9. JetBrains | 24% 24% (n=233) of all JetBrains engineers (n=97217) were active on GitHub. | 13% 13% (n=233) of all JetBrains employees (n=1,80018) were active on GitHub. | 233 233 JetBrains employees were active on GitHub. | 
| 10. Odoo | 22% 22% (n=141) of all Odoo engineers (n=64519) were active on GitHub. | 8% 8% (n=141) of all Odoo employees (n=1,70020) were active on GitHub. | 141 141 Odoo employees were active on GitHub. | 
| 11. WikiMedia Foundation | 21% 21% (n=43) of all WikiMedia Foundation engineers (n=20421) were active on GitHub. | 6% 6% (n=43) of all WikiMedia Foundation employees (n=70022) were active on GitHub. | 43 43 WikiMedia Foundation employees were active on GitHub. | 
| 12. Docker | 21% 21% (n=35) of all Docker engineers (n=16723) were active on GitHub. | 5% 5% (n=35) of all Docker employees (n=76724) were active on GitHub. | 35 35 Docker employees were active on GitHub. | 
| 13. WSO2 | 19% 19% (n=127) of all WSO2 engineers (n=66425) were active on GitHub. | 12% 12% (n=127) of all WSO2 employees (n=1,02026) were active on GitHub. | 127 127 WSO2 employees were active on GitHub. | 
| 14. Mapbox | 15% 15% (n=37) of all Mapbox engineers (n=24027) were active on GitHub. | 6% 6% (n=37) of all Mapbox employees (n=65428) were active on GitHub. | 37 37 Mapbox employees were active on GitHub. | 
| 15. DataDog | 14% 14% (n=327) of all DataDog engineers (n=2,40029) were active on GitHub. | 6% 6% (n=327) of all DataDog employees (n=5,20030) were active on GitHub. | 327 327 DataDog employees were active on GitHub. | 
| 16. Cloudflare | 12% 12% (n=101) of all Cloudflare engineers (n=83031) were active on GitHub. | 3% 3% (n=101) of all Cloudflare employees (n=3,68232) were active on GitHub. | 101 101 Cloudflare employees were active on GitHub. | 
| 17. MongoDB | 12% 12% (n=148) of all MongoDB engineers (n=1,22633) were active on GitHub. | 3% 3% (n=148) of all MongoDB employees (n=5,03734) were active on GitHub. | 148 148 MongoDB employees were active on GitHub. | 
| 18. New Relic | 11% 11% (n=94) of all New Relic engineers (n=88435) were active on GitHub. | 4% 4% (n=94) of all New Relic employees (n=2,58436) were active on GitHub. | 94 94 New Relic employees were active on GitHub. | 
| 19. Confluent | 9% 9% (n=92) of all Confluent engineers (n=1,03437) were active on GitHub. | 3% 3% (n=92) of all Confluent employees (n=2,74438) were active on GitHub. | 92 92 Confluent employees were active on GitHub. | 
| 20. Shopify | 8% 8% (n=284) of all Shopify engineers (n=3,56439) were active on GitHub. | 3% 3% (n=284) of all Shopify employees (n=8,30040) were active on GitHub. | 284 284 Shopify employees were active on GitHub. | 
| 21. ESRI | 7% 7% (n=145) of all ESRI engineers (n=2,07441) were active on GitHub. | 2% 2% (n=145) of all ESRI employees (n=6,44742) were active on GitHub. | 145 145 ESRI employees were active on GitHub. | 
| 22. Progress Software | 6% 6% (n=55) of all Progress Software engineers (n=88643) were active on GitHub. | 2% 2% (n=55) of all Progress Software employees (n=2,28444) were active on GitHub. | 55 55 Progress Software employees were active on GitHub. | 
| 23. Microsoft | 6% 6% (n=4,245) of all Microsoft engineers (n=72,00045) were active on GitHub. | 2% 2% (n=4,245) of all Microsoft employees (n=221,00046) were active on GitHub. | 4,245 4,245 Microsoft employees were active on GitHub. | 
| 24. Okta | 5% 5% (n=86) of all Okta engineers (n=1,57047) were active on GitHub. | 1% 1% (n=86) of all Okta employees (n=5,90848) were active on GitHub. | 86 86 Okta employees were active on GitHub. | 
| 25. Alibaba | 5% 5% (n=453) of all Alibaba engineers (n=10,02549) were active on GitHub. | 0% 0% (n=453) of all Alibaba employees (n=224,95550) were active on GitHub. | 453 453 Alibaba employees were active on GitHub. | 
| 26. ThoughtWorks | 4% 4% (n=165) of all ThoughtWorks engineers (n=3,76551) were active on GitHub. | 2% 2% (n=165) of all ThoughtWorks employees (n=10,50052) were active on GitHub. | 165 165 ThoughtWorks employees were active on GitHub. | 
| 27. Square, Inc. | 4% 4% (n=87) of all Square, Inc. engineers (n=2,06053) were active on GitHub. | 1% 1% (n=87) of all Square, Inc. employees (n=12,98554) were active on GitHub. | 87 87 Square, Inc. employees were active on GitHub. | 
| 28. VMWare | 4% 4% (n=499) of all VMWare engineers (n=12,94455) were active on GitHub. | 1% 1% (n=499) of all VMWare employees (n=38,30056) were active on GitHub. | 499 499 VMWare employees were active on GitHub. | 
| 29. Snowflake, Inc. | 4% 4% (n=77) of all Snowflake, Inc. engineers (n=2,00257) were active on GitHub. | 1% 1% (n=77) of all Snowflake, Inc. employees (n=7,00458) were active on GitHub. | 77 77 Snowflake, Inc. employees were active on GitHub. | 
| 30. Netflix | 4% 4% (n=92) of all Netflix engineers (n=2,40959) were active on GitHub. | 1% 1% (n=92) of all Netflix employees (n=13,00060) were active on GitHub. | 92 92 Netflix employees were active on GitHub. | 
| 31. Amazon | 4% 4% (n=1,632) of all Amazon engineers (n=43,60561) were active on GitHub. | 1% 1% (n=1,632) of all Amazon employees (n=125,34562) were active on GitHub. | 1,632 1,632 Amazon employees were active on GitHub. | 
| 32. Adobe | 4% 4% (n=374) of all Adobe engineers (n=10,24763) were active on GitHub. | 1% 1% (n=374) of all Adobe employees (n=29,94564) were active on GitHub. | 374 374 Adobe employees were active on GitHub. | 
| 33. Twilio | 3% 3% (n=89) of all Twilio engineers (n=2,56365) were active on GitHub. | 2% 2% (n=89) of all Twilio employees (n=5,86766) were active on GitHub. | 89 89 Twilio employees were active on GitHub. | 
| 34. Unity Technologies | 3% 3% (n=129) of all Unity Technologies engineers (n=3,84467) were active on GitHub. | 2% 2% (n=129) of all Unity Technologies employees (n=6,74868) were active on GitHub. | 129 129 Unity Technologies employees were active on GitHub. | 
| 35. Zendesk | 3% 3% (n=49) of all Zendesk engineers (n=1,48169) were active on GitHub. | 1% 1% (n=49) of all Zendesk employees (n=6,17970) were active on GitHub. | 49 49 Zendesk employees were active on GitHub. | 
| 36. Hyland | 3% 3% (n=36) of all Hyland engineers (n=1,09271) were active on GitHub. | 1% 1% (n=36) of all Hyland employees (n=4,08572) were active on GitHub. | 36 36 Hyland employees were active on GitHub. | 
| 37. Arm Ltd | 3% 3% (n=151) of all Arm Ltd engineers (n=4,75373) were active on GitHub. | 3% 3% (n=151) of all Arm Ltd employees (n=5,96374) were active on GitHub. | 151 151 Arm Ltd employees were active on GitHub. | 
| 38. Splunk | 3% 3% (n=71) of all Splunk engineers (n=2,38775) were active on GitHub. | 1% 1% (n=71) of all Splunk employees (n=8,00076) were active on GitHub. | 71 71 Splunk employees were active on GitHub. | 
| 39. CyberAgent | 3% 3% (n=46) of all CyberAgent engineers (n=1,66077) were active on GitHub. | 1% 1% (n=46) of all CyberAgent employees (n=7,25178) were active on GitHub. | 46 46 CyberAgent employees were active on GitHub. | 
| 40. Tencent | 3% 3% (n=359) of all Tencent engineers (n=13,64279) were active on GitHub. | 0% 0% (n=359) of all Tencent employees (n=105,41780) were active on GitHub. | 359 359 Tencent employees were active on GitHub. | 
| 41. Google | 3% 3% (n=1,955) of all Google engineers (n=75,57181) were active on GitHub. | 1% 1% (n=1,955) of all Google employees (n=182,50282) were active on GitHub. | 1,955 1,955 Google employees were active on GitHub. | 
| 42. WIX | 3% 3% (n=59) of all WIX engineers (n=2,30183) were active on GitHub. | 1% 1% (n=59) of all WIX employees (n=4,60084) were active on GitHub. | 59 59 WIX employees were active on GitHub. | 
| 43. Zalando DE | 2% 2% (n=41) of all Zalando DE engineers (n=1,72285) were active on GitHub. | 0% 0% (n=41) of all Zalando DE employees (n=15,79386) were active on GitHub. | 41 41 Zalando DE employees were active on GitHub. | 
| 44. Stripe | 2% 2% (n=66) of all Stripe engineers (n=2,95287) were active on GitHub. | 1% 1% (n=66) of all Stripe employees (n=8,40988) were active on GitHub. | 66 66 Stripe employees were active on GitHub. | 
| 45. Spotify | 2% 2% (n=95) of all Spotify engineers (n=4,71989) were active on GitHub. | 1% 1% (n=95) of all Spotify employees (n=9,12390) were active on GitHub. | 95 95 Spotify employees were active on GitHub. | 
| 46. NVIDIA | 2% 2% (n=432) of all NVIDIA engineers (n=22,20091) were active on GitHub. | 1% 1% (n=432) of all NVIDIA employees (n=29,60092) were active on GitHub. | 432 432 NVIDIA employees were active on GitHub. | 
| 47. BBC | 2% 2% (n=34) of all BBC engineers (n=1,82293) were active on GitHub. | 0% 0% (n=34) of all BBC employees (n=21,63194) were active on GitHub. | 34 34 BBC employees were active on GitHub. | 
| 48. Atlassian | 2% 2% (n=92) of all Atlassian engineers (n=5,36395) were active on GitHub. | 1% 1% (n=92) of all Atlassian employees (n=10,72696) were active on GitHub. | 92 92 Atlassian employees were active on GitHub. | 
| 49. Autodesk | 2% 2% (n=69) of all Autodesk engineers (n=4,20997) were active on GitHub. | 0% 0% (n=69) of all Autodesk employees (n=14,10098) were active on GitHub. | 69 69 Autodesk employees were active on GitHub. | 
| 50. Uber | 2% 2% (n=98) of all Uber engineers (n=6,42699) were active on GitHub. | 0% 0% (n=98) of all Uber employees (n=30,400100) were active on GitHub. | 98 98 Uber employees were active on GitHub. | 
| 51. Indeed | 1% 1% (n=38) of all Indeed engineers (n=2,813101) were active on GitHub. | 0% 0% (n=38) of all Indeed employees (n=18,038102) were active on GitHub. | 38 38 Indeed employees were active on GitHub. | 
| 52. Meta | 1% 1% (n=421) of all Meta engineers (n=31,338103) were active on GitHub. | 1% 1% (n=421) of all Meta employees (n=67,317104) were active on GitHub. | 421 421 Meta employees were active on GitHub. | 
| 53. SAP SE | 1% 1% (n=431) of all SAP SE engineers (n=33,377105) were active on GitHub. | 0% 0% (n=431) of all SAP SE employees (n=107,602106) were active on GitHub. | 431 431 SAP SE employees were active on GitHub. | 
| 54. Intel | 1% 1% (n=723) of all Intel engineers (n=57,201107) were active on GitHub. | 1% 1% (n=723) of all Intel employees (n=124,800108) were active on GitHub. | 723 723 Intel employees were active on GitHub. | 
| 55. AMD | 1% 1% (n=195) of all AMD engineers (n=15,606109) were active on GitHub. | 1% 1% (n=195) of all AMD employees (n=26,000110) were active on GitHub. | 195 195 AMD employees were active on GitHub. | 
| 56. Salesforce | 1% 1% (n=240) of all Salesforce engineers (n=19,483111) were active on GitHub. | 0% 0% (n=240) of all Salesforce employees (n=72,682112) were active on GitHub. | 240 240 Salesforce employees were active on GitHub. | 
| 57. Yandex | 1% 1% (n=141) of all Yandex engineers (n=13,003113) were active on GitHub. | 1% 1% (n=141) of all Yandex employees (n=26,361114) were active on GitHub. | 141 141 Yandex employees were active on GitHub. | 
| 58. Bloomberg | 1% 1% (n=68) of all Bloomberg engineers (n=7,328115) were active on GitHub. | 0% 0% (n=68) of all Bloomberg employees (n=25,923116) were active on GitHub. | 68 68 Bloomberg employees were active on GitHub. | 
| 59. Cisco Systems | 1% 1% (n=191) of all Cisco Systems engineers (n=23,772117) were active on GitHub. | 0% 0% (n=191) of all Cisco Systems employees (n=84,900118) were active on GitHub. | 191 191 Cisco Systems employees were active on GitHub. | 
| 60. Oracle | 1% 1% (n=330) of all Oracle engineers (n=47,000119) were active on GitHub. | 0% 0% (n=330) of all Oracle employees (n=164,000120) were active on GitHub. | 330 330 Oracle employees were active on GitHub. | 
| 61. Baidu | 1% 1% (n=131) of all Baidu engineers (n=21,800121) were active on GitHub. | 0% 0% (n=131) of all Baidu employees (n=39,800122) were active on GitHub. | 131 131 Baidu employees were active on GitHub. | 
| 62. PayPal | 1% 1% (n=52) of all PayPal engineers (n=8,658123) were active on GitHub. | 0% 0% (n=52) of all PayPal employees (n=27,200124) were active on GitHub. | 52 52 PayPal employees were active on GitHub. | 
| 63. NetEase | 1% 1% (n=87) of all NetEase engineers (n=14,855125) were active on GitHub. | 0% 0% (n=87) of all NetEase employees (n=29,128126) were active on GitHub. | 87 87 NetEase employees were active on GitHub. | 
| 64. Apple | 0% 0% (n=233) of all Apple engineers (n=46,752127) were active on GitHub. | 0% 0% (n=233) of all Apple employees (n=161,000128) were active on GitHub. | 233 233 Apple employees were active on GitHub. | 
| 65. EPAM Systems | 0% 0% (n=201) of all EPAM Systems engineers (n=47,350129) were active on GitHub. | 0% 0% (n=201) of all EPAM Systems employees (n=53,150130) were active on GitHub. | 201 201 EPAM Systems employees were active on GitHub. | 
| 66. Ericsson | 0% 0% (n=75) of all Ericsson engineers (n=28,219131) were active on GitHub. | 0% 0% (n=75) of all Ericsson employees (n=99,952132) were active on GitHub. | 75 75 Ericsson employees were active on GitHub. | 
| 67. Nokia | 0% 0% (n=64) of all Nokia engineers (n=26,395133) were active on GitHub. | 0% 0% (n=64) of all Nokia employees (n=86,689134) were active on GitHub. | 64 64 Nokia employees were active on GitHub. | 
| 68. Capgemini | 0% 0% (n=126) of all Capgemini engineers (n=69,796135) were active on GitHub. | 0% 0% (n=126) of all Capgemini employees (n=340,400136) were active on GitHub. | 126 126 Capgemini employees were active on GitHub. | 
| 69. Samsung | 0% 0% (n=140) of all Samsung engineers (n=83,729137) were active on GitHub. | 0% 0% (n=140) of all Samsung employees (n=267,860138) were active on GitHub. | 140 140 Samsung employees were active on GitHub. | 
| 70. Globant | 0% 0% (n=38) of all Globant engineers (n=24,968139) were active on GitHub. | 0% 0% (n=38) of all Globant employees (n=29,150140) were active on GitHub. | 38 38 Globant employees were active on GitHub. | 
| 71. Huawei | 0% 0% (n=128) of all Huawei engineers (n=114,000141) were active on GitHub. | 0% 0% (n=128) of all Huawei employees (n=207,000142) were active on GitHub. | 128 128 Huawei employees were active on GitHub. | 
| 72. IBM | (n=2,647) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=2,647) of all IBM employees (n=282,200143) were active on GitHub. | 2,647 2,647 IBM employees were active on GitHub. | 
| 73. ByteDance | (n=306) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=306) of all ByteDance employees (n=NaN0) were active on GitHub. | 306 306 ByteDance employees were active on GitHub. | 
| 74. Canonical | (n=174) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=174) of all Canonical employees (n=NaN0) were active on GitHub. | 174 174 Canonical employees were active on GitHub. | 
| 75. Accenture | (n=149) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=149) of all Accenture employees (n=733,000144) were active on GitHub. | 149 149 Accenture employees were active on GitHub. | 
| 76. Databricks | (n=103) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=103) of all Databricks employees (n=7,211145) were active on GitHub. | 103 103 Databricks employees were active on GitHub. | 
| 77. Sentry.io | (n=80) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 21% 21% (n=80) of all Sentry.io employees (n=378146) were active on GitHub. | 80 80 Sentry.io employees were active on GitHub. | 
| 78. Yahoo! | (n=77) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=77) of all Yahoo! employees (n=NaN0) were active on GitHub. | 77 77 Yahoo! employees were active on GitHub. | 
| 79. Software Mansion | (n=75) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=75) of all Software Mansion employees (n=NaN0) were active on GitHub. | 75 75 Software Mansion employees were active on GitHub. | 
| 80. Posit | (n=66) of all Posit engineers (n=NaN0) were active on GitHub. | (n=66) of all Posit employees (n=NaN0) were active on GitHub. | 66 66 Posit employees were active on GitHub. | 
| 81. UCL | (n=54) of all UCL engineers (n=NaN0) were active on GitHub. | (n=54) of all UCL employees (n=NaN0) were active on GitHub. | 54 54 UCL employees were active on GitHub. | 
| 82. Snyk | (n=54) of all Snyk engineers (n=NaN0) were active on GitHub. | 5% 5% (n=54) of all Snyk employees (n=1,171147) were active on GitHub. | 54 54 Snyk employees were active on GitHub. | 
| 83. PingCAP | (n=53) of all PingCAP engineers (n=NaN0) were active on GitHub. | 13% 13% (n=53) of all PingCAP employees (n=410148) were active on GitHub. | 53 53 PingCAP employees were active on GitHub. | 
| 84. @SSWConsulting | (n=52) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=52) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 52 52 @SSWConsulting employees were active on GitHub. | 
| 85. Qlik | (n=49) of all Qlik engineers (n=NaN0) were active on GitHub. | (n=49) of all Qlik employees (n=NaN0) were active on GitHub. | 49 49 Qlik employees were active on GitHub. | 
| 86. TU Delft | (n=49) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=49) of all TU Delft employees (n=NaN0) were active on GitHub. | 49 49 TU Delft employees were active on GitHub. | 
| 87. @MathWorks | (n=48) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=48) of all @MathWorks employees (n=NaN0) were active on GitHub. | 48 48 @MathWorks employees were active on GitHub. | 
| 88. Palo Alto Networks | (n=45) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=45) of all Palo Alto Networks employees (n=13,948149) were active on GitHub. | 45 45 Palo Alto Networks employees were active on GitHub. | 
| 89. Orange S.A. | (n=45) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=45) of all Orange S.A. employees (n=127,109150) were active on GitHub. | 45 45 Orange S.A. employees were active on GitHub. | 
| 90. Intuit | (n=44) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=44) of all Intuit employees (n=18,200151) were active on GitHub. | 44 44 Intuit employees were active on GitHub. | 
| 91. Harness | (n=42) of all Harness engineers (n=NaN0) were active on GitHub. | (n=42) of all Harness employees (n=NaN0) were active on GitHub. | 42 42 Harness employees were active on GitHub. | 
| 92. Kitware | (n=41) of all Kitware engineers (n=NaN0) were active on GitHub. | 24% 24% (n=41) of all Kitware employees (n=171152) were active on GitHub. | 41 41 Kitware employees were active on GitHub. | 
| 93. Remote | (n=39) of all Remote engineers (n=NaN0) were active on GitHub. | (n=39) of all Remote employees (n=NaN0) were active on GitHub. | 39 39 Remote employees were active on GitHub. | 
| 94. Cloudera | (n=39) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=39) of all Cloudera employees (n=NaN0) were active on GitHub. | 39 39 Cloudera employees were active on GitHub. | 
| 95. NTNU | (n=38) of all NTNU engineers (n=NaN0) were active on GitHub. | (n=38) of all NTNU employees (n=NaN0) were active on GitHub. | 38 38 NTNU employees were active on GitHub. | 
| 96. R3 | (n=37) of all R3 engineers (n=NaN0) were active on GitHub. | (n=37) of all R3 employees (n=NaN0) were active on GitHub. | 37 37 R3 employees were active on GitHub. | 
| 97. Software Developer | (n=37) of all Software Developer engineers (n=NaN0) were active on GitHub. | (n=37) of all Software Developer employees (n=NaN0) were active on GitHub. | 37 37 Software Developer employees were active on GitHub. | 
| 98. BUAA | (n=36) of all BUAA engineers (n=NaN0) were active on GitHub. | (n=36) of all BUAA employees (n=NaN0) were active on GitHub. | 36 36 BUAA employees were active on GitHub. | 
| 99. DigitalOcean | (n=36) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 3% 3% (n=36) of all DigitalOcean employees (n=1,156153) were active on GitHub. | 36 36 DigitalOcean employees were active on GitHub. | 
| 100. TU Darmstadt | (n=34) of all TU Darmstadt engineers (n=NaN0) were active on GitHub. | (n=34) of all TU Darmstadt employees (n=NaN0) were active on GitHub. | 34 34 TU Darmstadt employees were active on GitHub. | 
References
- SUSE engineer count: linkedin.com
- SUSE employee count: links.imagerelay.com (page 10)
- Vercel engineer count: linkedin.com
- Vercel employee count: linkedin.com
- 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)
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 13)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- 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
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- WikiMedia Foundation employee count: wikimediafoundation.org
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- Mapbox engineer count: linkedin.com
- Mapbox 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)
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- MongoDB engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 9)
- New Relic engineer count: linkedin.com (Retrieved December 2023)
- New Relic employee count: linkedin.com (Retrieved December 2023)
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- Shopify engineer count: linkedin.com (retrieved Dec 2023)
- Shopify employee count: s27.q4cdn.com (page 22)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Progress Software engineer count: sec.gov (page 7, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 7)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 14)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Interim Report, page 15)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 20)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 16)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 17)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 18)
- Twilio engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Zendesk engineer count: linkedin.com (retrieved Dec 2023)
- Zendesk employee count: linkedin.com (retrieved Dec 2023)
- Hyland engineer count: linkedin.com
- Hyland employee count: linkedin.com
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- CyberAgent engineer count: cyberagent.co.jp (page 8)
- CyberAgent employee count: cyberagent.co.jp (page 8)
- 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)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Spotify engineer count: sec.gov (page 68, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 68)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- BBC engineer count: linkedin.com
- BBC employee count: bbc.co.uk (page 59)
- 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)
- Autodesk engineer count: linkedin.com (retrieved Dec 2023)
- Autodesk employee count: sec.gov (page 13)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 7)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 60)
- 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)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 12)
- Salesforce engineer count: linkedin.com (retrieved Dec 2023)
- Salesforce employee count: sec.gov (page 10)
- 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
- Cisco Systems engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 10)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- Baidu engineer count: sec.gov (page 196, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 196)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- NetEase engineer count: sec.gov (page 156, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 156)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- 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)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 4)
- Samsung engineer count: samsung.com (page 58, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 58)
- Globant engineer count: sec.gov (page 79, referred to as employees in 'technology')
- Globant employee count: sec.gov (page 78)
- 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)
- Databricks employee count: linkedin.com
- Sentry.io employee count: linkedin.com
- Snyk employee count: linkedin.com
- PingCAP employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- Orange S.A. employee count: gallery.orange.com (page 58)
- Intuit employee count: sec.gov (page 12)
- Kitware employee count: linkedin.com
- DigitalOcean employee count: sec.gov (page 15)