Corporate GitHub Activity
Most Active Corporations on GitHub, 12 2022
Ranking companies with employees who, during 12 2022, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Grafana Labs | 48% 48% (n=165) of all Grafana Labs engineers (n=3431) were active on GitHub. | 28% 28% (n=165) of all Grafana Labs employees (n=6002) were active on GitHub. | 165 165 Grafana Labs employees were active on GitHub. | 
|---|---|---|---|
| 2. SUSE | 38% 38% (n=200) of all SUSE engineers (n=5223) were active on GitHub. | 8% 8% (n=200) of all SUSE employees (n=2,3984) were active on GitHub. | 200 200 SUSE employees were active on GitHub. | 
| 3. Automattic | 31% 31% (n=258) of all Automattic engineers (n=8305) were active on GitHub. | 13% 13% (n=258) of all Automattic employees (n=2,0026) were active on GitHub. | 258 258 Automattic employees were active on GitHub. | 
| 4. Mozilla | 29% 29% (n=139) of all Mozilla engineers (n=4727) were active on GitHub. | 9% 9% (n=139) of all Mozilla employees (n=1,5108) were active on GitHub. | 139 139 Mozilla employees were active on GitHub. | 
| 5. Docker | 27% 27% (n=27) of all Docker engineers (n=1019) were active on GitHub. | 6% 6% (n=27) of all Docker employees (n=43510) were active on GitHub. | 27 27 Docker employees were active on GitHub. | 
| 6. Elastic | 24% 24% (n=222) of all Elastic engineers (n=91411) were active on GitHub. | 8% 8% (n=222) of all Elastic employees (n=2,88612) were active on GitHub. | 222 222 Elastic employees were active on GitHub. | 
| 7. HashiCorp | 24% 24% (n=160) of all HashiCorp engineers (n=67013) were active on GitHub. | 7% 7% (n=160) of all HashiCorp employees (n=2,40014) were active on GitHub. | 160 160 HashiCorp employees were active on GitHub. | 
| 8. The Guardian | 22% 22% (n=28) of all The Guardian engineers (n=12715) were active on GitHub. | 1% 1% (n=28) of all The Guardian employees (n=2,30016) were active on GitHub. | 28 28 The Guardian employees were active on GitHub. | 
| 9. JetBrains | 20% 20% (n=144) of all JetBrains engineers (n=71917) were active on GitHub. | 8% 8% (n=144) of all JetBrains employees (n=1,90018) were active on GitHub. | 144 144 JetBrains employees were active on GitHub. | 
| 10. Vercel | 16% 16% (n=19) of all Vercel engineers (n=11819) were active on GitHub. | 5% 5% (n=19) of all Vercel employees (n=39820) were active on GitHub. | 19 19 Vercel employees were active on GitHub. | 
| 11. Mapbox | 13% 13% (n=33) of all Mapbox engineers (n=25821) were active on GitHub. | 5% 5% (n=33) of all Mapbox employees (n=67822) were active on GitHub. | 33 33 Mapbox employees were active on GitHub. | 
| 12. WikiMedia Foundation | 12% 12% (n=23) of all WikiMedia Foundation engineers (n=19423) were active on GitHub. | (n=23) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 23 23 WikiMedia Foundation employees were active on GitHub. | 
| 13. Cloudflare | 11% 11% (n=66) of all Cloudflare engineers (n=61024) were active on GitHub. | 2% 2% (n=66) of all Cloudflare employees (n=3,21725) were active on GitHub. | 66 66 Cloudflare employees were active on GitHub. | 
| 14. DataDog | 10% 10% (n=194) of all DataDog engineers (n=2,00026) were active on GitHub. | 4% 4% (n=194) of all DataDog employees (n=4,80027) were active on GitHub. | 194 194 DataDog employees were active on GitHub. | 
| 15. MongoDB | 9% 9% (n=96) of all MongoDB engineers (n=1,03028) were active on GitHub. | 2% 2% (n=96) of all MongoDB employees (n=4,61929) were active on GitHub. | 96 96 MongoDB employees were active on GitHub. | 
| 16. New Relic | 7% 7% (n=56) of all New Relic engineers (n=81930) were active on GitHub. | 2% 2% (n=56) of all New Relic employees (n=2,66331) were active on GitHub. | 56 56 New Relic employees were active on GitHub. | 
| 17. WSO2 | 6% 6% (n=45) of all WSO2 engineers (n=77532) were active on GitHub. | 4% 4% (n=45) of all WSO2 employees (n=1,16533) were active on GitHub. | 45 45 WSO2 employees were active on GitHub. | 
| 18. GitLab | 5% 5% (n=24) of all GitLab engineers (n=49434) were active on GitHub. | 1% 1% (n=24) of all GitLab employees (n=2,17035) were active on GitHub. | 24 24 GitLab employees were active on GitHub. | 
| 19. Odoo | 5% 5% (n=22) of all Odoo engineers (n=47436) were active on GitHub. | 2% 2% (n=22) of all Odoo employees (n=1,32737) were active on GitHub. | 22 22 Odoo employees were active on GitHub. | 
| 20. Confluent | 4% 4% (n=34) of all Confluent engineers (n=81838) were active on GitHub. | 1% 1% (n=34) of all Confluent employees (n=2,76139) were active on GitHub. | 34 34 Confluent employees were active on GitHub. | 
| 21. ESRI | 4% 4% (n=74) of all ESRI engineers (n=1,94740) were active on GitHub. | 1% 1% (n=74) of all ESRI employees (n=5,87341) were active on GitHub. | 74 74 ESRI employees were active on GitHub. | 
| 22. Shopify | 4% 4% (n=151) of all Shopify engineers (n=4,03742) were active on GitHub. | 1% 1% (n=151) of all Shopify employees (n=11,60043) were active on GitHub. | 151 151 Shopify employees were active on GitHub. | 
| 23. Square, Inc. | 4% 4% (n=68) of all Square, Inc. engineers (n=1,83144) were active on GitHub. | 1% 1% (n=68) of all Square, Inc. employees (n=12,42845) were active on GitHub. | 68 68 Square, Inc. employees were active on GitHub. | 
| 24. Microsoft | 3% 3% (n=2,522) of all Microsoft engineers (n=73,00046) were active on GitHub. | 1% 1% (n=2,522) of all Microsoft employees (n=221,00047) were active on GitHub. | 2,522 2,522 Microsoft employees were active on GitHub. | 
| 25. Okta | 3% 3% (n=44) of all Okta engineers (n=1,39248) were active on GitHub. | 1% 1% (n=44) of all Okta employees (n=6,01349) were active on GitHub. | 44 44 Okta employees were active on GitHub. | 
| 26. Alibaba | 3% 3% (n=281) of all Alibaba engineers (n=9,44050) were active on GitHub. | 0% 0% (n=281) of all Alibaba employees (n=254,94151) were active on GitHub. | 281 281 Alibaba employees were active on GitHub. | 
| 27. Snowflake, Inc. | 3% 3% (n=35) of all Snowflake, Inc. engineers (n=1,37852) were active on GitHub. | 1% 1% (n=35) of all Snowflake, Inc. employees (n=5,88453) were active on GitHub. | 35 35 Snowflake, Inc. employees were active on GitHub. | 
| 28. VMWare | 2% 2% (n=324) of all VMWare engineers (n=13,33254) were active on GitHub. | 1% 1% (n=324) of all VMWare employees (n=38,30055) were active on GitHub. | 324 324 VMWare employees were active on GitHub. | 
| 29. Twitter | 2% 2% (n=33) of all Twitter engineers (n=1,36956) were active on GitHub. | 0% 0% (n=33) of all Twitter employees (n=9,40057) were active on GitHub. | 33 33 Twitter employees were active on GitHub. | 
| 30. Amazon | 2% 2% (n=895) of all Amazon engineers (n=37,13458) were active on GitHub. | 1% 1% (n=895) of all Amazon employees (n=112,31559) were active on GitHub. | 895 895 Amazon employees were active on GitHub. | 
| 31. Netflix | 2% 2% (n=46) of all Netflix engineers (n=2,22760) were active on GitHub. | 0% 0% (n=46) of all Netflix employees (n=12,80061) were active on GitHub. | 46 46 Netflix employees were active on GitHub. | 
| 32. ThoughtWorks | 2% 2% (n=83) of all ThoughtWorks engineers (n=4,15262) were active on GitHub. | 1% 1% (n=83) of all ThoughtWorks employees (n=12,50063) were active on GitHub. | 83 83 ThoughtWorks employees were active on GitHub. | 
| 33. WIX | 2% 2% (n=43) of all WIX engineers (n=2,20664) were active on GitHub. | 1% 1% (n=43) of all WIX employees (n=4,74265) were active on GitHub. | 43 43 WIX employees were active on GitHub. | 
| 34. Unity Technologies | 2% 2% (n=69) of all Unity Technologies engineers (n=3,75366) were active on GitHub. | 1% 1% (n=69) of all Unity Technologies employees (n=7,70367) were active on GitHub. | 69 69 Unity Technologies employees were active on GitHub. | 
| 35. Google | 2% 2% (n=1,256) of all Google engineers (n=71,08468) were active on GitHub. | 1% 1% (n=1,256) of all Google employees (n=190,23469) were active on GitHub. | 1,256 1,256 Google employees were active on GitHub. | 
| 36. Arm Ltd | 2% 2% (n=82) of all Arm Ltd engineers (n=4,75870) were active on GitHub. | 1% 1% (n=82) of all Arm Ltd employees (n=6,32971) were active on GitHub. | 82 82 Arm Ltd employees were active on GitHub. | 
| 37. Stripe | 2% 2% (n=48) of all Stripe engineers (n=2,96172) were active on GitHub. | 1% 1% (n=48) of all Stripe employees (n=8,37273) were active on GitHub. | 48 48 Stripe employees were active on GitHub. | 
| 38. Tencent | 2% 2% (n=208) of all Tencent engineers (n=12,97974) were active on GitHub. | 0% 0% (n=208) of all Tencent employees (n=108,43675) were active on GitHub. | 208 208 Tencent employees were active on GitHub. | 
| 39. Splunk | 2% 2% (n=33) of all Splunk engineers (n=2,07676) were active on GitHub. | 0% 0% (n=33) of all Splunk employees (n=8,00077) were active on GitHub. | 33 33 Splunk employees were active on GitHub. | 
| 40. Zendesk | 2% 2% (n=25) of all Zendesk engineers (n=1,62078) were active on GitHub. | 0% 0% (n=25) of all Zendesk employees (n=6,44079) were active on GitHub. | 25 25 Zendesk employees were active on GitHub. | 
| 41. Zalando DE | 1% 1% (n=24) of all Zalando DE engineers (n=1,60880) were active on GitHub. | 0% 0% (n=24) of all Zalando DE employees (n=16,99981) were active on GitHub. | 24 24 Zalando DE employees were active on GitHub. | 
| 42. Adobe | 1% 1% (n=139) of all Adobe engineers (n=9,45082) were active on GitHub. | 0% 0% (n=139) of all Adobe employees (n=29,23983) were active on GitHub. | 139 139 Adobe employees were active on GitHub. | 
| 43. CyberAgent | 1% 1% (n=21) of all CyberAgent engineers (n=1,47084) were active on GitHub. | 0% 0% (n=21) of all CyberAgent employees (n=6,33785) were active on GitHub. | 21 21 CyberAgent employees were active on GitHub. | 
| 44. Twilio | 1% 1% (n=51) of all Twilio engineers (n=3,59086) were active on GitHub. | 1% 1% (n=51) of all Twilio employees (n=8,15687) were active on GitHub. | 51 51 Twilio employees were active on GitHub. | 
| 45. Lyft | 1% 1% (n=25) of all Lyft engineers (n=1,81188) were active on GitHub. | 1% 1% (n=25) of all Lyft employees (n=4,41989) were active on GitHub. | 25 25 Lyft employees were active on GitHub. | 
| 46. NVIDIA | 1% 1% (n=240) of all NVIDIA engineers (n=19,53290) were active on GitHub. | 1% 1% (n=240) of all NVIDIA employees (n=26,19691) were active on GitHub. | 240 240 NVIDIA employees were active on GitHub. | 
| 47. Spotify | 1% 1% (n=45) of all Spotify engineers (n=4,16992) were active on GitHub. | 1% 1% (n=45) of all Spotify employees (n=8,35993) were active on GitHub. | 45 45 Spotify employees were active on GitHub. | 
| 48. Indeed | 1% 1% (n=24) of all Indeed engineers (n=2,45794) were active on GitHub. | 0% 0% (n=24) of all Indeed employees (n=16,38795) were active on GitHub. | 24 24 Indeed employees were active on GitHub. | 
| 49. Atlassian | 1% 1% (n=43) of all Atlassian engineers (n=4,40696) were active on GitHub. | 0% 0% (n=43) of all Atlassian employees (n=8,81397) were active on GitHub. | 43 43 Atlassian employees were active on GitHub. | 
| 50. Uber | 1% 1% (n=48) of all Uber engineers (n=5,50298) were active on GitHub. | 0% 0% (n=48) of all Uber employees (n=32,80099) were active on GitHub. | 48 48 Uber employees were active on GitHub. | 
| 51. Meta | 1% 1% (n=272) of all Meta engineers (n=35,611100) were active on GitHub. | 0% 0% (n=272) of all Meta employees (n=86,482101) were active on GitHub. | 272 272 Meta employees were active on GitHub. | 
| 52. Intel | 1% 1% (n=421) of all Intel engineers (n=57,090102) were active on GitHub. | 0% 0% (n=421) of all Intel employees (n=131,900103) were active on GitHub. | 421 421 Intel employees were active on GitHub. | 
| 53. SAP SE | 1% 1% (n=235) of all SAP SE engineers (n=34,122104) were active on GitHub. | 0% 0% (n=235) of all SAP SE employees (n=111,961105) were active on GitHub. | 235 235 SAP SE employees were active on GitHub. | 
| 54. Salesforce | 1% 1% (n=139) of all Salesforce engineers (n=20,537106) were active on GitHub. | 0% 0% (n=139) of all Salesforce employees (n=79,390107) were active on GitHub. | 139 139 Salesforce employees were active on GitHub. | 
| 55. AMD | 1% 1% (n=82) of all AMD engineers (n=12,146108) were active on GitHub. | 0% 0% (n=82) of all AMD employees (n=25,000109) were active on GitHub. | 82 82 AMD employees were active on GitHub. | 
| 56. Yandex | 1% 1% (n=62) of all Yandex engineers (n=10,708110) were active on GitHub. | 0% 0% (n=62) of all Yandex employees (n=20,850111) were active on GitHub. | 62 62 Yandex employees were active on GitHub. | 
| 57. Autodesk | 1% 1% (n=20) of all Autodesk engineers (n=3,800112) were active on GitHub. | 0% 0% (n=20) of all Autodesk employees (n=13,700113) were active on GitHub. | 20 20 Autodesk employees were active on GitHub. | 
| 58. Baidu | 0% 0% (n=103) of all Baidu engineers (n=23,600114) were active on GitHub. | 0% 0% (n=103) of all Baidu employees (n=41,300115) were active on GitHub. | 103 103 Baidu employees were active on GitHub. | 
| 59. Bloomberg | 0% 0% (n=25) of all Bloomberg engineers (n=6,326116) were active on GitHub. | 0% 0% (n=25) of all Bloomberg employees (n=23,033117) were active on GitHub. | 25 25 Bloomberg employees were active on GitHub. | 
| 60. Cisco Systems | 0% 0% (n=90) of all Cisco Systems engineers (n=23,407118) were active on GitHub. | 0% 0% (n=90) of all Cisco Systems employees (n=83,300119) were active on GitHub. | 90 90 Cisco Systems employees were active on GitHub. | 
| 61. PayPal | 0% 0% (n=29) of all PayPal engineers (n=8,805120) were active on GitHub. | 0% 0% (n=29) of all PayPal employees (n=29,900121) were active on GitHub. | 29 29 PayPal employees were active on GitHub. | 
| 62. Apple | 0% 0% (n=129) of all Apple engineers (n=39,361122) were active on GitHub. | 0% 0% (n=129) of all Apple employees (n=164,000123) were active on GitHub. | 129 129 Apple employees were active on GitHub. | 
| 63. NetEase | 0% 0% (n=48) of all NetEase engineers (n=15,211124) were active on GitHub. | 0% 0% (n=48) of all NetEase employees (n=31,119125) were active on GitHub. | 48 48 NetEase employees were active on GitHub. | 
| 64. Oracle | 0% 0% (n=134) of all Oracle engineers (n=44,000126) were active on GitHub. | 0% 0% (n=134) of all Oracle employees (n=143,000127) were active on GitHub. | 134 134 Oracle employees were active on GitHub. | 
| 65. EPAM Systems | 0% 0% (n=88) of all EPAM Systems engineers (n=52,850128) were active on GitHub. | 0% 0% (n=88) of all EPAM Systems employees (n=59,300129) were active on GitHub. | 88 88 EPAM Systems employees were active on GitHub. | 
| 66. Ericsson | 0% 0% (n=32) of all Ericsson engineers (n=29,304130) were active on GitHub. | 0% 0% (n=32) of all Ericsson employees (n=105,529131) were active on GitHub. | 32 32 Ericsson employees were active on GitHub. | 
| 67. Nokia | 0% 0% (n=19) of all Nokia engineers (n=23,836132) were active on GitHub. | 0% 0% (n=19) of all Nokia employees (n=86,896133) were active on GitHub. | 19 19 Nokia employees were active on GitHub. | 
| 68. Samsung | 0% 0% (n=62) of all Samsung engineers (n=80,496134) were active on GitHub. | 0% 0% (n=62) of all Samsung employees (n=270,372135) were active on GitHub. | 62 62 Samsung employees were active on GitHub. | 
| 69. Capgemini | 0% 0% (n=50) of all Capgemini engineers (n=69,803136) were active on GitHub. | 0% 0% (n=50) of all Capgemini employees (n=360,000137) were active on GitHub. | 50 50 Capgemini employees were active on GitHub. | 
| 70. Huawei | 0% 0% (n=60) of all Huawei engineers (n=114,000138) were active on GitHub. | 0% 0% (n=60) of all Huawei employees (n=207,000139) were active on GitHub. | 60 60 Huawei employees were active on GitHub. | 
| 71. IBM | (n=1,425) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=1,425) of all IBM employees (n=288,300140) were active on GitHub. | 1,425 1,425 IBM employees were active on GitHub. | 
| 72. Canonical | (n=82) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=82) of all Canonical employees (n=NaN0) were active on GitHub. | 82 82 Canonical employees were active on GitHub. | 
| 73. ByteDance | (n=82) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=82) of all ByteDance employees (n=NaN0) were active on GitHub. | 82 82 ByteDance employees were active on GitHub. | 
| 74. Sentry.io | (n=57) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=57) of all Sentry.io employees (n=NaN0) were active on GitHub. | 57 57 Sentry.io employees were active on GitHub. | 
| 75. Accenture | (n=52) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=52) of all Accenture employees (n=721,000141) were active on GitHub. | 52 52 Accenture employees were active on GitHub. | 
| 76. Yahoo! | (n=49) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=49) of all Yahoo! employees (n=NaN0) were active on GitHub. | 49 49 Yahoo! employees were active on GitHub. | 
| 77. Databricks | (n=48) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=48) of all Databricks employees (n=NaN0) were active on GitHub. | 48 48 Databricks 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. PingCAP | (n=41) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=41) of all PingCAP employees (n=NaN0) were active on GitHub. | 41 41 PingCAP employees were active on GitHub. | 
| 80. Apple Developer Academy @ POSTECH | (n=37) of all Apple Developer Academy @ POSTECH engineers (n=NaN0) were active on GitHub. | (n=37) of all Apple Developer Academy @ POSTECH employees (n=NaN0) were active on GitHub. | 37 37 Apple Developer Academy @ POSTECH employees were active on GitHub. | 
| 81. Masai | (n=34) of all Masai engineers (n=NaN0) were active on GitHub. | (n=34) of all Masai employees (n=NaN0) were active on GitHub. | 34 34 Masai employees were active on GitHub. | 
| 82. Posit | (n=34) of all Posit engineers (n=NaN0) were active on GitHub. | (n=34) of all Posit employees (n=NaN0) were active on GitHub. | 34 34 Posit employees were active on GitHub. | 
| 83. Snyk | (n=31) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=31) of all Snyk employees (n=NaN0) were active on GitHub. | 31 31 Snyk employees were active on GitHub. | 
| 84. Palo Alto Networks | (n=29) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=29) of all Palo Alto Networks employees (n=12,561142) were active on GitHub. | 29 29 Palo Alto Networks employees were active on GitHub. | 
| 85. Kitware | (n=29) of all Kitware engineers (n=NaN0) were active on GitHub. | 17% 17% (n=29) of all Kitware employees (n=174143) were active on GitHub. | 29 29 Kitware employees were active on GitHub. | 
| 86. @bytedance | (n=29) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=29) of all @bytedance employees (n=NaN0) were active on GitHub. | 29 29 @bytedance employees were active on GitHub. | 
| 87. R3 | (n=28) of all R3 engineers (n=NaN0) were active on GitHub. | (n=28) of all R3 employees (n=NaN0) were active on GitHub. | 28 28 R3 employees were active on GitHub. | 
| 88. DigitalOcean | (n=23) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 2% 2% (n=23) of all DigitalOcean employees (n=1,204144) were active on GitHub. | 23 23 DigitalOcean employees were active on GitHub. | 
| 89. @vercel | (n=23) of all @vercel engineers (n=NaN0) were active on GitHub. | (n=23) of all @vercel employees (n=NaN0) were active on GitHub. | 23 23 @vercel employees were active on GitHub. | 
| 90. Protocol Labs | (n=23) of all Protocol Labs engineers (n=NaN0) were active on GitHub. | (n=23) of all Protocol Labs employees (n=NaN0) were active on GitHub. | 23 23 Protocol Labs employees were active on GitHub. | 
| 91. @apache | (n=23) of all @apache engineers (n=NaN0) were active on GitHub. | (n=23) of all @apache employees (n=NaN0) were active on GitHub. | 23 23 @apache employees were active on GitHub. | 
| 92. 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. | 
| 93. 100Devs | (n=22) of all 100Devs engineers (n=NaN0) were active on GitHub. | (n=22) of all 100Devs employees (n=NaN0) were active on GitHub. | 22 22 100Devs employees were active on GitHub. | 
| 94. UCL | (n=21) of all UCL engineers (n=NaN0) were active on GitHub. | (n=21) of all UCL employees (n=NaN0) were active on GitHub. | 21 21 UCL employees were active on GitHub. | 
| 95. CircleCI | (n=21) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=21) of all CircleCI employees (n=NaN0) were active on GitHub. | 21 21 CircleCI employees were active on GitHub. | 
| 96. @espressif | (n=20) of all @espressif engineers (n=NaN0) were active on GitHub. | (n=20) of all @espressif employees (n=NaN0) were active on GitHub. | 20 20 @espressif employees were active on GitHub. | 
| 97. @paritytech | (n=20) of all @paritytech engineers (n=NaN0) were active on GitHub. | (n=20) of all @paritytech employees (n=NaN0) were active on GitHub. | 20 20 @paritytech employees were active on GitHub. | 
| 98. Harness | (n=19) of all Harness engineers (n=NaN0) were active on GitHub. | (n=19) of all Harness employees (n=NaN0) were active on GitHub. | 19 19 Harness employees were active on GitHub. | 
| 99. @protocol | (n=19) of all @protocol engineers (n=NaN0) were active on GitHub. | (n=19) of all @protocol employees (n=NaN0) were active on GitHub. | 19 19 @protocol employees were active on GitHub. | 
| 100. Dynatrace | (n=19) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=19) of all Dynatrace employees (n=NaN0) were active on GitHub. | 19 19 Dynatrace 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 FY22, page 249)
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved March 2023)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- HashiCorp engineer count: sec.gov (page 13)
- HashiCorp employee count: sec.gov (page 14)
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Vercel engineer count: linkedin.com
- Vercel employee count: linkedin.com
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- 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 11, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 8)
- New Relic engineer count: linkedin.com
- New Relic employee count: sec.gov (page 9)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- GitLab engineer count: linkedin.com
- GitLab employee count: sec.gov (page 13)
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Shopify engineer count: linkedin.com
- Shopify employee count: s27.q4cdn.com (page 23)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 21)
- Microsoft engineer count: sec.gov (page 8, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 8)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 13)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Annual Report, page 168)
- 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 16)
- Twitter engineer count: linkedin.com
- Twitter employee count: linkedin.com
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- WIX engineer count: sec.gov (page 142, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 142)
- Unity Technologies engineer count: sec.gov (page 4, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 4)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 8)
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 87)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Zendesk engineer count: linkedin.com
- Zendesk employee count: sec.gov (page 54)
- 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)
- CyberAgent engineer count: d2utiq8et4vl56.cloudfront.net (page 80)
- CyberAgent employee count: d2utiq8et4vl56.cloudfront.net (page 80)
- Twilio engineer count: sec.gov (page 7, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Lyft engineer count: sec.gov (page 11, referred to as employees in 'product management, engineering, design and science')
- Lyft employee count: sec.gov (page 11)
- NVIDIA engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 12)
- Spotify engineer count: sec.gov (page 69, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 69)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- Atlassian engineer count: sec.gov (page 65, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 43)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 8)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 55)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- SAP SE engineer count: sec.gov (page F-22, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 101)
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 10)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Yandex engineer count: sec.gov (page 48, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 48)
- Autodesk engineer count: linkedin.com
- Autodesk employee count: sec.gov (page 12)
- Baidu engineer count: sec.gov (page 197, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 197)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Cisco Systems engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 11)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 14)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- NetEase engineer count: sec.gov (page 159, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 159)
- Oracle engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 14)
- 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 9, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 11)
- Nokia engineer count: linkedin.com
- Nokia employee count: sec.gov (page 86)
- Samsung engineer count: samsung.com (page 103, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 103)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 17)
- Huawei engineer count: www-file.huawei.com (page 70, referred to as employees in 'R&D')
- Huawei employee count: www-file.huawei.com (page 2)
- IBM employee count: ibm.com (page 15)
- Accenture employee count: sec.gov (page 24)
- Palo Alto Networks employee count: sec.gov (page 11)
- Kitware employee count: linkedin.com
- DigitalOcean employee count: sec.gov (page 13)