Corporate GitHub Activity
Most Active Corporations on GitHub, 04 2021
Ranking companies with employees who, during 04 2021, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 39% 39% (n=187) of all SUSE engineers (n=4751) were active on GitHub. | 9% 9% (n=187) of all SUSE employees (n=2,0452) were active on GitHub. | 187 187 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Automattic | 31% 31% (n=207) of all Automattic engineers (n=6653) were active on GitHub. | 12% 12% (n=207) of all Automattic employees (n=1,7004) were active on GitHub. | 207 207 Automattic employees were active on GitHub. | 
| 3. Grafana Labs | 30% 30% (n=73) of all Grafana Labs engineers (n=2405) were active on GitHub. | 18% 18% (n=73) of all Grafana Labs employees (n=4006) were active on GitHub. | 73 73 Grafana Labs employees were active on GitHub. | 
| 4. Mozilla | 29% 29% (n=156) of all Mozilla engineers (n=5477) were active on GitHub. | 11% 11% (n=156) of all Mozilla employees (n=1,3858) were active on GitHub. | 156 156 Mozilla employees were active on GitHub. | 
| 5. JetBrains | 27% 27% (n=157) of all JetBrains engineers (n=5759) were active on GitHub. | 8% 8% (n=157) of all JetBrains employees (n=1,90010) were active on GitHub. | 157 157 JetBrains employees were active on GitHub. | 
| 6. The Guardian | 26% 26% (n=29) of all The Guardian engineers (n=11211) were active on GitHub. | 1% 1% (n=29) of all The Guardian employees (n=2,13012) were active on GitHub. | 29 29 The Guardian employees were active on GitHub. | 
| 7. HashiCorp | 24% 24% (n=121) of all HashiCorp engineers (n=50013) were active on GitHub. | 7% 7% (n=121) of all HashiCorp employees (n=1,85014) were active on GitHub. | 121 121 HashiCorp employees were active on GitHub. | 
| 8. Elastic | 24% 24% (n=217) of all Elastic engineers (n=90515) were active on GitHub. | 7% 7% (n=217) of all Elastic employees (n=2,97816) were active on GitHub. | 217 217 Elastic employees were active on GitHub. | 
| 9. Mapbox | 21% 21% (n=52) of all Mapbox engineers (n=25017) were active on GitHub. | 9% 9% (n=52) of all Mapbox employees (n=60118) were active on GitHub. | 52 52 Mapbox employees were active on GitHub. | 
| 10. Odoo | 20% 20% (n=77) of all Odoo engineers (n=37919) were active on GitHub. | 8% 8% (n=77) of all Odoo employees (n=94520) were active on GitHub. | 77 77 Odoo employees were active on GitHub. | 
| 11. WikiMedia Foundation | 15% 15% (n=27) of all WikiMedia Foundation engineers (n=18521) were active on GitHub. | (n=27) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 27 27 WikiMedia Foundation employees were active on GitHub. | 
| 12. Cloudflare | 10% 10% (n=54) of all Cloudflare engineers (n=52622) were active on GitHub. | 2% 2% (n=54) of all Cloudflare employees (n=2,44023) were active on GitHub. | 54 54 Cloudflare employees were active on GitHub. | 
| 13. DataDog | 9% 9% (n=132) of all DataDog engineers (n=1,40024) were active on GitHub. | 4% 4% (n=132) of all DataDog employees (n=3,20025) were active on GitHub. | 132 132 DataDog employees were active on GitHub. | 
| 14. MongoDB | 9% 9% (n=79) of all MongoDB engineers (n=86326) were active on GitHub. | 2% 2% (n=79) of all MongoDB employees (n=3,54427) were active on GitHub. | 79 79 MongoDB employees were active on GitHub. | 
| 15. WSO2 | 8% 8% (n=67) of all WSO2 engineers (n=85028) were active on GitHub. | 7% 7% (n=67) of all WSO2 employees (n=97829) were active on GitHub. | 67 67 WSO2 employees were active on GitHub. | 
| 16. New Relic | 8% 8% (n=57) of all New Relic engineers (n=74430) were active on GitHub. | 3% 3% (n=57) of all New Relic employees (n=2,21731) were active on GitHub. | 57 57 New Relic employees were active on GitHub. | 
| 17. Confluent | 8% 8% (n=50) of all Confluent engineers (n=65932) were active on GitHub. | 3% 3% (n=50) of all Confluent employees (n=1,98133) were active on GitHub. | 50 50 Confluent employees were active on GitHub. | 
| 18. Liferay | 6% 6% (n=28) of all Liferay engineers (n=43134) were active on GitHub. | 2% 2% (n=28) of all Liferay employees (n=1,19235) were active on GitHub. | 28 28 Liferay employees were active on GitHub. | 
| 19. ESRI | 5% 5% (n=96) of all ESRI engineers (n=1,82036) were active on GitHub. | 2% 2% (n=96) of all ESRI employees (n=5,42937) were active on GitHub. | 96 96 ESRI employees were active on GitHub. | 
| 20. Okta | 5% 5% (n=63) of all Okta engineers (n=1,23138) were active on GitHub. | 1% 1% (n=63) of all Okta employees (n=5,03039) were active on GitHub. | 63 63 Okta employees were active on GitHub. | 
| 21. Microsoft | 5% 5% (n=2,871) of all Microsoft engineers (n=60,00040) were active on GitHub. | 2% 2% (n=2,871) of all Microsoft employees (n=181,00041) were active on GitHub. | 2,871 2,871 Microsoft employees were active on GitHub. | 
| 22. Unity Technologies | 4% 4% (n=111) of all Unity Technologies engineers (n=2,77642) were active on GitHub. | 2% 2% (n=111) of all Unity Technologies employees (n=5,24543) were active on GitHub. | 111 111 Unity Technologies employees were active on GitHub. | 
| 23. Progress Software | 4% 4% (n=32) of all Progress Software engineers (n=81844) were active on GitHub. | 2% 2% (n=32) of all Progress Software employees (n=2,10345) were active on GitHub. | 32 32 Progress Software employees were active on GitHub. | 
| 24. Square, Inc. | 4% 4% (n=60) of all Square, Inc. engineers (n=1,62146) were active on GitHub. | 1% 1% (n=60) of all Square, Inc. employees (n=8,52147) were active on GitHub. | 60 60 Square, Inc. employees were active on GitHub. | 
| 25. WIX | 3% 3% (n=80) of all WIX engineers (n=2,34948) were active on GitHub. | 2% 2% (n=80) of all WIX employees (n=5,05749) were active on GitHub. | 80 80 WIX employees were active on GitHub. | 
| 26. Alibaba | 3% 3% (n=306) of all Alibaba engineers (n=9,25550) were active on GitHub. | 0% 0% (n=306) of all Alibaba employees (n=251,46251) were active on GitHub. | 306 306 Alibaba employees were active on GitHub. | 
| 27. ThoughtWorks | 3% 3% (n=120) of all ThoughtWorks engineers (n=3,65852) were active on GitHub. | 1% 1% (n=120) of all ThoughtWorks employees (n=10,60053) were active on GitHub. | 120 120 ThoughtWorks employees were active on GitHub. | 
| 28. Shopify | 3% 3% (n=128) of all Shopify engineers (n=4,36054) were active on GitHub. | 1% 1% (n=128) of all Shopify employees (n=10,00055) were active on GitHub. | 128 128 Shopify employees were active on GitHub. | 
| 29. Splunk | 3% 3% (n=57) of all Splunk engineers (n=2,11856) were active on GitHub. | 1% 1% (n=57) of all Splunk employees (n=7,00057) were active on GitHub. | 57 57 Splunk employees were active on GitHub. | 
| 30. Netflix | 3% 3% (n=57) of all Netflix engineers (n=2,12158) were active on GitHub. | 1% 1% (n=57) of all Netflix employees (n=11,30059) were active on GitHub. | 57 57 Netflix employees were active on GitHub. | 
| 31. VMWare | 2% 2% (n=340) of all VMWare engineers (n=13,96560) were active on GitHub. | 1% 1% (n=340) of all VMWare employees (n=37,50061) were active on GitHub. | 340 340 VMWare employees were active on GitHub. | 
| 32. Google | 2% 2% (n=1,254) of all Google engineers (n=62,37762) were active on GitHub. | 1% 1% (n=1,254) of all Google employees (n=156,50063) were active on GitHub. | 1,254 1,254 Google employees were active on GitHub. | 
| 33. Zalando DE | 2% 2% (n=31) of all Zalando DE engineers (n=1,54664) were active on GitHub. | 0% 0% (n=31) of all Zalando DE employees (n=17,04365) were active on GitHub. | 31 31 Zalando DE employees were active on GitHub. | 
| 34. Tencent | 2% 2% (n=232) of all Tencent engineers (n=11,57266) were active on GitHub. | 0% 0% (n=232) of all Tencent employees (n=112,77167) were active on GitHub. | 232 232 Tencent employees were active on GitHub. | 
| 35. Amazon | 2% 2% (n=742) of all Amazon engineers (n=38,27768) were active on GitHub. | 1% 1% (n=742) of all Amazon employees (n=85,26669) were active on GitHub. | 742 742 Amazon employees were active on GitHub. | 
| 36. Twilio | 2% 2% (n=58) of all Twilio engineers (n=3,10370) were active on GitHub. | 1% 1% (n=58) of all Twilio employees (n=7,86771) were active on GitHub. | 58 58 Twilio employees were active on GitHub. | 
| 37. Stripe | 2% 2% (n=55) of all Stripe engineers (n=3,05072) were active on GitHub. | 1% 1% (n=55) of all Stripe employees (n=4,65373) were active on GitHub. | 55 55 Stripe employees were active on GitHub. | 
| 38. BBC | 2% 2% (n=24) of all BBC engineers (n=1,35874) were active on GitHub. | 0% 0% (n=24) of all BBC employees (n=22,21975) were active on GitHub. | 24 24 BBC employees were active on GitHub. | 
| 39. Zendesk | 2% 2% (n=28) of all Zendesk engineers (n=1,65076) were active on GitHub. | 0% 0% (n=28) of all Zendesk employees (n=5,86077) were active on GitHub. | 28 28 Zendesk employees were active on GitHub. | 
| 40. Adobe | 2% 2% (n=162) of all Adobe engineers (n=9,60178) were active on GitHub. | 1% 1% (n=162) of all Adobe employees (n=25,98879) were active on GitHub. | 162 162 Adobe employees were active on GitHub. | 
| 41. Yelp | 2% 2% (n=20) of all Yelp engineers (n=1,23280) were active on GitHub. | 0% 0% (n=20) of all Yelp employees (n=4,40081) were active on GitHub. | 20 20 Yelp employees were active on GitHub. | 
| 42. Twitter | 2% 2% (n=39) of all Twitter engineers (n=2,42482) were active on GitHub. | 0% 0% (n=39) of all Twitter employees (n=8,20083) were active on GitHub. | 39 39 Twitter employees were active on GitHub. | 
| 43. Spotify | 2% 2% (n=51) of all Spotify engineers (n=3,17584) were active on GitHub. | 1% 1% (n=51) of all Spotify employees (n=6,61785) were active on GitHub. | 51 51 Spotify employees were active on GitHub. | 
| 44. Atlassian | 2% 2% (n=51) of all Atlassian engineers (n=3,21686) were active on GitHub. | 1% 1% (n=51) of all Atlassian employees (n=6,43387) were active on GitHub. | 51 51 Atlassian employees were active on GitHub. | 
| 45. Autodesk | 1% 1% (n=52) of all Autodesk engineers (n=3,51988) were active on GitHub. | 0% 0% (n=52) of all Autodesk employees (n=11,50089) were active on GitHub. | 52 52 Autodesk employees were active on GitHub. | 
| 46. Lyft | 1% 1% (n=25) of all Lyft engineers (n=1,78190) were active on GitHub. | 1% 1% (n=25) of all Lyft employees (n=4,45391) were active on GitHub. | 25 25 Lyft employees were active on GitHub. | 
| 47. Airbnb | 1% 1% (n=22) of all Airbnb engineers (n=1,67592) were active on GitHub. | 0% 0% (n=22) of all Airbnb employees (n=6,13293) were active on GitHub. | 22 22 Airbnb employees were active on GitHub. | 
| 48. NVIDIA | 1% 1% (n=200) of all NVIDIA engineers (n=16,24294) were active on GitHub. | 1% 1% (n=200) of all NVIDIA employees (n=22,47395) were active on GitHub. | 200 200 NVIDIA employees were active on GitHub. | 
| 49. Uber | 1% 1% (n=50) of all Uber engineers (n=4,78496) were active on GitHub. | 0% 0% (n=50) of all Uber employees (n=29,30097) were active on GitHub. | 50 50 Uber employees were active on GitHub. | 
| 50. Salesforce | 1% 1% (n=195) of all Salesforce engineers (n=21,35998) were active on GitHub. | 0% 0% (n=195) of all Salesforce employees (n=73,54199) were active on GitHub. | 195 195 Salesforce employees were active on GitHub. | 
| 51. Bloomberg | 1% 1% (n=46) of all Bloomberg engineers (n=5,316100) were active on GitHub. | 0% 0% (n=46) of all Bloomberg employees (n=21,559101) were active on GitHub. | 46 46 Bloomberg employees were active on GitHub. | 
| 52. SAP SE | 1% 1% (n=261) of all SAP SE engineers (n=32,244102) were active on GitHub. | 0% 0% (n=261) of all SAP SE employees (n=107,415103) were active on GitHub. | 261 261 SAP SE employees were active on GitHub. | 
| 53. Yandex | 1% 1% (n=70) of all Yandex engineers (n=9,192104) were active on GitHub. | 0% 0% (n=70) of all Yandex employees (n=18,004105) were active on GitHub. | 70 70 Yandex employees were active on GitHub. | 
| 54. Intel | 1% 1% (n=408) of all Intel engineers (n=61,806106) were active on GitHub. | 0% 0% (n=408) of all Intel employees (n=121,100107) were active on GitHub. | 408 408 Intel employees were active on GitHub. | 
| 55. AMD | 0% 0% (n=53) of all AMD engineers (n=10,749108) were active on GitHub. | 0% 0% (n=53) of all AMD employees (n=15,500109) were active on GitHub. | 53 53 AMD employees were active on GitHub. | 
| 56. Baidu | 0% 0% (n=120) of all Baidu engineers (n=27,500110) were active on GitHub. | 0% 0% (n=120) of all Baidu employees (n=45,500111) were active on GitHub. | 120 120 Baidu employees were active on GitHub. | 
| 57. Workday | 0% 0% (n=20) of all Workday engineers (n=4,886112) were active on GitHub. | 0% 0% (n=20) of all Workday employees (n=15,200113) were active on GitHub. | 20 20 Workday employees were active on GitHub. | 
| 58. Cisco Systems | 0% 0% (n=95) of all Cisco Systems engineers (n=23,532114) were active on GitHub. | 0% 0% (n=95) of all Cisco Systems employees (n=79,500115) were active on GitHub. | 95 95 Cisco Systems employees were active on GitHub. | 
| 59. Oracle | 0% 0% (n=145) of all Oracle engineers (n=40,000116) were active on GitHub. | 0% 0% (n=145) of all Oracle employees (n=132,000117) were active on GitHub. | 145 145 Oracle employees were active on GitHub. | 
| 60. Apple | 0% 0% (n=109) of all Apple engineers (n=33,076118) were active on GitHub. | 0% 0% (n=109) of all Apple employees (n=154,000119) were active on GitHub. | 109 109 Apple employees were active on GitHub. | 
| 61. PayPal | 0% 0% (n=26) of all PayPal engineers (n=9,157120) were active on GitHub. | 0% 0% (n=26) of all PayPal employees (n=30,900121) were active on GitHub. | 26 26 PayPal employees were active on GitHub. | 
| 62. NetEase | 0% 0% (n=39) of all NetEase engineers (n=15,292122) were active on GitHub. | 0% 0% (n=39) of all NetEase employees (n=32,064123) were active on GitHub. | 39 39 NetEase employees were active on GitHub. | 
| 63. Capital One | 0% 0% (n=22) of all Capital One engineers (n=10,151124) were active on GitHub. | 0% 0% (n=22) of all Capital One employees (n=50,767125) were active on GitHub. | 22 22 Capital One employees were active on GitHub. | 
| 64. EPAM Systems | 0% 0% (n=101) of all EPAM Systems engineers (n=52,617126) were active on GitHub. | 0% 0% (n=101) of all EPAM Systems employees (n=58,824127) were active on GitHub. | 101 101 EPAM Systems employees were active on GitHub. | 
| 65. Ericsson | 0% 0% (n=38) of all Ericsson engineers (n=27,379128) were active on GitHub. | 0% 0% (n=38) of all Ericsson employees (n=101,322129) were active on GitHub. | 38 38 Ericsson employees were active on GitHub. | 
| 66. Nokia | 0% 0% (n=28) of all Nokia engineers (n=22,030130) were active on GitHub. | 0% 0% (n=28) of all Nokia employees (n=87,927131) were active on GitHub. | 28 28 Nokia employees were active on GitHub. | 
| 67. Samsung | 0% 0% (n=65) of all Samsung engineers (n=75,229132) were active on GitHub. | 0% 0% (n=65) of all Samsung employees (n=266,673133) were active on GitHub. | 65 65 Samsung employees were active on GitHub. | 
| 68. Huawei | 0% 0% (n=64) of all Huawei engineers (n=107,000134) were active on GitHub. | 0% 0% (n=64) of all Huawei employees (n=195,000135) were active on GitHub. | 64 64 Huawei employees were active on GitHub. | 
| 69. Capgemini | 0% 0% (n=28) of all Capgemini engineers (n=67,119136) were active on GitHub. | 0% 0% (n=28) of all Capgemini employees (n=325,000137) were active on GitHub. | 28 28 Capgemini employees were active on GitHub. | 
| 70. IBM | (n=1,561) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,561) of all IBM employees (n=282,100138) were active on GitHub. | 1,561 1,561 IBM employees were active on GitHub. | 
| 71. Facebook | (n=274) of all Facebook engineers (n=NaN0) were active on GitHub. | 0% 0% (n=274) of all Facebook employees (n=71,970139) were active on GitHub. | 274 274 Facebook employees were active on GitHub. | 
| 72. ByteDance | (n=110) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=110) of all ByteDance employees (n=NaN0) were active on GitHub. | 110 110 ByteDance employees were active on GitHub. | 
| 73. Arm Ltd | (n=98) of all Arm Ltd engineers (n=NaN0) were active on GitHub. | (n=98) of all Arm Ltd employees (n=NaN0) were active on GitHub. | 98 98 Arm Ltd employees were active on GitHub. | 
| 74. Canonical | (n=75) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=75) of all Canonical employees (n=NaN0) were active on GitHub. | 75 75 Canonical employees were active on GitHub. | 
| 75. Accenture | (n=66) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=66) of all Accenture employees (n=624,000140) were active on GitHub. | 66 66 Accenture employees were active on GitHub. | 
| 76. PingCAP | (n=46) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=46) of all PingCAP employees (n=NaN0) were active on GitHub. | 46 46 PingCAP employees were active on GitHub. | 
| 77. Yahoo! | (n=44) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=44) of all Yahoo! employees (n=NaN0) were active on GitHub. | 44 44 Yahoo! employees were active on GitHub. | 
| 78. Intuit | (n=35) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=35) of all Intuit employees (n=13,500141) were active on GitHub. | 35 35 Intuit employees were active on GitHub. | 
| 79. Sentry.io | (n=33) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=33) of all Sentry.io employees (n=NaN0) were active on GitHub. | 33 33 Sentry.io employees were active on GitHub. | 
| 80. Snyk | (n=33) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=33) of all Snyk employees (n=NaN0) were active on GitHub. | 33 33 Snyk employees were active on GitHub. | 
| 81. ???? | (n=31) of all ???? engineers (n=NaN0) were active on GitHub. | (n=31) of all ???? employees (n=NaN0) were active on GitHub. | 31 31 ???? employees were active on GitHub. | 
| 82. Kitware | (n=30) of all Kitware engineers (n=NaN0) were active on GitHub. | 18% 18% (n=30) of all Kitware employees (n=163142) were active on GitHub. | 30 30 Kitware employees were active on GitHub. | 
| 83. HERE Technologies | (n=30) of all HERE Technologies engineers (n=NaN0) were active on GitHub. | (n=30) of all HERE Technologies employees (n=NaN0) were active on GitHub. | 30 30 HERE Technologies employees were active on GitHub. | 
| 84. Databricks | (n=29) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=29) of all Databricks employees (n=NaN0) were active on GitHub. | 29 29 Databricks employees were active on GitHub. | 
| 85. Software Mansion | (n=29) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=29) of all Software Mansion employees (n=NaN0) were active on GitHub. | 29 29 Software Mansion employees were active on GitHub. | 
| 86. 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. | 
| 87. Puppet Labs | (n=27) of all Puppet Labs engineers (n=NaN0) were active on GitHub. | (n=27) of all Puppet Labs employees (n=NaN0) were active on GitHub. | 27 27 Puppet Labs employees were active on GitHub. | 
| 88. TU Delft | (n=27) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=27) of all TU Delft employees (n=NaN0) were active on GitHub. | 27 27 TU Delft employees were active on GitHub. | 
| 89. App Academy (@appacademy) | (n=26) of all App Academy (@appacademy) engineers (n=NaN0) were active on GitHub. | (n=26) of all App Academy (@appacademy) employees (n=NaN0) were active on GitHub. | 26 26 App Academy (@appacademy) employees were active on GitHub. | 
| 90. Palo Alto Networks | (n=26) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=26) of all Palo Alto Networks employees (n=10,473143) were active on GitHub. | 26 26 Palo Alto Networks employees were active on GitHub. | 
| 91. Broad Institute | (n=26) of all Broad Institute engineers (n=NaN0) were active on GitHub. | (n=26) of all Broad Institute employees (n=NaN0) were active on GitHub. | 26 26 Broad Institute employees were active on GitHub. | 
| 92. M247 Ltd | (n=26) of all M247 Ltd engineers (n=NaN0) were active on GitHub. | (n=26) of all M247 Ltd employees (n=NaN0) were active on GitHub. | 26 26 M247 Ltd employees were active on GitHub. | 
| 93. Trybe | (n=24) of all Trybe engineers (n=NaN0) were active on GitHub. | (n=24) of all Trybe employees (n=NaN0) were active on GitHub. | 24 24 Trybe employees were active on GitHub. | 
| 94. Talend | (n=24) of all Talend engineers (n=NaN0) were active on GitHub. | (n=24) of all Talend employees (n=NaN0) were active on GitHub. | 24 24 Talend employees were active on GitHub. | 
| 95. Camptocamp | (n=21) of all Camptocamp engineers (n=NaN0) were active on GitHub. | (n=21) of all Camptocamp employees (n=NaN0) were active on GitHub. | 21 21 Camptocamp employees were active on GitHub. | 
| 96. ?? | (n=20) of all ?? engineers (n=NaN0) were active on GitHub. | (n=20) of all ?? employees (n=NaN0) were active on GitHub. | 20 20 ?? employees were active on GitHub. | 
| 97. RStudio | (n=20) of all RStudio engineers (n=NaN0) were active on GitHub. | (n=20) of all RStudio employees (n=NaN0) were active on GitHub. | 20 20 RStudio 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. CircleCI | (n=20) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=20) of all CircleCI employees (n=NaN0) were active on GitHub. | 20 20 CircleCI employees were active on GitHub. | 
| 100. M247 Ltd | (n=19) of all M247 Ltd engineers (n=NaN0) were active on GitHub. | (n=19) of all M247 Ltd employees (n=NaN0) were active on GitHub. | 19 19 M247 Ltd employees were active on GitHub. | 
References
- 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)
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 14)
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 16)
- 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)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- New Relic engineer count: linkedin.com
- New Relic employee count: sec.gov (page 8)
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 14)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 13)
- Microsoft engineer count: sec.gov (page 8, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 8)
- Unity Technologies engineer count: sec.gov (page 11, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 11)
- Progress Software engineer count: sec.gov (page 9, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 9)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 13)
- WIX engineer count: sec.gov (page 139, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 139)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Annual Report, page 168)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- 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)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 14)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 9)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 75)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Twilio engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 12)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- BBC engineer count: linkedin.com
- BBC employee count: downloads.bbc.co.uk (page 53)
- Zendesk engineer count: sec.gov (page 9, referred to as employees in 'research and development')
- Zendesk employee count: sec.gov (page 54)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 16)
- Yelp engineer count: sec.gov (page 13, referred to as employees in 'product development')
- Yelp employee count: sec.gov (page 13)
- Twitter engineer count: linkedin.com
- Twitter 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)
- 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)
- Autodesk engineer count: linkedin.com
- Autodesk employee count: sec.gov (page 13)
- 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)
- Airbnb engineer count: sec.gov (page 5)
- Airbnb employee count: sec.gov (page 6)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 8)
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 9)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- 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)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 13)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Baidu engineer count: sec.gov (page 185, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 185)
- Workday engineer count: linkedin.com
- Workday employee count: sec.gov (page 3)
- 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 14, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 14)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- NetEase engineer count: sec.gov (page 146, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 146)
- Capital One engineer count: linkedin.com
- Capital One employee count: sec.gov (page 17)
- 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)
- 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)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 3)
- IBM employee count: ibm.com (page 15)
- Facebook employee count: sec.gov (page 10)
- Accenture employee count: sec.gov (page 21)
- Intuit employee count: sec.gov (page 14)
- Kitware employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)