Corporate GitHub Activity
Most Active Corporations on GitHub, 09 2021
Ranking companies with employees who, during 09 2021, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Grafana Labs | 41% 41% (n=99) of all Grafana Labs engineers (n=2401) were active on GitHub. | 25% 25% (n=99) of all Grafana Labs employees (n=4002) were active on GitHub. | 99 99 Grafana Labs employees were active on GitHub. | 
|---|---|---|---|
| 2. SUSE | 38% 38% (n=181) of all SUSE engineers (n=4753) were active on GitHub. | 9% 9% (n=181) of all SUSE employees (n=2,0454) were active on GitHub. | 181 181 SUSE employees were active on GitHub. | 
| 3. Automattic | 33% 33% (n=219) of all Automattic engineers (n=6655) were active on GitHub. | 13% 13% (n=219) of all Automattic employees (n=1,7006) were active on GitHub. | 219 219 Automattic employees were active on GitHub. | 
| 4. JetBrains | 27% 27% (n=155) of all JetBrains engineers (n=5757) were active on GitHub. | 8% 8% (n=155) of all JetBrains employees (n=1,9008) were active on GitHub. | 155 155 JetBrains employees were active on GitHub. | 
| 5. HashiCorp | 26% 26% (n=129) of all HashiCorp engineers (n=5009) were active on GitHub. | 7% 7% (n=129) of all HashiCorp employees (n=1,85010) were active on GitHub. | 129 129 HashiCorp employees were active on GitHub. | 
| 6. Mozilla | 26% 26% (n=141) of all Mozilla engineers (n=54711) were active on GitHub. | 10% 10% (n=141) of all Mozilla employees (n=1,38512) were active on GitHub. | 141 141 Mozilla employees were active on GitHub. | 
| 7. Elastic | 25% 25% (n=227) of all Elastic engineers (n=90513) were active on GitHub. | 8% 8% (n=227) of all Elastic employees (n=2,97814) were active on GitHub. | 227 227 Elastic employees were active on GitHub. | 
| 8. The Guardian | 23% 23% (n=26) of all The Guardian engineers (n=11215) were active on GitHub. | 1% 1% (n=26) of all The Guardian employees (n=2,13016) were active on GitHub. | 26 26 The Guardian employees were active on GitHub. | 
| 9. Mapbox | 18% 18% (n=46) of all Mapbox engineers (n=25017) were active on GitHub. | 8% 8% (n=46) of all Mapbox employees (n=60118) were active on GitHub. | 46 46 Mapbox employees were active on GitHub. | 
| 10. WikiMedia Foundation | 11% 11% (n=21) of all WikiMedia Foundation engineers (n=18519) were active on GitHub. | (n=21) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 21 21 WikiMedia Foundation employees were active on GitHub. | 
| 11. DataDog | 11% 11% (n=152) of all DataDog engineers (n=1,40020) were active on GitHub. | 5% 5% (n=152) of all DataDog employees (n=3,20021) were active on GitHub. | 152 152 DataDog employees were active on GitHub. | 
| 12. Cloudflare | 10% 10% (n=53) of all Cloudflare engineers (n=52622) were active on GitHub. | 2% 2% (n=53) of all Cloudflare employees (n=2,44023) were active on GitHub. | 53 53 Cloudflare employees were active on GitHub. | 
| 13. MongoDB | 9% 9% (n=79) of all MongoDB engineers (n=86324) were active on GitHub. | 2% 2% (n=79) of all MongoDB employees (n=3,54425) were active on GitHub. | 79 79 MongoDB employees were active on GitHub. | 
| 14. WSO2 | 8% 8% (n=70) of all WSO2 engineers (n=85026) were active on GitHub. | 7% 7% (n=70) of all WSO2 employees (n=97827) were active on GitHub. | 70 70 WSO2 employees were active on GitHub. | 
| 15. Confluent | 8% 8% (n=52) of all Confluent engineers (n=65928) were active on GitHub. | 3% 3% (n=52) of all Confluent employees (n=1,98129) were active on GitHub. | 52 52 Confluent employees were active on GitHub. | 
| 16. New Relic | 7% 7% (n=55) of all New Relic engineers (n=74430) were active on GitHub. | 2% 2% (n=55) of all New Relic employees (n=2,21731) were active on GitHub. | 55 55 New Relic employees were active on GitHub. | 
| 17. Liferay | 5% 5% (n=22) of all Liferay engineers (n=43132) were active on GitHub. | 2% 2% (n=22) of all Liferay employees (n=1,19233) were active on GitHub. | 22 22 Liferay employees were active on GitHub. | 
| 18. Microsoft | 5% 5% (n=2,767) of all Microsoft engineers (n=60,00034) were active on GitHub. | 2% 2% (n=2,767) of all Microsoft employees (n=181,00035) were active on GitHub. | 2,767 2,767 Microsoft employees were active on GitHub. | 
| 19. ESRI | 4% 4% (n=77) of all ESRI engineers (n=1,82036) were active on GitHub. | 1% 1% (n=77) of all ESRI employees (n=5,42937) were active on GitHub. | 77 77 ESRI employees were active on GitHub. | 
| 20. Okta | 4% 4% (n=52) of all Okta engineers (n=1,23138) were active on GitHub. | 1% 1% (n=52) of all Okta employees (n=5,03039) were active on GitHub. | 52 52 Okta employees were active on GitHub. | 
| 21. Unity Technologies | 4% 4% (n=116) of all Unity Technologies engineers (n=2,77640) were active on GitHub. | 2% 2% (n=116) of all Unity Technologies employees (n=5,24541) were active on GitHub. | 116 116 Unity Technologies employees were active on GitHub. | 
| 22. Square, Inc. | 4% 4% (n=61) of all Square, Inc. engineers (n=1,62142) were active on GitHub. | 1% 1% (n=61) of all Square, Inc. employees (n=8,52143) were active on GitHub. | 61 61 Square, Inc. employees were active on GitHub. | 
| 23. Progress Software | 4% 4% (n=29) of all Progress Software engineers (n=81844) were active on GitHub. | 1% 1% (n=29) of all Progress Software employees (n=2,10345) were active on GitHub. | 29 29 Progress Software employees were active on GitHub. | 
| 24. Alibaba | 4% 4% (n=326) of all Alibaba engineers (n=9,25546) were active on GitHub. | 0% 0% (n=326) of all Alibaba employees (n=251,46247) were active on GitHub. | 326 326 Alibaba employees were active on GitHub. | 
| 25. Shopify | 3% 3% (n=134) of all Shopify engineers (n=4,36048) were active on GitHub. | 1% 1% (n=134) of all Shopify employees (n=10,00049) were active on GitHub. | 134 134 Shopify employees were active on GitHub. | 
| 26. Splunk | 3% 3% (n=56) of all Splunk engineers (n=2,11850) were active on GitHub. | 1% 1% (n=56) of all Splunk employees (n=7,00051) were active on GitHub. | 56 56 Splunk employees were active on GitHub. | 
| 27. Snowflake, Inc. | 3% 3% (n=20) of all Snowflake, Inc. engineers (n=78852) were active on GitHub. | 1% 1% (n=20) of all Snowflake, Inc. employees (n=3,99253) were active on GitHub. | 20 20 Snowflake, Inc. employees were active on GitHub. | 
| 28. VMWare | 3% 3% (n=351) of all VMWare engineers (n=13,96554) were active on GitHub. | 1% 1% (n=351) of all VMWare employees (n=37,50055) were active on GitHub. | 351 351 VMWare employees were active on GitHub. | 
| 29. ThoughtWorks | 2% 2% (n=87) of all ThoughtWorks engineers (n=3,65856) were active on GitHub. | 1% 1% (n=87) of all ThoughtWorks employees (n=10,60057) were active on GitHub. | 87 87 ThoughtWorks employees were active on GitHub. | 
| 30. Netflix | 2% 2% (n=50) of all Netflix engineers (n=2,12158) were active on GitHub. | 0% 0% (n=50) of all Netflix employees (n=11,30059) were active on GitHub. | 50 50 Netflix employees were active on GitHub. | 
| 31. Tencent | 2% 2% (n=240) of all Tencent engineers (n=11,57260) were active on GitHub. | 0% 0% (n=240) of all Tencent employees (n=112,77161) were active on GitHub. | 240 240 Tencent employees were active on GitHub. | 
| 32. Zendesk | 2% 2% (n=34) of all Zendesk engineers (n=1,65062) were active on GitHub. | 1% 1% (n=34) of all Zendesk employees (n=5,86063) were active on GitHub. | 34 34 Zendesk employees were active on GitHub. | 
| 33. Amazon | 2% 2% (n=775) of all Amazon engineers (n=38,27764) were active on GitHub. | 1% 1% (n=775) of all Amazon employees (n=85,26665) were active on GitHub. | 775 775 Amazon employees were active on GitHub. | 
| 34. WIX | 2% 2% (n=47) of all WIX engineers (n=2,34966) were active on GitHub. | 1% 1% (n=47) of all WIX employees (n=5,05767) were active on GitHub. | 47 47 WIX employees were active on GitHub. | 
| 35. Twilio | 2% 2% (n=62) of all Twilio engineers (n=3,10368) were active on GitHub. | 1% 1% (n=62) of all Twilio employees (n=7,86769) were active on GitHub. | 62 62 Twilio employees were active on GitHub. | 
| 36. Google | 2% 2% (n=1,165) of all Google engineers (n=62,37770) were active on GitHub. | 1% 1% (n=1,165) of all Google employees (n=156,50071) were active on GitHub. | 1,165 1,165 Google employees were active on GitHub. | 
| 37. Spotify | 2% 2% (n=56) of all Spotify engineers (n=3,17572) were active on GitHub. | 1% 1% (n=56) of all Spotify employees (n=6,61773) were active on GitHub. | 56 56 Spotify employees were active on GitHub. | 
| 38. Lyft | 2% 2% (n=31) of all Lyft engineers (n=1,78174) were active on GitHub. | 1% 1% (n=31) of all Lyft employees (n=4,45375) were active on GitHub. | 31 31 Lyft employees were active on GitHub. | 
| 39. Zalando DE | 2% 2% (n=26) of all Zalando DE engineers (n=1,54676) were active on GitHub. | 0% 0% (n=26) of all Zalando DE employees (n=17,04377) were active on GitHub. | 26 26 Zalando DE employees were active on GitHub. | 
| 40. Adobe | 2% 2% (n=151) of all Adobe engineers (n=9,60178) were active on GitHub. | 1% 1% (n=151) of all Adobe employees (n=25,98879) were active on GitHub. | 151 151 Adobe employees were active on GitHub. | 
| 41. BBC | 1% 1% (n=20) of all BBC engineers (n=1,35880) were active on GitHub. | 0% 0% (n=20) of all BBC employees (n=22,21981) were active on GitHub. | 20 20 BBC employees were active on GitHub. | 
| 42. Stripe | 1% 1% (n=44) of all Stripe engineers (n=3,05082) were active on GitHub. | 1% 1% (n=44) of all Stripe employees (n=4,65383) were active on GitHub. | 44 44 Stripe employees were active on GitHub. | 
| 43. Airbnb | 1% 1% (n=23) of all Airbnb engineers (n=1,67584) were active on GitHub. | 0% 0% (n=23) of all Airbnb employees (n=6,13285) were active on GitHub. | 23 23 Airbnb employees were active on GitHub. | 
| 44. Atlassian | 1% 1% (n=43) of all Atlassian engineers (n=3,21686) were active on GitHub. | 1% 1% (n=43) of all Atlassian employees (n=6,43387) were active on GitHub. | 43 43 Atlassian employees were active on GitHub. | 
| 45. NVIDIA | 1% 1% (n=217) of all NVIDIA engineers (n=16,24288) were active on GitHub. | 1% 1% (n=217) of all NVIDIA employees (n=22,47389) were active on GitHub. | 217 217 NVIDIA employees were active on GitHub. | 
| 46. Twitter | 1% 1% (n=29) of all Twitter engineers (n=2,42490) were active on GitHub. | 0% 0% (n=29) of all Twitter employees (n=8,20091) were active on GitHub. | 29 29 Twitter employees were active on GitHub. | 
| 47. Uber | 1% 1% (n=55) of all Uber engineers (n=4,78492) were active on GitHub. | 0% 0% (n=55) of all Uber employees (n=29,30093) were active on GitHub. | 55 55 Uber employees were active on GitHub. | 
| 48. CyberAgent | 1% 1% (n=24) of all CyberAgent engineers (n=2,54994) were active on GitHub. | 0% 0% (n=24) of all CyberAgent employees (n=5,94495) were active on GitHub. | 24 24 CyberAgent employees were active on GitHub. | 
| 49. Salesforce | 1% 1% (n=175) of all Salesforce engineers (n=21,35996) were active on GitHub. | 0% 0% (n=175) of all Salesforce employees (n=73,54197) were active on GitHub. | 175 175 Salesforce employees were active on GitHub. | 
| 50. Autodesk | 1% 1% (n=27) of all Autodesk engineers (n=3,51998) were active on GitHub. | 0% 0% (n=27) of all Autodesk employees (n=11,50099) were active on GitHub. | 27 27 Autodesk employees were active on GitHub. | 
| 51. SAP SE | 1% 1% (n=239) of all SAP SE engineers (n=32,244100) were active on GitHub. | 0% 0% (n=239) of all SAP SE employees (n=107,415101) were active on GitHub. | 239 239 SAP SE employees were active on GitHub. | 
| 52. Yandex | 1% 1% (n=63) of all Yandex engineers (n=9,192102) were active on GitHub. | 0% 0% (n=63) of all Yandex employees (n=18,004103) were active on GitHub. | 63 63 Yandex employees were active on GitHub. | 
| 53. Bloomberg | 1% 1% (n=33) of all Bloomberg engineers (n=5,316104) were active on GitHub. | 0% 0% (n=33) of all Bloomberg employees (n=21,559105) were active on GitHub. | 33 33 Bloomberg employees were active on GitHub. | 
| 54. Intel | 1% 1% (n=373) of all Intel engineers (n=61,806106) were active on GitHub. | 0% 0% (n=373) of all Intel employees (n=121,100107) were active on GitHub. | 373 373 Intel employees were active on GitHub. | 
| 55. AMD | 0% 0% (n=50) of all AMD engineers (n=10,749108) were active on GitHub. | 0% 0% (n=50) of all AMD employees (n=15,500109) were active on GitHub. | 50 50 AMD employees were active on GitHub. | 
| 56. Apple | 0% 0% (n=130) of all Apple engineers (n=33,076110) were active on GitHub. | 0% 0% (n=130) of all Apple employees (n=154,000111) were active on GitHub. | 130 130 Apple employees were active on GitHub. | 
| 57. Baidu | 0% 0% (n=108) of all Baidu engineers (n=27,500112) were active on GitHub. | 0% 0% (n=108) of all Baidu employees (n=45,500113) were active on GitHub. | 108 108 Baidu employees were active on GitHub. | 
| 58. Oracle | 0% 0% (n=156) of all Oracle engineers (n=40,000114) were active on GitHub. | 0% 0% (n=156) of all Oracle employees (n=132,000115) were active on GitHub. | 156 156 Oracle employees were active on GitHub. | 
| 59. Cisco Systems | 0% 0% (n=83) of all Cisco Systems engineers (n=23,532116) were active on GitHub. | 0% 0% (n=83) of all Cisco Systems employees (n=79,500117) were active on GitHub. | 83 83 Cisco Systems employees were active on GitHub. | 
| 60. NetEase | 0% 0% (n=47) of all NetEase engineers (n=15,292118) were active on GitHub. | 0% 0% (n=47) of all NetEase employees (n=32,064119) were active on GitHub. | 47 47 NetEase employees were active on GitHub. | 
| 61. PayPal | 0% 0% (n=28) of all PayPal engineers (n=9,157120) were active on GitHub. | 0% 0% (n=28) of all PayPal employees (n=30,900121) were active on GitHub. | 28 28 PayPal employees were active on GitHub. | 
| 62. EPAM Systems | 0% 0% (n=88) of all EPAM Systems engineers (n=52,617122) were active on GitHub. | 0% 0% (n=88) of all EPAM Systems employees (n=58,824123) were active on GitHub. | 88 88 EPAM Systems employees were active on GitHub. | 
| 63. Ericsson | 0% 0% (n=36) of all Ericsson engineers (n=27,379124) were active on GitHub. | 0% 0% (n=36) of all Ericsson employees (n=101,322125) were active on GitHub. | 36 36 Ericsson employees were active on GitHub. | 
| 64. Nokia | 0% 0% (n=23) of all Nokia engineers (n=22,030126) were active on GitHub. | 0% 0% (n=23) of all Nokia employees (n=87,927127) were active on GitHub. | 23 23 Nokia employees were active on GitHub. | 
| 65. Capgemini | 0% 0% (n=43) of all Capgemini engineers (n=67,119128) were active on GitHub. | 0% 0% (n=43) of all Capgemini employees (n=325,000129) were active on GitHub. | 43 43 Capgemini employees were active on GitHub. | 
| 66. Samsung | 0% 0% (n=46) of all Samsung engineers (n=75,229130) were active on GitHub. | 0% 0% (n=46) of all Samsung employees (n=266,673131) were active on GitHub. | 46 46 Samsung employees were active on GitHub. | 
| 67. Huawei | 0% 0% (n=51) of all Huawei engineers (n=107,000132) were active on GitHub. | 0% 0% (n=51) of all Huawei employees (n=195,000133) were active on GitHub. | 51 51 Huawei employees were active on GitHub. | 
| 68. IBM | (n=1,560) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,560) of all IBM employees (n=282,100134) were active on GitHub. | 1,560 1,560 IBM employees were active on GitHub. | 
| 69. Facebook | (n=282) of all Facebook engineers (n=NaN0) were active on GitHub. | 0% 0% (n=282) of all Facebook employees (n=71,970135) were active on GitHub. | 282 282 Facebook employees were active on GitHub. | 
| 70. Arm Ltd | (n=103) of all Arm Ltd engineers (n=NaN0) were active on GitHub. | (n=103) of all Arm Ltd employees (n=NaN0) were active on GitHub. | 103 103 Arm Ltd employees were active on GitHub. | 
| 71. ByteDance | (n=94) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=94) of all ByteDance employees (n=NaN0) were active on GitHub. | 94 94 ByteDance employees were active on GitHub. | 
| 72. Canonical | (n=72) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=72) of all Canonical employees (n=NaN0) were active on GitHub. | 72 72 Canonical employees were active on GitHub. | 
| 73. Trybe | (n=61) of all Trybe engineers (n=NaN0) were active on GitHub. | (n=61) of all Trybe employees (n=NaN0) were active on GitHub. | 61 61 Trybe employees were active on GitHub. | 
| 74. Accenture | (n=59) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=59) of all Accenture employees (n=624,000136) were active on GitHub. | 59 59 Accenture employees were active on GitHub. | 
| 75. Yahoo! | (n=53) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=53) of all Yahoo! employees (n=NaN0) were active on GitHub. | 53 53 Yahoo! employees were active on GitHub. | 
| 76. PingCAP | (n=50) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=50) of all PingCAP employees (n=NaN0) were active on GitHub. | 50 50 PingCAP employees were active on GitHub. | 
| 77. Sentry.io | (n=38) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=38) of all Sentry.io employees (n=NaN0) were active on GitHub. | 38 38 Sentry.io employees were active on GitHub. | 
| 78. Snyk | (n=36) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=36) of all Snyk employees (n=NaN0) were active on GitHub. | 36 36 Snyk employees were active on GitHub. | 
| 79. Databricks | (n=35) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=35) of all Databricks employees (n=NaN0) were active on GitHub. | 35 35 Databricks employees were active on GitHub. | 
| 80. CircleCI | (n=32) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=32) of all CircleCI employees (n=NaN0) were active on GitHub. | 32 32 CircleCI employees were active on GitHub. | 
| 81. Cloudera | (n=29) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=29) of all Cloudera employees (n=NaN0) were active on GitHub. | 29 29 Cloudera employees were active on GitHub. | 
| 82. Palo Alto Networks | (n=27) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=27) of all Palo Alto Networks employees (n=10,473137) were active on GitHub. | 27 27 Palo Alto Networks employees were active on GitHub. | 
| 83. Intuit | (n=27) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=27) of all Intuit employees (n=13,500138) were active on GitHub. | 27 27 Intuit employees were active on GitHub. | 
| 84. DigitalOcean | (n=26) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 3% 3% (n=26) of all DigitalOcean employees (n=786139) were active on GitHub. | 26 26 DigitalOcean employees were active on GitHub. | 
| 85. RStudio | (n=26) of all RStudio engineers (n=NaN0) were active on GitHub. | (n=26) of all RStudio employees (n=NaN0) were active on GitHub. | 26 26 RStudio employees were active on GitHub. | 
| 86. HERE Technologies | (n=25) of all HERE Technologies engineers (n=NaN0) were active on GitHub. | (n=25) of all HERE Technologies employees (n=NaN0) were active on GitHub. | 25 25 HERE Technologies employees were active on GitHub. | 
| 87. Broad Institute | (n=23) of all Broad Institute engineers (n=NaN0) were active on GitHub. | (n=23) of all Broad Institute employees (n=NaN0) were active on GitHub. | 23 23 Broad Institute employees were active on GitHub. | 
| 88. Software Mansion | (n=23) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=23) of all Software Mansion employees (n=NaN0) were active on GitHub. | 23 23 Software Mansion employees were active on GitHub. | 
| 89. TU Delft | (n=22) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=22) of all TU Delft employees (n=NaN0) were active on GitHub. | 22 22 TU Delft employees were active on GitHub. | 
| 90. Camptocamp | (n=22) of all Camptocamp engineers (n=NaN0) were active on GitHub. | (n=22) of all Camptocamp employees (n=NaN0) were active on GitHub. | 22 22 Camptocamp employees were active on GitHub. | 
| 91. Ascensio System SIA | (n=22) of all Ascensio System SIA engineers (n=NaN0) were active on GitHub. | (n=22) of all Ascensio System SIA employees (n=NaN0) were active on GitHub. | 22 22 Ascensio System SIA employees were active on GitHub. | 
| 92. Kitware | (n=22) of all Kitware engineers (n=NaN0) were active on GitHub. | 13% 13% (n=22) of all Kitware employees (n=163140) were active on GitHub. | 22 22 Kitware employees were active on GitHub. | 
| 93. @wazuh | (n=21) of all @wazuh engineers (n=NaN0) were active on GitHub. | (n=21) of all @wazuh employees (n=NaN0) were active on GitHub. | 21 21 @wazuh employees were active on GitHub. | 
| 94. @sourcegraph | (n=20) of all @sourcegraph engineers (n=NaN0) were active on GitHub. | (n=20) of all @sourcegraph employees (n=NaN0) were active on GitHub. | 20 20 @sourcegraph employees were active on GitHub. | 
| 95. Puppet Labs | (n=19) of all Puppet Labs engineers (n=NaN0) were active on GitHub. | (n=19) of all Puppet Labs employees (n=NaN0) were active on GitHub. | 19 19 Puppet Labs employees were active on GitHub. | 
| 96. Shopee | (n=19) of all Shopee engineers (n=NaN0) were active on GitHub. | (n=19) of all Shopee employees (n=NaN0) were active on GitHub. | 19 19 Shopee employees were active on GitHub. | 
| 97. Talend | (n=19) of all Talend engineers (n=NaN0) were active on GitHub. | (n=19) of all Talend employees (n=NaN0) were active on GitHub. | 19 19 Talend employees were active on GitHub. | 
| 98. VTEX | (n=18) of all VTEX engineers (n=NaN0) were active on GitHub. | (n=18) of all VTEX employees (n=NaN0) were active on GitHub. | 18 18 VTEX employees were active on GitHub. | 
| 99. 광주소프트웨어마이스터고등학교 | (n=18) of all 광주소프트웨어마이스터고등학교 engineers (n=NaN0) were active on GitHub. | (n=18) of all 광주소프트웨어마이스터고등학교 employees (n=NaN0) were active on GitHub. | 18 18 광주소프트웨어마이스터고등학교 employees were active on GitHub. | 
| 100. @bytedance | (n=18) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=18) of all @bytedance employees (n=NaN0) were active on GitHub. | 18 18 @bytedance employees were active on GitHub. | 
References
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- SUSE engineer count: linkedin.com
- SUSE employee count: ir.suse.com (Annual Report FY21, page 228)
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved March 2022)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 14)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- WikiMedia Foundation engineer 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 16)
- MongoDB engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 8)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 14)
- New Relic engineer count: linkedin.com
- New Relic employee count: sec.gov (page 8)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Microsoft engineer count: sec.gov (page 8, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 8)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 13)
- Unity Technologies engineer count: sec.gov (page 11, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 11)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 13)
- Progress Software engineer count: sec.gov (page 9, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 9)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Annual Report, page 168)
- Shopify engineer count: linkedin.com
- Shopify employee count: s27.q4cdn.com (page 22)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 12)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 14)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 75)
- Zendesk engineer count: sec.gov (page 9, referred to as employees in 'research and development')
- Zendesk employee count: sec.gov (page 54)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- WIX engineer count: sec.gov (page 139, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 139)
- Twilio engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 12)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 9)
- Spotify engineer count: sec.gov (page 69, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 69)
- Lyft engineer count: sec.gov (page 12, referred to as employees in 'product management, engineering, design and science')
- Lyft employee count: sec.gov (page 12)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 16)
- BBC engineer count: linkedin.com
- BBC employee count: downloads.bbc.co.uk (page 53)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Airbnb engineer count: sec.gov (page 5)
- Airbnb employee count: sec.gov (page 6)
- Atlassian engineer count: sec.gov (page 65, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 78)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Twitter engineer count: linkedin.com
- Twitter employee count: sec.gov (page 11)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 8)
- CyberAgent engineer count: d2utiq8et4vl56.cloudfront.net (page 30, referred to as 'engineers and creators')
- CyberAgent employee count: d2utiq8et4vl56.cloudfront.net (page 127)
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 9)
- Autodesk engineer count: linkedin.com
- Autodesk employee count: sec.gov (page 13)
- SAP SE engineer count: sec.gov (page F-22, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 84)
- Yandex engineer count: sec.gov (page 50, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 50)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 13)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- Baidu engineer count: sec.gov (page 185, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 185)
- Oracle engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 14)
- 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 146, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 146)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- EPAM Systems engineer count: sec.gov (page 5, referred to as 'core information technology professionals as well as designers, consultants and scientists')
- EPAM Systems employee count: sec.gov (page 5)
- Ericsson engineer count: sec.gov (page 9, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- Nokia engineer count: linkedin.com
- Nokia employee count: sec.gov (page 61)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 3)
- Samsung engineer count: samsung.com (page 103, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 103)
- Huawei engineer count: www-file.huawei.com (page 72, referred to as employees in 'R&D')
- Huawei employee count: www-file.huawei.com (page 2)
- IBM employee count: ibm.com (page 15)
- Facebook employee count: sec.gov (page 10)
- Accenture employee count: sec.gov (page 21)
- Palo Alto Networks employee count: sec.gov (page 11)
- Intuit employee count: sec.gov (page 14)
- DigitalOcean employee count: sec.gov (page 15)
- Kitware employee count: linkedin.com