Corporate GitHub Activity
Most Active Corporations on GitHub, Q1 2022
Ranking companies with employees who, during Q1 2022, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 58% 58% (n=305) of all SUSE engineers (n=5221) were active on GitHub. | 13% 13% (n=305) of all SUSE employees (n=2,3982) were active on GitHub. | 305 305 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Grafana Labs | 45% 45% (n=155) of all Grafana Labs engineers (n=3433) were active on GitHub. | 26% 26% (n=155) of all Grafana Labs employees (n=6004) were active on GitHub. | 155 155 Grafana Labs employees were active on GitHub. | 
| 3. Mozilla | 44% 44% (n=207) of all Mozilla engineers (n=4725) were active on GitHub. | 14% 14% (n=207) of all Mozilla employees (n=1,5106) were active on GitHub. | 207 207 Mozilla employees were active on GitHub. | 
| 4. Automattic | 39% 39% (n=323) of all Automattic engineers (n=8307) were active on GitHub. | 16% 16% (n=323) of all Automattic employees (n=2,0028) were active on GitHub. | 323 323 Automattic employees were active on GitHub. | 
| 5. Elastic | 35% 35% (n=321) of all Elastic engineers (n=9149) were active on GitHub. | 11% 11% (n=321) of all Elastic employees (n=2,88610) were active on GitHub. | 321 321 Elastic employees were active on GitHub. | 
| 6. The Guardian | 35% 35% (n=44) of all The Guardian engineers (n=12711) were active on GitHub. | 2% 2% (n=44) of all The Guardian employees (n=2,30012) were active on GitHub. | 44 44 The Guardian employees were active on GitHub. | 
| 7. JetBrains | 32% 32% (n=227) of all JetBrains engineers (n=71913) were active on GitHub. | 12% 12% (n=227) of all JetBrains employees (n=1,90014) were active on GitHub. | 227 227 JetBrains employees were active on GitHub. | 
| 8. HashiCorp | 27% 27% (n=184) of all HashiCorp engineers (n=67015) were active on GitHub. | 8% 8% (n=184) of all HashiCorp employees (n=2,40016) were active on GitHub. | 184 184 HashiCorp employees were active on GitHub. | 
| 9. Mapbox | 25% 25% (n=65) of all Mapbox engineers (n=25817) were active on GitHub. | 10% 10% (n=65) of all Mapbox employees (n=67818) were active on GitHub. | 65 65 Mapbox employees were active on GitHub. | 
| 10. WikiMedia Foundation | 22% 22% (n=43) of all WikiMedia Foundation engineers (n=19419) were active on GitHub. | (n=43) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 43 43 WikiMedia Foundation employees were active on GitHub. | 
| 11. WSO2 | 17% 17% (n=130) of all WSO2 engineers (n=77520) were active on GitHub. | 11% 11% (n=130) of all WSO2 employees (n=1,16521) were active on GitHub. | 130 130 WSO2 employees were active on GitHub. | 
| 12. Cloudflare | 15% 15% (n=89) of all Cloudflare engineers (n=61022) were active on GitHub. | 3% 3% (n=89) of all Cloudflare employees (n=3,21723) were active on GitHub. | 89 89 Cloudflare employees were active on GitHub. | 
| 13. MongoDB | 14% 14% (n=148) of all MongoDB engineers (n=1,03024) were active on GitHub. | 3% 3% (n=148) of all MongoDB employees (n=4,61925) were active on GitHub. | 148 148 MongoDB employees were active on GitHub. | 
| 14. New Relic | 13% 13% (n=106) of all New Relic engineers (n=81926) were active on GitHub. | 4% 4% (n=106) of all New Relic employees (n=2,66327) were active on GitHub. | 106 106 New Relic employees were active on GitHub. | 
| 15. Liferay | 13% 13% (n=56) of all Liferay engineers (n=44428) were active on GitHub. | 4% 4% (n=56) of all Liferay employees (n=1,28929) were active on GitHub. | 56 56 Liferay employees were active on GitHub. | 
| 16. Confluent | 11% 11% (n=93) of all Confluent engineers (n=81830) were active on GitHub. | 3% 3% (n=93) of all Confluent employees (n=2,76131) were active on GitHub. | 93 93 Confluent employees were active on GitHub. | 
| 17. DataDog | 11% 11% (n=226) of all DataDog engineers (n=2,00032) were active on GitHub. | 5% 5% (n=226) of all DataDog employees (n=4,80033) were active on GitHub. | 226 226 DataDog employees were active on GitHub. | 
| 18. Odoo | 11% 11% (n=50) of all Odoo engineers (n=47434) were active on GitHub. | 4% 4% (n=50) of all Odoo employees (n=1,32735) were active on GitHub. | 50 50 Odoo employees were active on GitHub. | 
| 19. ESRI | 8% 8% (n=159) of all ESRI engineers (n=1,94736) were active on GitHub. | 3% 3% (n=159) of all ESRI employees (n=5,87337) were active on GitHub. | 159 159 ESRI employees were active on GitHub. | 
| 20. Shopify | 7% 7% (n=294) of all Shopify engineers (n=4,03738) were active on GitHub. | 3% 3% (n=294) of all Shopify employees (n=11,60039) were active on GitHub. | 294 294 Shopify employees were active on GitHub. | 
| 21. Progress Software | 7% 7% (n=59) of all Progress Software engineers (n=84240) were active on GitHub. | 3% 3% (n=59) of all Progress Software employees (n=2,07141) were active on GitHub. | 59 59 Progress Software employees were active on GitHub. | 
| 22. Square, Inc. | 6% 6% (n=116) of all Square, Inc. engineers (n=1,83142) were active on GitHub. | 1% 1% (n=116) of all Square, Inc. employees (n=12,42843) were active on GitHub. | 116 116 Square, Inc. employees were active on GitHub. | 
| 23. Microsoft | 6% 6% (n=4,476) of all Microsoft engineers (n=73,00044) were active on GitHub. | 2% 2% (n=4,476) of all Microsoft employees (n=221,00045) were active on GitHub. | 4,476 4,476 Microsoft employees were active on GitHub. | 
| 24. Okta | 6% 6% (n=82) of all Okta engineers (n=1,39246) were active on GitHub. | 1% 1% (n=82) of all Okta employees (n=6,01347) were active on GitHub. | 82 82 Okta employees were active on GitHub. | 
| 25. Alibaba | 6% 6% (n=533) of all Alibaba engineers (n=9,44048) were active on GitHub. | 0% 0% (n=533) of all Alibaba employees (n=254,94149) were active on GitHub. | 533 533 Alibaba employees were active on GitHub. | 
| 26. Netflix | 5% 5% (n=107) of all Netflix engineers (n=2,22750) were active on GitHub. | 1% 1% (n=107) of all Netflix employees (n=12,80051) were active on GitHub. | 107 107 Netflix employees were active on GitHub. | 
| 27. VMWare | 5% 5% (n=635) of all VMWare engineers (n=13,33252) were active on GitHub. | 2% 2% (n=635) of all VMWare employees (n=38,30053) were active on GitHub. | 635 635 VMWare employees were active on GitHub. | 
| 28. Twitter | 5% 5% (n=65) of all Twitter engineers (n=1,36954) were active on GitHub. | 1% 1% (n=65) of all Twitter employees (n=9,40055) were active on GitHub. | 65 65 Twitter employees were active on GitHub. | 
| 29. ThoughtWorks | 5% 5% (n=196) of all ThoughtWorks engineers (n=4,15256) were active on GitHub. | 2% 2% (n=196) of all ThoughtWorks employees (n=12,50057) were active on GitHub. | 196 196 ThoughtWorks employees were active on GitHub. | 
| 30. Unity Technologies | 5% 5% (n=177) of all Unity Technologies engineers (n=3,75358) were active on GitHub. | 2% 2% (n=177) of all Unity Technologies employees (n=7,70359) were active on GitHub. | 177 177 Unity Technologies employees were active on GitHub. | 
| 31. Amazon | 4% 4% (n=1,454) of all Amazon engineers (n=37,13460) were active on GitHub. | 1% 1% (n=1,454) of all Amazon employees (n=112,31561) were active on GitHub. | 1,454 1,454 Amazon employees were active on GitHub. | 
| 32. Stripe | 4% 4% (n=112) of all Stripe engineers (n=2,96162) were active on GitHub. | 1% 1% (n=112) of all Stripe employees (n=8,37263) were active on GitHub. | 112 112 Stripe employees were active on GitHub. | 
| 33. Tencent | 4% 4% (n=486) of all Tencent engineers (n=12,97964) were active on GitHub. | 0% 0% (n=486) of all Tencent employees (n=108,43665) were active on GitHub. | 486 486 Tencent employees were active on GitHub. | 
| 34. Zendesk | 4% 4% (n=58) of all Zendesk engineers (n=1,62066) were active on GitHub. | 1% 1% (n=58) of all Zendesk employees (n=6,44067) were active on GitHub. | 58 58 Zendesk employees were active on GitHub. | 
| 35. WIX | 4% 4% (n=78) of all WIX engineers (n=2,20668) were active on GitHub. | 2% 2% (n=78) of all WIX employees (n=4,74269) were active on GitHub. | 78 78 WIX employees were active on GitHub. | 
| 36. Splunk | 4% 4% (n=73) of all Splunk engineers (n=2,07670) were active on GitHub. | 1% 1% (n=73) of all Splunk employees (n=8,00071) were active on GitHub. | 73 73 Splunk employees were active on GitHub. | 
| 37. Twilio | 3% 3% (n=116) of all Twilio engineers (n=3,59072) were active on GitHub. | 1% 1% (n=116) of all Twilio employees (n=8,15673) were active on GitHub. | 116 116 Twilio employees were active on GitHub. | 
| 38. BBC | 3% 3% (n=49) of all BBC engineers (n=1,52174) were active on GitHub. | 0% 0% (n=49) of all BBC employees (n=21,28175) were active on GitHub. | 49 49 BBC employees were active on GitHub. | 
| 39. Zalando DE | 3% 3% (n=49) of all Zalando DE engineers (n=1,60876) were active on GitHub. | 0% 0% (n=49) of all Zalando DE employees (n=16,99977) were active on GitHub. | 49 49 Zalando DE employees were active on GitHub. | 
| 40. Adobe | 3% 3% (n=284) of all Adobe engineers (n=9,45078) were active on GitHub. | 1% 1% (n=284) of all Adobe employees (n=29,23979) were active on GitHub. | 284 284 Adobe employees were active on GitHub. | 
| 41. Arm Ltd | 3% 3% (n=139) of all Arm Ltd engineers (n=4,75880) were active on GitHub. | 2% 2% (n=139) of all Arm Ltd employees (n=6,32981) were active on GitHub. | 139 139 Arm Ltd employees were active on GitHub. | 
| 42. Google | 3% 3% (n=1,990) of all Google engineers (n=71,08482) were active on GitHub. | 1% 1% (n=1,990) of all Google employees (n=190,23483) were active on GitHub. | 1,990 1,990 Google employees were active on GitHub. | 
| 43. Lyft | 3% 3% (n=48) of all Lyft engineers (n=1,81184) were active on GitHub. | 1% 1% (n=48) of all Lyft employees (n=4,41985) were active on GitHub. | 48 48 Lyft employees were active on GitHub. | 
| 44. Spotify | 3% 3% (n=107) of all Spotify engineers (n=4,16986) were active on GitHub. | 1% 1% (n=107) of all Spotify employees (n=8,35987) were active on GitHub. | 107 107 Spotify employees were active on GitHub. | 
| 45. Airbnb | 2% 2% (n=42) of all Airbnb engineers (n=1,90088) were active on GitHub. | 1% 1% (n=42) of all Airbnb employees (n=6,81189) were active on GitHub. | 42 42 Airbnb employees were active on GitHub. | 
| 46. Atlassian | 2% 2% (n=94) of all Atlassian engineers (n=4,40690) were active on GitHub. | 1% 1% (n=94) of all Atlassian employees (n=8,81391) were active on GitHub. | 94 94 Atlassian employees were active on GitHub. | 
| 47. Autodesk | 2% 2% (n=65) of all Autodesk engineers (n=3,80092) were active on GitHub. | 0% 0% (n=65) of all Autodesk employees (n=13,70093) were active on GitHub. | 65 65 Autodesk employees were active on GitHub. | 
| 48. NVIDIA | 2% 2% (n=333) of all NVIDIA engineers (n=19,53294) were active on GitHub. | 1% 1% (n=333) of all NVIDIA employees (n=26,19695) were active on GitHub. | 333 333 NVIDIA employees were active on GitHub. | 
| 49. Uber | 2% 2% (n=91) of all Uber engineers (n=5,50296) were active on GitHub. | 0% 0% (n=91) of all Uber employees (n=32,80097) were active on GitHub. | 91 91 Uber employees were active on GitHub. | 
| 50. Salesforce | 2% 2% (n=324) of all Salesforce engineers (n=20,53798) were active on GitHub. | 0% 0% (n=324) of all Salesforce employees (n=79,39099) were active on GitHub. | 324 324 Salesforce employees were active on GitHub. | 
| 51. Indeed | 2% 2% (n=37) of all Indeed engineers (n=2,457100) were active on GitHub. | 0% 0% (n=37) of all Indeed employees (n=16,387101) were active on GitHub. | 37 37 Indeed employees were active on GitHub. | 
| 52. Meta | 1% 1% (n=484) of all Meta engineers (n=35,611102) were active on GitHub. | 1% 1% (n=484) of all Meta employees (n=86,482103) were active on GitHub. | 484 484 Meta employees were active on GitHub. | 
| 53. SAP SE | 1% 1% (n=429) of all SAP SE engineers (n=34,122104) were active on GitHub. | 0% 0% (n=429) of all SAP SE employees (n=111,961105) were active on GitHub. | 429 429 SAP SE employees were active on GitHub. | 
| 54. Yandex | 1% 1% (n=129) of all Yandex engineers (n=10,708106) were active on GitHub. | 1% 1% (n=129) of all Yandex employees (n=20,850107) were active on GitHub. | 129 129 Yandex employees were active on GitHub. | 
| 55. Intel | 1% 1% (n=648) of all Intel engineers (n=57,090108) were active on GitHub. | 0% 0% (n=648) of all Intel employees (n=131,900109) were active on GitHub. | 648 648 Intel employees were active on GitHub. | 
| 56. Cisco Systems | 1% 1% (n=233) of all Cisco Systems engineers (n=23,407110) were active on GitHub. | 0% 0% (n=233) of all Cisco Systems employees (n=83,300111) were active on GitHub. | 233 233 Cisco Systems employees were active on GitHub. | 
| 57. Bloomberg | 1% 1% (n=62) of all Bloomberg engineers (n=6,326112) were active on GitHub. | 0% 0% (n=62) of all Bloomberg employees (n=23,033113) were active on GitHub. | 62 62 Bloomberg employees were active on GitHub. | 
| 58. Baidu | 1% 1% (n=217) of all Baidu engineers (n=23,600114) were active on GitHub. | 1% 1% (n=217) of all Baidu employees (n=41,300115) were active on GitHub. | 217 217 Baidu employees were active on GitHub. | 
| 59. AMD | 1% 1% (n=108) of all AMD engineers (n=12,146116) were active on GitHub. | 0% 0% (n=108) of all AMD employees (n=25,000117) were active on GitHub. | 108 108 AMD employees were active on GitHub. | 
| 60. Oracle | 1% 1% (n=304) of all Oracle engineers (n=44,000118) were active on GitHub. | 0% 0% (n=304) of all Oracle employees (n=143,000119) were active on GitHub. | 304 304 Oracle employees were active on GitHub. | 
| 61. PayPal | 1% 1% (n=58) of all PayPal engineers (n=8,805120) were active on GitHub. | 0% 0% (n=58) of all PayPal employees (n=29,900121) were active on GitHub. | 58 58 PayPal employees were active on GitHub. | 
| 62. NetEase | 1% 1% (n=95) of all NetEase engineers (n=15,211122) were active on GitHub. | 0% 0% (n=95) of all NetEase employees (n=31,119123) were active on GitHub. | 95 95 NetEase employees were active on GitHub. | 
| 63. Apple | 1% 1% (n=200) of all Apple engineers (n=39,361124) were active on GitHub. | 0% 0% (n=200) of all Apple employees (n=164,000125) were active on GitHub. | 200 200 Apple employees were active on GitHub. | 
| 64. EPAM Systems | 0% 0% (n=220) of all EPAM Systems engineers (n=52,850126) were active on GitHub. | 0% 0% (n=220) of all EPAM Systems employees (n=59,300127) were active on GitHub. | 220 220 EPAM Systems employees were active on GitHub. | 
| 65. Ericsson | 0% 0% (n=72) of all Ericsson engineers (n=29,304128) were active on GitHub. | 0% 0% (n=72) of all Ericsson employees (n=105,529129) were active on GitHub. | 72 72 Ericsson employees were active on GitHub. | 
| 66. Nokia | 0% 0% (n=57) of all Nokia engineers (n=23,836130) were active on GitHub. | 0% 0% (n=57) of all Nokia employees (n=86,896131) were active on GitHub. | 57 57 Nokia employees were active on GitHub. | 
| 67. Samsung | 0% 0% (n=155) of all Samsung engineers (n=80,496132) were active on GitHub. | 0% 0% (n=155) of all Samsung employees (n=270,372133) were active on GitHub. | 155 155 Samsung employees were active on GitHub. | 
| 68. Capgemini | 0% 0% (n=100) of all Capgemini engineers (n=69,803134) were active on GitHub. | 0% 0% (n=100) of all Capgemini employees (n=360,000135) were active on GitHub. | 100 100 Capgemini employees were active on GitHub. | 
| 69. Huawei | 0% 0% (n=145) of all Huawei engineers (n=114,000136) were active on GitHub. | 0% 0% (n=145) of all Huawei employees (n=207,000137) were active on GitHub. | 145 145 Huawei employees were active on GitHub. | 
| 70. IBM | (n=2,799) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=2,799) of all IBM employees (n=288,300138) were active on GitHub. | 2,799 2,799 IBM employees were active on GitHub. | 
| 71. ByteDance | (n=166) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=166) of all ByteDance employees (n=NaN0) were active on GitHub. | 166 166 ByteDance employees were active on GitHub. | 
| 72. Accenture | (n=158) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=158) of all Accenture employees (n=721,000139) were active on GitHub. | 158 158 Accenture employees were active on GitHub. | 
| 73. Canonical | (n=114) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=114) of all Canonical employees (n=NaN0) were active on GitHub. | 114 114 Canonical employees were active on GitHub. | 
| 74. Yahoo! | (n=84) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=84) of all Yahoo! employees (n=NaN0) were active on GitHub. | 84 84 Yahoo! employees were active on GitHub. | 
| 75. PingCAP | (n=83) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=83) of all PingCAP employees (n=NaN0) were active on GitHub. | 83 83 PingCAP employees were active on GitHub. | 
| 76. Snyk | (n=80) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=80) of all Snyk employees (n=NaN0) were active on GitHub. | 80 80 Snyk employees were active on GitHub. | 
| 77. Databricks | (n=76) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=76) of all Databricks employees (n=NaN0) were active on GitHub. | 76 76 Databricks employees were active on GitHub. | 
| 78. Sentry.io | (n=54) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=54) of all Sentry.io employees (n=NaN0) were active on GitHub. | 54 54 Sentry.io employees were active on GitHub. | 
| 79. Trybe | (n=52) of all Trybe engineers (n=NaN0) were active on GitHub. | (n=52) of all Trybe employees (n=NaN0) were active on GitHub. | 52 52 Trybe employees were active on GitHub. | 
| 80. CircleCI | (n=51) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=51) of all CircleCI employees (n=NaN0) were active on GitHub. | 51 51 CircleCI employees were active on GitHub. | 
| 81. 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. | 
| 82. Software Mansion | (n=49) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=49) of all Software Mansion employees (n=NaN0) were active on GitHub. | 49 49 Software Mansion employees were active on GitHub. | 
| 83. Intuit | (n=49) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=49) of all Intuit employees (n=17,300140) were active on GitHub. | 49 49 Intuit employees were active on GitHub. | 
| 84. Epitech | (n=48) of all Epitech engineers (n=NaN0) were active on GitHub. | (n=48) of all Epitech employees (n=NaN0) were active on GitHub. | 48 48 Epitech employees were active on GitHub. | 
| 85. Orange S.A. | (n=47) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=47) of all Orange S.A. employees (n=130,307141) were active on GitHub. | 47 47 Orange S.A. employees were active on GitHub. | 
| 86. Kitware | (n=47) of all Kitware engineers (n=NaN0) were active on GitHub. | 27% 27% (n=47) of all Kitware employees (n=174142) were active on GitHub. | 47 47 Kitware employees were active on GitHub. | 
| 87. Puppet Labs | (n=45) of all Puppet Labs engineers (n=NaN0) were active on GitHub. | (n=45) of all Puppet Labs employees (n=NaN0) were active on GitHub. | 45 45 Puppet Labs employees were active on GitHub. | 
| 88. UCL | (n=44) of all UCL engineers (n=NaN0) were active on GitHub. | (n=44) of all UCL employees (n=NaN0) were active on GitHub. | 44 44 UCL employees were active on GitHub. | 
| 89. Cloudera | (n=44) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=44) of all Cloudera employees (n=NaN0) were active on GitHub. | 44 44 Cloudera employees were active on GitHub. | 
| 90. @bytedance | (n=44) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=44) of all @bytedance employees (n=NaN0) were active on GitHub. | 44 44 @bytedance employees were active on GitHub. | 
| 91. Tata Consultancy Services | (n=41) of all Tata Consultancy Services engineers (n=NaN0) were active on GitHub. | (n=41) of all Tata Consultancy Services employees (n=NaN0) were active on GitHub. | 41 41 Tata Consultancy Services employees were active on GitHub. | 
| 92. Palo Alto Networks | (n=41) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=41) of all Palo Alto Networks employees (n=12,561143) were active on GitHub. | 41 41 Palo Alto Networks employees were active on GitHub. | 
| 93. TCS | (n=40) of all TCS engineers (n=NaN0) were active on GitHub. | (n=40) of all TCS employees (n=NaN0) were active on GitHub. | 40 40 TCS employees were active on GitHub. | 
| 94. CI&T | (n=40) of all CI&T engineers (n=NaN0) were active on GitHub. | (n=40) of all CI&T employees (n=NaN0) were active on GitHub. | 40 40 CI&T employees were active on GitHub. | 
| 95. 42 | (n=39) of all 42 engineers (n=NaN0) were active on GitHub. | (n=39) of all 42 employees (n=NaN0) were active on GitHub. | 39 39 42 employees were active on GitHub. | 
| 96. Broad Institute | (n=38) of all Broad Institute engineers (n=NaN0) were active on GitHub. | (n=38) of all Broad Institute employees (n=NaN0) were active on GitHub. | 38 38 Broad Institute employees were active on GitHub. | 
| 97. DigitalOcean | (n=38) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 3% 3% (n=38) of all DigitalOcean employees (n=1,204144) were active on GitHub. | 38 38 DigitalOcean employees were active on GitHub. | 
| 98. RStudio | (n=37) of all RStudio engineers (n=NaN0) were active on GitHub. | (n=37) of all RStudio employees (n=NaN0) were active on GitHub. | 37 37 RStudio employees were active on GitHub. | 
| 99. Dynatrace | (n=37) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=37) of all Dynatrace employees (n=NaN0) were active on GitHub. | 37 37 Dynatrace employees were active on GitHub. | 
| 100. MIPT | (n=36) of all MIPT engineers (n=NaN0) were active on GitHub. | (n=36) of all MIPT employees (n=NaN0) were active on GitHub. | 36 36 MIPT employees were active on GitHub. | 
References
- SUSE engineer count: linkedin.com
- SUSE employee count: ir.suse.com (Annual Report FY22, page 249)
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved March 2023)
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- HashiCorp engineer count: sec.gov (page 13)
- HashiCorp employee count: sec.gov (page 14)
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- 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)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- DataDog engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 11)
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Shopify engineer count: linkedin.com
- Shopify employee count: s27.q4cdn.com (page 23)
- Progress Software engineer count: sec.gov (page 8, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 8)
- 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)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 16)
- Twitter engineer count: linkedin.com
- Twitter employee count: linkedin.com
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Unity Technologies engineer count: sec.gov (page 4, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 4)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 87)
- Zendesk engineer count: linkedin.com
- Zendesk employee count: sec.gov (page 54)
- WIX engineer count: sec.gov (page 142, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 142)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Twilio engineer count: sec.gov (page 7, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- BBC engineer count: linkedin.com
- BBC employee count: downloads.bbc.co.uk (page 62)
- 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)
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 8)
- 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)
- Spotify engineer count: sec.gov (page 69, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 69)
- Airbnb engineer count: sec.gov (page 4)
- Airbnb employee count: sec.gov (page 4)
- 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)
- Autodesk engineer count: linkedin.com
- Autodesk employee count: sec.gov (page 12)
- NVIDIA engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 12)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 8)
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 10)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 55)
- 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)
- Yandex engineer count: sec.gov (page 48, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 48)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- Cisco Systems engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 11)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Baidu engineer count: sec.gov (page 197, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 197)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Oracle engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 14)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 14)
- NetEase engineer count: sec.gov (page 159, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 159)
- 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 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)
- Intuit employee count: sec.gov (page 12)
- Orange S.A. employee count: gallery.orange.com (page 57)
- Kitware employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- DigitalOcean employee count: sec.gov (page 13)