Corporate GitHub Activity
Most Active Corporations on GitHub, 07 2023
Ranking companies with employees who, during 07 2023, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 38% 38% (n=217) of all SUSE engineers (n=5751) were active on GitHub. | 9% 9% (n=217) of all SUSE employees (n=2,4002) were active on GitHub. | 217 217 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Vercel | 36% 36% (n=56) of all Vercel engineers (n=1543) were active on GitHub. | 12% 12% (n=56) of all Vercel employees (n=4734) were active on GitHub. | 56 56 Vercel employees were active on GitHub. | 
| 3. Grafana Labs | 36% 36% (n=187) of all Grafana Labs engineers (n=5165) were active on GitHub. | 15% 15% (n=187) of all Grafana Labs employees (n=1,2176) were active on GitHub. | 187 187 Grafana Labs employees were active on GitHub. | 
| 4. Automattic | 35% 35% (n=302) of all Automattic engineers (n=8667) were active on GitHub. | 16% 16% (n=302) of all Automattic employees (n=1,9308) were active on GitHub. | 302 302 Automattic employees were active on GitHub. | 
| 5. HashiCorp | 26% 26% (n=179) of all HashiCorp engineers (n=6809) were active on GitHub. | 8% 8% (n=179) of all HashiCorp employees (n=2,20010) were active on GitHub. | 179 179 HashiCorp employees were active on GitHub. | 
| 6. Elastic | 26% 26% (n=262) of all Elastic engineers (n=1,02211) were active on GitHub. | 8% 8% (n=262) of all Elastic employees (n=3,18712) were active on GitHub. | 262 262 Elastic employees were active on GitHub. | 
| 7. Mozilla | 25% 25% (n=149) of all Mozilla engineers (n=58513) were active on GitHub. | 9% 9% (n=149) of all Mozilla employees (n=1,74514) were active on GitHub. | 149 149 Mozilla employees were active on GitHub. | 
| 8. Odoo | 18% 18% (n=119) of all Odoo engineers (n=64515) were active on GitHub. | 7% 7% (n=119) of all Odoo employees (n=1,70016) were active on GitHub. | 119 119 Odoo 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. The Guardian | 17% 17% (n=25) of all The Guardian engineers (n=14419) were active on GitHub. | 1% 1% (n=25) of all The Guardian employees (n=2,50120) were active on GitHub. | 25 25 The Guardian employees were active on GitHub. | 
| 11. JetBrains | 16% 16% (n=157) of all JetBrains engineers (n=97221) were active on GitHub. | 9% 9% (n=157) of all JetBrains employees (n=1,80022) were active on GitHub. | 157 157 JetBrains employees were active on GitHub. | 
| 12. WikiMedia Foundation | 10% 10% (n=20) of all WikiMedia Foundation engineers (n=20423) were active on GitHub. | 3% 3% (n=20) of all WikiMedia Foundation employees (n=70024) were active on GitHub. | 20 20 WikiMedia Foundation employees were active on GitHub. | 
| 13. DataDog | 10% 10% (n=231) of all DataDog engineers (n=2,40025) were active on GitHub. | 4% 4% (n=231) of all DataDog employees (n=5,20026) were active on GitHub. | 231 231 DataDog employees were active on GitHub. | 
| 14. WSO2 | 9% 9% (n=61) of all WSO2 engineers (n=66427) were active on GitHub. | 6% 6% (n=61) of all WSO2 employees (n=1,02028) were active on GitHub. | 61 61 WSO2 employees were active on GitHub. | 
| 15. MongoDB | 9% 9% (n=107) of all MongoDB engineers (n=1,22629) were active on GitHub. | 2% 2% (n=107) of all MongoDB employees (n=5,03730) were active on GitHub. | 107 107 MongoDB employees were active on GitHub. | 
| 16. Cloudflare | 9% 9% (n=72) of all Cloudflare engineers (n=83031) were active on GitHub. | 2% 2% (n=72) of all Cloudflare employees (n=3,68232) were active on GitHub. | 72 72 Cloudflare employees were active on GitHub. | 
| 17. Shopify | 5% 5% (n=176) of all Shopify engineers (n=3,56433) were active on GitHub. | 2% 2% (n=176) of all Shopify employees (n=8,30034) were active on GitHub. | 176 176 Shopify employees were active on GitHub. | 
| 18. Confluent | 4% 4% (n=46) of all Confluent engineers (n=1,03435) were active on GitHub. | 2% 2% (n=46) of all Confluent employees (n=2,74436) were active on GitHub. | 46 46 Confluent employees were active on GitHub. | 
| 19. New Relic | 4% 4% (n=38) of all New Relic engineers (n=88437) were active on GitHub. | 1% 1% (n=38) of all New Relic employees (n=2,58438) were active on GitHub. | 38 38 New Relic employees were active on GitHub. | 
| 20. ESRI | 4% 4% (n=85) of all ESRI engineers (n=2,07439) were active on GitHub. | 1% 1% (n=85) of all ESRI employees (n=6,44740) were active on GitHub. | 85 85 ESRI employees were active on GitHub. | 
| 21. Twitter | 4% 4% (n=21) of all Twitter engineers (n=54941) were active on GitHub. | 1% 1% (n=21) of all Twitter employees (n=2,14042) were active on GitHub. | 21 21 Twitter employees were active on GitHub. | 
| 22. Microsoft | 4% 4% (n=2,570) of all Microsoft engineers (n=72,00043) were active on GitHub. | 1% 1% (n=2,570) of all Microsoft employees (n=221,00044) were active on GitHub. | 2,570 2,570 Microsoft employees were active on GitHub. | 
| 23. GitLab | 3% 3% (n=21) of all GitLab engineers (n=64145) were active on GitHub. | 1% 1% (n=21) of all GitLab employees (n=2,13046) were active on GitHub. | 21 21 GitLab employees were active on GitHub. | 
| 24. Progress Software | 3% 3% (n=29) of all Progress Software engineers (n=88647) were active on GitHub. | 1% 1% (n=29) of all Progress Software employees (n=2,28448) were active on GitHub. | 29 29 Progress Software employees were active on GitHub. | 
| 25. Okta | 3% 3% (n=46) of all Okta engineers (n=1,57049) were active on GitHub. | 1% 1% (n=46) of all Okta employees (n=5,90850) were active on GitHub. | 46 46 Okta employees were active on GitHub. | 
| 26. Alibaba | 3% 3% (n=278) of all Alibaba engineers (n=10,02551) were active on GitHub. | 0% 0% (n=278) of all Alibaba employees (n=224,95552) were active on GitHub. | 278 278 Alibaba employees were active on GitHub. | 
| 27. Square, Inc. | 3% 3% (n=57) of all Square, Inc. engineers (n=2,06053) were active on GitHub. | 0% 0% (n=57) of all Square, Inc. employees (n=12,98554) were active on GitHub. | 57 57 Square, Inc. employees were active on GitHub. | 
| 28. VMWare | 2% 2% (n=314) of all VMWare engineers (n=12,94455) were active on GitHub. | 1% 1% (n=314) of all VMWare employees (n=38,30056) were active on GitHub. | 314 314 VMWare employees were active on GitHub. | 
| 29. Snowflake, Inc. | 2% 2% (n=46) of all Snowflake, Inc. engineers (n=2,00257) were active on GitHub. | 1% 1% (n=46) of all Snowflake, Inc. employees (n=7,00458) were active on GitHub. | 46 46 Snowflake, Inc. employees were active on GitHub. | 
| 30. ThoughtWorks | 2% 2% (n=83) of all ThoughtWorks engineers (n=3,76559) were active on GitHub. | 1% 1% (n=83) of all ThoughtWorks employees (n=10,50060) were active on GitHub. | 83 83 ThoughtWorks employees were active on GitHub. | 
| 31. Netflix | 2% 2% (n=53) of all Netflix engineers (n=2,40961) were active on GitHub. | 0% 0% (n=53) of all Netflix employees (n=13,00062) were active on GitHub. | 53 53 Netflix employees were active on GitHub. | 
| 32. Amazon | 2% 2% (n=914) of all Amazon engineers (n=43,60563) were active on GitHub. | 1% 1% (n=914) of all Amazon employees (n=125,34564) were active on GitHub. | 914 914 Amazon employees were active on GitHub. | 
| 33. Arm Ltd | 2% 2% (n=90) of all Arm Ltd engineers (n=4,75365) were active on GitHub. | 2% 2% (n=90) of all Arm Ltd employees (n=5,96366) were active on GitHub. | 90 90 Arm Ltd employees were active on GitHub. | 
| 34. Unity Technologies | 2% 2% (n=72) of all Unity Technologies engineers (n=3,84467) were active on GitHub. | 1% 1% (n=72) of all Unity Technologies employees (n=6,74868) were active on GitHub. | 72 72 Unity Technologies employees were active on GitHub. | 
| 35. Splunk | 2% 2% (n=44) of all Splunk engineers (n=2,38769) were active on GitHub. | 1% 1% (n=44) of all Splunk employees (n=8,00070) were active on GitHub. | 44 44 Splunk employees were active on GitHub. | 
| 36. Twilio | 2% 2% (n=47) of all Twilio engineers (n=2,56371) were active on GitHub. | 1% 1% (n=47) of all Twilio employees (n=5,86772) were active on GitHub. | 47 47 Twilio employees were active on GitHub. | 
| 37. Adobe | 2% 2% (n=176) of all Adobe engineers (n=10,24773) were active on GitHub. | 1% 1% (n=176) of all Adobe employees (n=29,94574) were active on GitHub. | 176 176 Adobe employees were active on GitHub. | 
| 38. Zendesk | 2% 2% (n=25) of all Zendesk engineers (n=1,48175) were active on GitHub. | 0% 0% (n=25) of all Zendesk employees (n=6,17976) were active on GitHub. | 25 25 Zendesk employees were active on GitHub. | 
| 39. Google | 2% 2% (n=1,196) of all Google engineers (n=75,57177) were active on GitHub. | 1% 1% (n=1,196) of all Google employees (n=182,50278) were active on GitHub. | 1,196 1,196 Google employees were active on GitHub. | 
| 40. CyberAgent | 2% 2% (n=25) of all CyberAgent engineers (n=1,66079) were active on GitHub. | 0% 0% (n=25) of all CyberAgent employees (n=7,25180) were active on GitHub. | 25 25 CyberAgent employees were active on GitHub. | 
| 41. Tencent | 1% 1% (n=203) of all Tencent engineers (n=13,64281) were active on GitHub. | 0% 0% (n=203) of all Tencent employees (n=105,41782) were active on GitHub. | 203 203 Tencent employees were active on GitHub. | 
| 42. Zalando DE | 1% 1% (n=24) of all Zalando DE engineers (n=1,72283) were active on GitHub. | 0% 0% (n=24) of all Zalando DE employees (n=15,79384) were active on GitHub. | 24 24 Zalando DE employees were active on GitHub. | 
| 43. WIX | 1% 1% (n=31) of all WIX engineers (n=2,30185) were active on GitHub. | 1% 1% (n=31) of all WIX employees (n=4,60086) were active on GitHub. | 31 31 WIX employees were active on GitHub. | 
| 44. Stripe | 1% 1% (n=39) of all Stripe engineers (n=2,95287) were active on GitHub. | 0% 0% (n=39) of all Stripe employees (n=8,40988) were active on GitHub. | 39 39 Stripe employees were active on GitHub. | 
| 45. NVIDIA | 1% 1% (n=279) of all NVIDIA engineers (n=22,20089) were active on GitHub. | 1% 1% (n=279) of all NVIDIA employees (n=29,60090) were active on GitHub. | 279 279 NVIDIA employees were active on GitHub. | 
| 46. Spotify | 1% 1% (n=45) of all Spotify engineers (n=4,71991) were active on GitHub. | 0% 0% (n=45) of all Spotify employees (n=9,12392) were active on GitHub. | 45 45 Spotify employees were active on GitHub. | 
| 47. Atlassian | 1% 1% (n=49) of all Atlassian engineers (n=5,36393) were active on GitHub. | 0% 0% (n=49) of all Atlassian employees (n=10,72694) were active on GitHub. | 49 49 Atlassian employees were active on GitHub. | 
| 48. Indeed | 1% 1% (n=24) of all Indeed engineers (n=2,81395) were active on GitHub. | 0% 0% (n=24) of all Indeed employees (n=18,03896) were active on GitHub. | 24 24 Indeed employees were active on GitHub. | 
| 49. AMD | 1% 1% (n=128) of all AMD engineers (n=15,60697) were active on GitHub. | 0% 0% (n=128) of all AMD employees (n=26,00098) were active on GitHub. | 128 128 AMD employees were active on GitHub. | 
| 50. Uber | 1% 1% (n=52) of all Uber engineers (n=6,42699) were active on GitHub. | 0% 0% (n=52) of all Uber employees (n=30,400100) were active on GitHub. | 52 52 Uber employees were active on GitHub. | 
| 51. Autodesk | 1% 1% (n=33) of all Autodesk engineers (n=4,209101) were active on GitHub. | 0% 0% (n=33) of all Autodesk employees (n=14,100102) were active on GitHub. | 33 33 Autodesk employees were active on GitHub. | 
| 52. Meta | 1% 1% (n=233) of all Meta engineers (n=31,338103) were active on GitHub. | 0% 0% (n=233) of all Meta employees (n=67,317104) were active on GitHub. | 233 233 Meta employees were active on GitHub. | 
| 53. Intel | 1% 1% (n=415) of all Intel engineers (n=57,201105) were active on GitHub. | 0% 0% (n=415) of all Intel employees (n=124,800106) were active on GitHub. | 415 415 Intel employees were active on GitHub. | 
| 54. SAP SE | 1% 1% (n=240) of all SAP SE engineers (n=33,377107) were active on GitHub. | 0% 0% (n=240) of all SAP SE employees (n=107,602108) were active on GitHub. | 240 240 SAP SE employees were active on GitHub. | 
| 55. Salesforce | 1% 1% (n=137) of all Salesforce engineers (n=19,483109) were active on GitHub. | 0% 0% (n=137) of all Salesforce employees (n=72,682110) were active on GitHub. | 137 137 Salesforce employees were active on GitHub. | 
| 56. Bloomberg | 0% 0% (n=34) of all Bloomberg engineers (n=7,328111) were active on GitHub. | 0% 0% (n=34) of all Bloomberg employees (n=25,923112) were active on GitHub. | 34 34 Bloomberg employees were active on GitHub. | 
| 57. Yandex | 0% 0% (n=59) of all Yandex engineers (n=13,003113) were active on GitHub. | 0% 0% (n=59) of all Yandex employees (n=26,361114) were active on GitHub. | 59 59 Yandex employees were active on GitHub. | 
| 58. Baidu | 0% 0% (n=90) of all Baidu engineers (n=21,800115) were active on GitHub. | 0% 0% (n=90) of all Baidu employees (n=39,800116) were active on GitHub. | 90 90 Baidu employees were active on GitHub. | 
| 59. Cisco Systems | 0% 0% (n=89) of all Cisco Systems engineers (n=23,772117) were active on GitHub. | 0% 0% (n=89) of all Cisco Systems employees (n=84,900118) were active on GitHub. | 89 89 Cisco Systems employees were active on GitHub. | 
| 60. Oracle | 0% 0% (n=174) of all Oracle engineers (n=47,000119) were active on GitHub. | 0% 0% (n=174) of all Oracle employees (n=164,000120) were active on GitHub. | 174 174 Oracle employees were active on GitHub. | 
| 61. PayPal | 0% 0% (n=28) of all PayPal engineers (n=8,658121) were active on GitHub. | 0% 0% (n=28) of all PayPal employees (n=27,200122) were active on GitHub. | 28 28 PayPal employees were active on GitHub. | 
| 62. NetEase | 0% 0% (n=46) of all NetEase engineers (n=14,855123) were active on GitHub. | 0% 0% (n=46) of all NetEase employees (n=29,128124) were active on GitHub. | 46 46 NetEase employees were active on GitHub. | 
| 63. Apple | 0% 0% (n=140) of all Apple engineers (n=46,752125) were active on GitHub. | 0% 0% (n=140) of all Apple employees (n=161,000126) were active on GitHub. | 140 140 Apple employees were active on GitHub. | 
| 64. EPAM Systems | 0% 0% (n=91) of all EPAM Systems engineers (n=47,350127) were active on GitHub. | 0% 0% (n=91) of all EPAM Systems employees (n=53,150128) were active on GitHub. | 91 91 EPAM Systems employees were active on GitHub. | 
| 65. Nokia | 0% 0% (n=34) of all Nokia engineers (n=26,395129) were active on GitHub. | 0% 0% (n=34) of all Nokia employees (n=86,689130) were active on GitHub. | 34 34 Nokia employees were active on GitHub. | 
| 66. Ericsson | 0% 0% (n=32) of all Ericsson engineers (n=28,219131) were active on GitHub. | 0% 0% (n=32) of all Ericsson employees (n=99,952132) were active on GitHub. | 32 32 Ericsson employees were active on GitHub. | 
| 67. Samsung | 0% 0% (n=72) of all Samsung engineers (n=83,729133) were active on GitHub. | 0% 0% (n=72) of all Samsung employees (n=267,860134) were active on GitHub. | 72 72 Samsung employees were active on GitHub. | 
| 68. Capgemini | 0% 0% (n=51) of all Capgemini engineers (n=69,796135) were active on GitHub. | 0% 0% (n=51) of all Capgemini employees (n=340,400136) were active on GitHub. | 51 51 Capgemini employees were active on GitHub. | 
| 69. Huawei | 0% 0% (n=58) of all Huawei engineers (n=114,000137) were active on GitHub. | 0% 0% (n=58) of all Huawei employees (n=207,000138) were active on GitHub. | 58 58 Huawei employees were active on GitHub. | 
| 70. IBM | (n=1,594) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,594) of all IBM employees (n=282,200139) were active on GitHub. | 1,594 1,594 IBM employees were active on GitHub. | 
| 71. ByteDance | (n=191) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=191) of all ByteDance employees (n=NaN0) were active on GitHub. | 191 191 ByteDance employees were active on GitHub. | 
| 72. Canonical | (n=101) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=101) of all Canonical employees (n=NaN0) were active on GitHub. | 101 101 Canonical employees were active on GitHub. | 
| 73. Accenture | (n=62) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=62) of all Accenture employees (n=733,000140) were active on GitHub. | 62 62 Accenture employees were active on GitHub. | 
| 74. Databricks | (n=61) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=61) of all Databricks employees (n=7,211141) were active on GitHub. | 61 61 Databricks employees were active on GitHub. | 
| 75. Sentry.io | (n=59) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 16% 16% (n=59) of all Sentry.io employees (n=378142) were active on GitHub. | 59 59 Sentry.io employees were active on GitHub. | 
| 76. Software Mansion | (n=52) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=52) of all Software Mansion employees (n=NaN0) were active on GitHub. | 52 52 Software Mansion employees were active on GitHub. | 
| 77. Yahoo! | (n=48) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=48) of all Yahoo! employees (n=NaN0) were active on GitHub. | 48 48 Yahoo! employees were active on GitHub. | 
| 78. Posit | (n=36) of all Posit engineers (n=NaN0) were active on GitHub. | (n=36) of all Posit employees (n=NaN0) were active on GitHub. | 36 36 Posit employees were active on GitHub. | 
| 79. PingCAP | (n=32) of all PingCAP engineers (n=NaN0) were active on GitHub. | 8% 8% (n=32) of all PingCAP employees (n=410143) were active on GitHub. | 32 32 PingCAP employees were active on GitHub. | 
| 80. @SSWConsulting | (n=32) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=32) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 32 32 @SSWConsulting employees were active on GitHub. | 
| 81. 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. | 
| 82. Palo Alto Networks | (n=30) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=30) of all Palo Alto Networks employees (n=13,948144) were active on GitHub. | 30 30 Palo Alto Networks employees were active on GitHub. | 
| 83. R3 | (n=29) of all R3 engineers (n=NaN0) were active on GitHub. | (n=29) of all R3 employees (n=NaN0) were active on GitHub. | 29 29 R3 employees were active on GitHub. | 
| 84. Ascensio System SIA | (n=27) of all Ascensio System SIA engineers (n=NaN0) were active on GitHub. | (n=27) of all Ascensio System SIA employees (n=NaN0) were active on GitHub. | 27 27 Ascensio System SIA employees were active on GitHub. | 
| 85. Qlik | (n=24) of all Qlik engineers (n=NaN0) were active on GitHub. | (n=24) of all Qlik employees (n=NaN0) were active on GitHub. | 24 24 Qlik employees were active on GitHub. | 
| 86. Snyk | (n=24) of all Snyk engineers (n=NaN0) were active on GitHub. | 2% 2% (n=24) of all Snyk employees (n=1,171145) were active on GitHub. | 24 24 Snyk employees were active on GitHub. | 
| 87. Kitware | (n=24) of all Kitware engineers (n=NaN0) were active on GitHub. | 14% 14% (n=24) of all Kitware employees (n=171146) were active on GitHub. | 24 24 Kitware employees were active on GitHub. | 
| 88. Front-End Developer | (n=23) of all Front-End Developer engineers (n=NaN0) were active on GitHub. | (n=23) of all Front-End Developer employees (n=NaN0) were active on GitHub. | 23 23 Front-End Developer employees were active on GitHub. | 
| 89. Orange S.A. | (n=23) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=23) of all Orange S.A. employees (n=127,109147) were active on GitHub. | 23 23 Orange S.A. employees were active on GitHub. | 
| 90. @Kong | (n=23) of all @Kong engineers (n=NaN0) were active on GitHub. | (n=23) of all @Kong employees (n=NaN0) were active on GitHub. | 23 23 @Kong employees were active on GitHub. | 
| 91. Cloudera | (n=22) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=22) of all Cloudera employees (n=NaN0) were active on GitHub. | 22 22 Cloudera employees were active on GitHub. | 
| 92. Software Developer | (n=22) of all Software Developer engineers (n=NaN0) were active on GitHub. | (n=22) of all Software Developer employees (n=NaN0) were active on GitHub. | 22 22 Software Developer employees were active on GitHub. | 
| 93. Ant Group | (n=21) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=21) of all Ant Group employees (n=NaN0) were active on GitHub. | 21 21 Ant Group employees were active on GitHub. | 
| 94. Intuit | (n=21) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=21) of all Intuit employees (n=18,200148) were active on GitHub. | 21 21 Intuit employees were active on GitHub. | 
| 95. @apache | (n=21) of all @apache engineers (n=NaN0) were active on GitHub. | (n=21) of all @apache employees (n=NaN0) were active on GitHub. | 21 21 @apache employees were active on GitHub. | 
| 96. TU Delft | (n=20) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=20) of all TU Delft employees (n=NaN0) were active on GitHub. | 20 20 TU Delft employees were active on GitHub. | 
| 97. Broad Institute | (n=20) of all Broad Institute engineers (n=NaN0) were active on GitHub. | (n=20) of all Broad Institute employees (n=NaN0) were active on GitHub. | 20 20 Broad Institute employees were active on GitHub. | 
| 98. Dynatrace | (n=20) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=20) of all Dynatrace employees (n=NaN0) were active on GitHub. | 20 20 Dynatrace employees were active on GitHub. | 
| 99. @input-output-hk | (n=20) of all @input-output-hk engineers (n=NaN0) were active on GitHub. | (n=20) of all @input-output-hk employees (n=NaN0) were active on GitHub. | 20 20 @input-output-hk employees were active on GitHub. | 
| 100. @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. | 
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)
- Elastic engineer count: linkedin.com (retrieved Dec 2023)
- Elastic employee count: sec.gov (page 15)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- 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
- WikiMedia Foundation engineer count: linkedin.com
- WikiMedia Foundation employee count: wikimediafoundation.org
- DataDog engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 11)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- 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)
- Shopify engineer count: linkedin.com (retrieved Dec 2023)
- Shopify employee count: s27.q4cdn.com (page 22)
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- New Relic engineer count: linkedin.com (Retrieved December 2023)
- New Relic employee count: linkedin.com (Retrieved December 2023)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Twitter engineer count: linkedin.com
- Twitter 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)
- GitLab engineer count: linkedin.com (retrieved December 2023)
- GitLab employee count: sec.gov (page 12)
- Progress Software engineer count: sec.gov (page 7, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 7)
- 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)
- 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)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- 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)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Twilio engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 18)
- Zendesk engineer count: linkedin.com (retrieved Dec 2023)
- Zendesk employee count: linkedin.com (retrieved Dec 2023)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 10)
- 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)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- WIX engineer count: sec.gov (page 89, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 149)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA 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)
- 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)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 12)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 7)
- Autodesk engineer count: linkedin.com (retrieved Dec 2023)
- Autodesk employee count: sec.gov (page 13)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 60)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- 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)
- Salesforce engineer count: linkedin.com (retrieved Dec 2023)
- Salesforce employee count: sec.gov (page 10)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Yandex engineer count: sec.gov (page 54, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 54)
- 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)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- 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)
- Nokia engineer count: linkedin.com (retrieved Dec 2023)
- Nokia employee count: sec.gov (page 105)
- Ericsson engineer count: sec.gov (page 6, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- 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)
- Databricks employee count: linkedin.com
- Sentry.io employee count: linkedin.com
- PingCAP employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- Snyk employee count: linkedin.com
- Kitware employee count: linkedin.com
- Orange S.A. employee count: gallery.orange.com (page 58)
- Intuit employee count: sec.gov (page 12)