Corporate GitHub Activity
Most Active Corporations on GitHub, 07 2026
Ranking companies with employees who, during 07 2026, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Sentry.io | 31% 31% (n=55) of all Sentry.io engineers (n=1781) were active on GitHub. | 13% 13% (n=55) of all Sentry.io employees (n=4222) were active on GitHub. | 55 55 Sentry.io employees were active on GitHub. |
|---|---|---|---|
| 2. Vercel | 29% 29% (n=83) of all Vercel engineers (n=2863) were active on GitHub. | 10% 10% (n=83) of all Vercel employees (n=8484) were active on GitHub. | 83 83 Vercel employees were active on GitHub. |
| 3. ClickHouse | 27% 27% (n=59) of all ClickHouse engineers (n=2215) were active on GitHub. | 12% 12% (n=59) of all ClickHouse employees (n=5096) were active on GitHub. | 59 59 ClickHouse employees were active on GitHub. |
| 4. Grafana Labs | 18% 18% (n=125) of all Grafana Labs engineers (n=7077) were active on GitHub. | 7% 7% (n=125) of all Grafana Labs employees (n=1,7728) were active on GitHub. | 125 125 Grafana Labs employees were active on GitHub. |
| 5. Elastic | 12% 12% (n=165) of all Elastic engineers (n=1,4219) were active on GitHub. | 5% 5% (n=165) of all Elastic employees (n=3,53710) were active on GitHub. | 165 165 Elastic employees were active on GitHub. |
| 6. Automattic | 11% 11% (n=74) of all Automattic engineers (n=66111) were active on GitHub. | 5% 5% (n=74) of all Automattic employees (n=1,46112) were active on GitHub. | 74 74 Automattic employees were active on GitHub. |
| 7. Cloudflare | 5% 5% (n=65) of all Cloudflare engineers (n=1,30813) were active on GitHub. | 1% 1% (n=65) of all Cloudflare employees (n=5,15614) were active on GitHub. | 65 65 Cloudflare employees were active on GitHub. |
| 8. Docker | 5% 5% (n=10) of all Docker engineers (n=20915) were active on GitHub. | 1% 1% (n=10) of all Docker employees (n=94916) were active on GitHub. | 10 10 Docker employees were active on GitHub. |
| 9. JetBrains | 4% 4% (n=49) of all JetBrains engineers (n=1,19517) were active on GitHub. | 2% 2% (n=49) of all JetBrains employees (n=2,24518) were active on GitHub. | 49 49 JetBrains employees were active on GitHub. |
| 10. SUSE | 4% 4% (n=30) of all SUSE engineers (n=73619) were active on GitHub. | 1% 1% (n=30) of all SUSE employees (n=2,70820) were active on GitHub. | 30 30 SUSE employees were active on GitHub. |
| 11. Mozilla | 3% 3% (n=21) of all Mozilla engineers (n=66821) were active on GitHub. | 1% 1% (n=21) of all Mozilla employees (n=1,76122) were active on GitHub. | 21 21 Mozilla employees were active on GitHub. |
| 12. Tenstorrent | 3% 3% (n=17) of all Tenstorrent engineers (n=63523) were active on GitHub. | 2% 2% (n=17) of all Tenstorrent employees (n=1,12324) were active on GitHub. | 17 17 Tenstorrent employees were active on GitHub. |
| 13. Odoo | 1% 1% (n=14) of all Odoo engineers (n=1,07425) were active on GitHub. | 0% 0% (n=14) of all Odoo employees (n=7,81826) were active on GitHub. | 14 14 Odoo employees were active on GitHub. |
| 14. OpenAI | 1% 1% (n=32) of all OpenAI engineers (n=2,91627) were active on GitHub. | 0% 0% (n=32) of all OpenAI employees (n=7,30328) were active on GitHub. | 32 32 OpenAI employees were active on GitHub. |
| 15. Confluent | 1% 1% (n=13) of all Confluent engineers (n=1,36729) were active on GitHub. | 0% 0% (n=13) of all Confluent employees (n=3,24130) were active on GitHub. | 13 13 Confluent employees were active on GitHub. |
| 16. NVIDIA | 1% 1% (n=276) of all NVIDIA engineers (n=31,00031) were active on GitHub. | 1% 1% (n=276) of all NVIDIA employees (n=42,00032) were active on GitHub. | 276 276 NVIDIA employees were active on GitHub. |
| 17. DataDog | 1% 1% (n=33) of all DataDog engineers (n=3,90033) were active on GitHub. | 0% 0% (n=33) of all DataDog employees (n=8,10034) were active on GitHub. | 33 33 DataDog employees were active on GitHub. |
| 18. WSO2 | 1% 1% (n=6) of all WSO2 engineers (n=72535) were active on GitHub. | 0% 0% (n=6) of all WSO2 employees (n=1,21536) were active on GitHub. | 6 6 WSO2 employees were active on GitHub. |
| 19. Microsoft | 1% 1% (n=472) of all Microsoft engineers (n=80,00037) were active on GitHub. | 0% 0% (n=472) of all Microsoft employees (n=228,00038) were active on GitHub. | 472 472 Microsoft employees were active on GitHub. |
| 20. Alibaba | 0% 0% (n=48) of all Alibaba engineers (n=9,84739) were active on GitHub. | 0% 0% (n=48) of all Alibaba employees (n=126,66140) were active on GitHub. | 48 48 Alibaba employees were active on GitHub. |
| 21. Snowflake, Inc. | 0% 0% (n=11) of all Snowflake, Inc. engineers (n=2,25741) were active on GitHub. | 0% 0% (n=11) of all Snowflake, Inc. employees (n=7,83442) were active on GitHub. | 11 11 Snowflake, Inc. employees were active on GitHub. |
| 22. AMD | 0% 0% (n=106) of all AMD engineers (n=21,98443) were active on GitHub. | 0% 0% (n=106) of all AMD employees (n=31,00044) were active on GitHub. | 106 106 AMD employees were active on GitHub. |
| 23. Shopify | 0% 0% (n=17) of all Shopify engineers (n=4,65845) were active on GitHub. | 0% 0% (n=17) of all Shopify employees (n=7,60046) were active on GitHub. | 17 17 Shopify employees were active on GitHub. |
| 24. Databricks | 0% 0% (n=17) of all Databricks engineers (n=6,20447) were active on GitHub. | 0% 0% (n=17) of all Databricks employees (n=14,59248) were active on GitHub. | 17 17 Databricks employees were active on GitHub. |
| 25. Arm Ltd | 0% 0% (n=19) of all Arm Ltd engineers (n=6,94349) were active on GitHub. | 0% 0% (n=19) of all Arm Ltd employees (n=8,33050) were active on GitHub. | 19 19 Arm Ltd employees were active on GitHub. |
| 26. Tencent | 0% 0% (n=34) of all Tencent engineers (n=13,32951) were active on GitHub. | 0% 0% (n=34) of all Tencent employees (n=110,55852) were active on GitHub. | 34 34 Tencent employees were active on GitHub. |
| 27. Google | 0% 0% (n=185) of all Google engineers (n=83,31853) were active on GitHub. | 0% 0% (n=185) of all Google employees (n=190,82054) were active on GitHub. | 185 185 Google employees were active on GitHub. |
| 28. Square, Inc. | 0% 0% (n=6) of all Square, Inc. engineers (n=2,95055) were active on GitHub. | 0% 0% (n=6) of all Square, Inc. employees (n=10,20556) were active on GitHub. | 6 6 Square, Inc. employees were active on GitHub. |
| 29. Netflix | 0% 0% (n=6) of all Netflix engineers (n=3,13057) were active on GitHub. | 0% 0% (n=6) of all Netflix employees (n=16,00058) were active on GitHub. | 6 6 Netflix employees were active on GitHub. |
| 30. Amazon | 0% 0% (n=91) of all Amazon engineers (n=49,06659) were active on GitHub. | 0% 0% (n=91) of all Amazon employees (n=153,71060) were active on GitHub. | 91 91 Amazon employees were active on GitHub. |
| 31. Adobe | 0% 0% (n=21) of all Adobe engineers (n=11,43661) were active on GitHub. | 0% 0% (n=21) of all Adobe employees (n=31,36062) were active on GitHub. | 21 21 Adobe employees were active on GitHub. |
| 32. Airbnb | 0% 0% (n=6) of all Airbnb engineers (n=3,69663) were active on GitHub. | 0% 0% (n=6) of all Airbnb employees (n=8,20064) were active on GitHub. | 6 6 Airbnb employees were active on GitHub. |
| 33. Apple | 0% 0% (n=62) of all Apple engineers (n=45,93265) were active on GitHub. | 0% 0% (n=62) of all Apple employees (n=166,00066) were active on GitHub. | 62 62 Apple employees were active on GitHub. |
| 34. Meta | 0% 0% (n=50) of all Meta engineers (n=39,83567) were active on GitHub. | 0% 0% (n=50) of all Meta employees (n=78,86568) were active on GitHub. | 50 50 Meta employees were active on GitHub. |
| 35. Uber | 0% 0% (n=10) of all Uber engineers (n=8,75969) were active on GitHub. | 0% 0% (n=10) of all Uber employees (n=34,00070) were active on GitHub. | 10 10 Uber employees were active on GitHub. |
| 36. Intel | 0% 0% (n=47) of all Intel engineers (n=51,69371) were active on GitHub. | 0% 0% (n=47) of all Intel employees (n=85,10072) were active on GitHub. | 47 47 Intel employees were active on GitHub. |
| 37. Broadcom | 0% 0% (n=17) of all Broadcom engineers (n=18,81073) were active on GitHub. | 0% 0% (n=17) of all Broadcom employees (n=33,00074) were active on GitHub. | 17 17 Broadcom employees were active on GitHub. |
| 38. Cisco Systems | 0% 0% (n=21) of all Cisco Systems engineers (n=25,25675) were active on GitHub. | 0% 0% (n=21) of all Cisco Systems employees (n=86,20076) were active on GitHub. | 21 21 Cisco Systems employees were active on GitHub. |
| 39. Salesforce | 0% 0% (n=9) of all Salesforce engineers (n=24,35977) were active on GitHub. | 0% 0% (n=9) of all Salesforce employees (n=83,33478) were active on GitHub. | 9 9 Salesforce employees were active on GitHub. |
| 40. SAP SE | 0% 0% (n=6) of all SAP SE engineers (n=37,96579) were active on GitHub. | 0% 0% (n=6) of all SAP SE employees (n=111,39780) were active on GitHub. | 6 6 SAP SE employees were active on GitHub. |
| 41. Huawei | 0% 0% (n=11) of all Huawei engineers (n=113,00081) were active on GitHub. | 0% 0% (n=11) of all Huawei employees (n=208,00082) were active on GitHub. | 11 11 Huawei employees were active on GitHub. |
| 42. IBM | (n=223) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=223) of all IBM employees (n=264,30083) were active on GitHub. | 223 223 IBM employees were active on GitHub. |
| 43. ByteDance | (n=45) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=45) of all ByteDance employees (n=NaN0) were active on GitHub. | 45 45 ByteDance employees were active on GitHub. |
| 44. PostHog | (n=28) of all PostHog engineers (n=NaN0) were active on GitHub. | (n=28) of all PostHog employees (n=NaN0) were active on GitHub. | 28 28 PostHog employees were active on GitHub. |
| 45. Software Mansion | (n=20) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=20) of all Software Mansion employees (n=NaN0) were active on GitHub. | 20 20 Software Mansion employees were active on GitHub. |
| 46. Supabase | (n=20) of all Supabase engineers (n=NaN0) were active on GitHub. | (n=20) of all Supabase employees (n=NaN0) were active on GitHub. | 20 20 Supabase employees were active on GitHub. |
| 47. @PostHog | (n=18) of all @PostHog engineers (n=NaN0) were active on GitHub. | (n=18) of all @PostHog employees (n=NaN0) were active on GitHub. | 18 18 @PostHog employees were active on GitHub. |
| 48. @gravitational | (n=17) of all @gravitational engineers (n=NaN0) were active on GitHub. | (n=17) of all @gravitational employees (n=NaN0) were active on GitHub. | 17 17 @gravitational employees were active on GitHub. |
| 49. Metabase | (n=16) of all Metabase engineers (n=NaN0) were active on GitHub. | (n=16) of all Metabase employees (n=NaN0) were active on GitHub. | 16 16 Metabase employees were active on GitHub. |
| 50. @PostHog | (n=16) of all @PostHog engineers (n=NaN0) were active on GitHub. | (n=16) of all @PostHog employees (n=NaN0) were active on GitHub. | 16 16 @PostHog employees were active on GitHub. |
| 51. @zed-industries | (n=14) of all @zed-industries engineers (n=NaN0) were active on GitHub. | (n=14) of all @zed-industries employees (n=NaN0) were active on GitHub. | 14 14 @zed-industries employees were active on GitHub. |
| 52. @expo | (n=14) of all @expo engineers (n=NaN0) were active on GitHub. | (n=14) of all @expo employees (n=NaN0) were active on GitHub. | 14 14 @expo employees were active on GitHub. |
| 53. Camunda | (n=13) of all Camunda engineers (n=NaN0) were active on GitHub. | (n=13) of all Camunda employees (n=NaN0) were active on GitHub. | 13 13 Camunda employees were active on GitHub. |
| 54. @supabase | (n=13) of all @supabase engineers (n=NaN0) were active on GitHub. | (n=13) of all @supabase employees (n=NaN0) were active on GitHub. | 13 13 @supabase employees were active on GitHub. |
| 55. @apache | (n=12) of all @apache engineers (n=NaN0) were active on GitHub. | (n=12) of all @apache employees (n=NaN0) were active on GitHub. | 12 12 @apache employees were active on GitHub. |
| 56. n8n | (n=11) of all n8n engineers (n=NaN0) were active on GitHub. | (n=11) of all n8n employees (n=NaN0) were active on GitHub. | 11 11 n8n employees were active on GitHub. |
| 57. @bitwarden | (n=10) of all @bitwarden engineers (n=NaN0) were active on GitHub. | (n=10) of all @bitwarden employees (n=NaN0) were active on GitHub. | 10 10 @bitwarden employees were active on GitHub. |
| 58. Teleport | (n=10) of all Teleport engineers (n=NaN0) were active on GitHub. | (n=10) of all Teleport employees (n=NaN0) were active on GitHub. | 10 10 Teleport employees were active on GitHub. |
| 59. @n8n-io | (n=10) of all @n8n-io engineers (n=NaN0) were active on GitHub. | (n=10) of all @n8n-io employees (n=NaN0) were active on GitHub. | 10 10 @n8n-io employees were active on GitHub. |
| 60. Posit | (n=10) of all Posit engineers (n=NaN0) were active on GitHub. | (n=10) of all Posit employees (n=NaN0) were active on GitHub. | 10 10 Posit employees were active on GitHub. |
| 61. @camunda | (n=10) of all @camunda engineers (n=NaN0) were active on GitHub. | (n=10) of all @camunda employees (n=NaN0) were active on GitHub. | 10 10 @camunda employees were active on GitHub. |
| 62. Canonical | (n=10) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=10) of all Canonical employees (n=NaN0) were active on GitHub. | 10 10 Canonical employees were active on GitHub. |
| 63. @clerk | (n=10) of all @clerk engineers (n=NaN0) were active on GitHub. | (n=10) of all @clerk employees (n=NaN0) were active on GitHub. | 10 10 @clerk employees were active on GitHub. |
| 64. Sentry | (n=9) of all Sentry engineers (n=NaN0) were active on GitHub. | (n=9) of all Sentry employees (n=NaN0) were active on GitHub. | 9 9 Sentry employees were active on GitHub. |
| 65. Juspay | (n=9) of all Juspay engineers (n=NaN0) were active on GitHub. | (n=9) of all Juspay employees (n=NaN0) were active on GitHub. | 9 9 Juspay employees were active on GitHub. |
| 66. Bitwarden | (n=9) of all Bitwarden engineers (n=NaN0) were active on GitHub. | (n=9) of all Bitwarden employees (n=NaN0) were active on GitHub. | 9 9 Bitwarden employees were active on GitHub. |
| 67. Coder | (n=8) of all Coder engineers (n=NaN0) were active on GitHub. | (n=8) of all Coder employees (n=NaN0) were active on GitHub. | 8 8 Coder employees were active on GitHub. |
| 68. @temporalio | (n=8) of all @temporalio engineers (n=NaN0) were active on GitHub. | (n=8) of all @temporalio employees (n=NaN0) were active on GitHub. | 8 8 @temporalio employees were active on GitHub. |
| 69. @RocketChat | (n=8) of all @RocketChat engineers (n=NaN0) were active on GitHub. | (n=8) of all @RocketChat employees (n=NaN0) were active on GitHub. | 8 8 @RocketChat employees were active on GitHub. |
| 70. Figma | (n=8) of all Figma engineers (n=NaN0) were active on GitHub. | (n=8) of all Figma employees (n=NaN0) were active on GitHub. | 8 8 Figma employees were active on GitHub. |
| 71. @Kong | (n=8) of all @Kong engineers (n=NaN0) were active on GitHub. | (n=8) of all @Kong employees (n=NaN0) were active on GitHub. | 8 8 @Kong employees were active on GitHub. |
| 72. Warp | (n=7) of all Warp engineers (n=NaN0) were active on GitHub. | (n=7) of all Warp employees (n=NaN0) were active on GitHub. | 7 7 Warp employees were active on GitHub. |
| 73. @antgroup | (n=7) of all @antgroup engineers (n=NaN0) were active on GitHub. | (n=7) of all @antgroup employees (n=NaN0) were active on GitHub. | 7 7 @antgroup employees were active on GitHub. |
| 74. @supabase | (n=7) of all @supabase engineers (n=NaN0) were active on GitHub. | (n=7) of all @supabase employees (n=NaN0) were active on GitHub. | 7 7 @supabase employees were active on GitHub. |
| 75. SpecterOps | (n=7) of all SpecterOps engineers (n=NaN0) were active on GitHub. | (n=7) of all SpecterOps employees (n=NaN0) were active on GitHub. | 7 7 SpecterOps employees were active on GitHub. |
| 76. Wazuh | (n=7) of all Wazuh engineers (n=NaN0) were active on GitHub. | (n=7) of all Wazuh employees (n=NaN0) were active on GitHub. | 7 7 Wazuh employees were active on GitHub. |
| 77. @tailscale | (n=7) of all @tailscale engineers (n=NaN0) were active on GitHub. | (n=7) of all @tailscale employees (n=NaN0) were active on GitHub. | 7 7 @tailscale employees were active on GitHub. |
| 78. @oxidecomputer | (n=7) of all @oxidecomputer engineers (n=NaN0) were active on GitHub. | (n=7) of all @oxidecomputer employees (n=NaN0) were active on GitHub. | 7 7 @oxidecomputer employees were active on GitHub. |
| 79. Dust | (n=7) of all Dust engineers (n=NaN0) were active on GitHub. | (n=7) of all Dust employees (n=NaN0) were active on GitHub. | 7 7 Dust employees were active on GitHub. |
| 80. @SelectDB | (n=7) of all @SelectDB engineers (n=NaN0) were active on GitHub. | (n=7) of all @SelectDB employees (n=NaN0) were active on GitHub. | 7 7 @SelectDB employees were active on GitHub. |
| 81. @n8n-io | (n=6) of all @n8n-io engineers (n=NaN0) were active on GitHub. | (n=6) of all @n8n-io employees (n=NaN0) were active on GitHub. | 6 6 @n8n-io employees were active on GitHub. |
| 82. The Linux Foundation | (n=6) of all The Linux Foundation engineers (n=NaN0) were active on GitHub. | (n=6) of all The Linux Foundation employees (n=NaN0) were active on GitHub. | 6 6 The Linux Foundation employees were active on GitHub. |
| 83. Anthropic | (n=6) of all Anthropic engineers (n=NaN0) were active on GitHub. | (n=6) of all Anthropic employees (n=NaN0) were active on GitHub. | 6 6 Anthropic employees were active on GitHub. |
| 84. @Inferact | (n=6) of all @Inferact engineers (n=NaN0) were active on GitHub. | (n=6) of all @Inferact employees (n=NaN0) were active on GitHub. | 6 6 @Inferact employees were active on GitHub. |
| 85. @mattermost | (n=6) of all @mattermost engineers (n=NaN0) were active on GitHub. | (n=6) of all @mattermost employees (n=NaN0) were active on GitHub. | 6 6 @mattermost employees were active on GitHub. |
| 86. @voidzero-dev | (n=6) of all @voidzero-dev engineers (n=NaN0) were active on GitHub. | (n=6) of all @voidzero-dev employees (n=NaN0) were active on GitHub. | 6 6 @voidzero-dev employees were active on GitHub. |
| 87. Kestra | (n=6) of all Kestra engineers (n=NaN0) were active on GitHub. | (n=6) of all Kestra employees (n=NaN0) were active on GitHub. | 6 6 Kestra employees were active on GitHub. |
| 88. @chatwoot | (n=6) of all @chatwoot engineers (n=NaN0) were active on GitHub. | (n=6) of all @chatwoot employees (n=NaN0) were active on GitHub. | 6 6 @chatwoot employees were active on GitHub. |
| 89. @anthropics | (n=6) of all @anthropics engineers (n=NaN0) were active on GitHub. | (n=6) of all @anthropics employees (n=NaN0) were active on GitHub. | 6 6 @anthropics employees were active on GitHub. |
| 90. Union.ai | (n=6) of all Union.ai engineers (n=NaN0) were active on GitHub. | (n=6) of all Union.ai employees (n=NaN0) were active on GitHub. | 6 6 Union.ai employees were active on GitHub. |
| 91. @inngest | (n=6) of all @inngest engineers (n=NaN0) were active on GitHub. | (n=6) of all @inngest employees (n=NaN0) were active on GitHub. | 6 6 @inngest employees were active on GitHub. |
| 92. @SSWConsulting | (n=6) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=6) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 6 6 @SSWConsulting employees were active on GitHub. |
| 93. @zml | (n=6) of all @zml engineers (n=NaN0) were active on GitHub. | (n=6) of all @zml employees (n=NaN0) were active on GitHub. | 6 6 @zml employees were active on GitHub. |
| 94. @yugabyte | (n=6) of all @yugabyte engineers (n=NaN0) were active on GitHub. | (n=6) of all @yugabyte employees (n=NaN0) were active on GitHub. | 6 6 @yugabyte employees were active on GitHub. |
| 95. Builder.io | (n=6) of all Builder.io engineers (n=NaN0) were active on GitHub. | (n=6) of all Builder.io employees (n=NaN0) were active on GitHub. | 6 6 Builder.io employees were active on GitHub. |
| 96. @bitwarden | (n=6) of all @bitwarden engineers (n=NaN0) were active on GitHub. | (n=6) of all @bitwarden employees (n=NaN0) were active on GitHub. | 6 6 @bitwarden employees were active on GitHub. |
| 97. Yugabyte | (n=6) of all Yugabyte engineers (n=NaN0) were active on GitHub. | (n=6) of all Yugabyte employees (n=NaN0) were active on GitHub. | 6 6 Yugabyte employees were active on GitHub. |
| 98. @pydantic | (n=5) of all @pydantic engineers (n=NaN0) were active on GitHub. | (n=5) of all @pydantic employees (n=NaN0) were active on GitHub. | 5 5 @pydantic employees were active on GitHub. |
| 99. LangChain | (n=5) of all LangChain engineers (n=NaN0) were active on GitHub. | (n=5) of all LangChain employees (n=NaN0) were active on GitHub. | 5 5 LangChain employees were active on GitHub. |
| 100. @apache | (n=5) of all @apache engineers (n=NaN0) were active on GitHub. | (n=5) of all @apache employees (n=NaN0) were active on GitHub. | 5 5 @apache employees were active on GitHub. |
References
- Sentry.io engineer count: linkedin.com (Retrieved February 2026)
- Sentry.io employee count: linkedin.com (Retrieved February 2026)
- Vercel engineer count: linkedin.com (Retrieved January 2026)
- Vercel employee count: linkedin.com (Retrieved January 2026)
- ClickHouse engineer count: linkedin.com (Retrieved March 2026)
- ClickHouse employee count: linkedin.com (Retrieved March 2026)
- Grafana Labs engineer count: linkedin.com (Retrieved January 2026)
- Grafana Labs employee count: linkedin.com (Retrieved January 2026)
- Elastic engineer count: linkedin.com (retrieved January 2026)
- Elastic employee count: sec.gov (page 15)
- Automattic engineer count: linkedin.com (Retrieved January 2026)
- Automattic employee count: automattic.com (Retrieved January 2026)
- Cloudflare engineer count: linkedin.com (Retrieved January 2026)
- Cloudflare employee count: sec.gov (page 18)
- Docker engineer count: linkedin.com (Retrieved January 2026)
- Docker employee count: linkedin.com (Retrieved January 2026)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- SUSE engineer count: linkedin.com (Retrieved January 2026)
- SUSE employee count: linkedin.com (Retrieved January 2026)
- Mozilla engineer count: linkedin.com (Retrieved January 2026)
- Mozilla employee count: linkedin.com (Retrieved January 2026)
- Tenstorrent engineer count: linkedin.com (Retrieved March 2026)
- Tenstorrent employee count: linkedin.com (Retrieved March 2026)
- Odoo engineer count: linkedin.com (Retrieved January 2026)
- Odoo employee count: linkedin.com (Retrieved January 2026)
- OpenAI engineer count: linkedin.com (Retrieved February 2026)
- OpenAI employee count: linkedin.com (Retrieved February 2026)
- Confluent engineer count: linkedin.com (Retrieved January 2026)
- Confluent employee count: sec.gov (page 19)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- DataDog engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 12)
- WSO2 engineer count: linkedin.com (Retrieved January 2026)
- WSO2 employee count: linkedin.com (Retrieved January 2026)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- Alibaba engineer count: linkedin.com (Retrieved January 2026)
- Alibaba employee count: data.alibabagroup.com (page 14)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- AMD engineer count: linkedin.com (Retrieved January 2026)
- AMD employee count: sec.gov (page 11)
- Shopify engineer count: linkedin.com (Retrieved January 2026)
- Shopify employee count: sec.gov (page 10)
- Databricks engineer count: linkedin.com (Retrieved February 2026)
- Databricks employee count: linkedin.com (Retrieved February 2026)
- Arm Ltd engineer count: sec.gov (page 110)
- Arm Ltd employee count: sec.gov (page 110)
- Tencent engineer count: linkedin.com (Retrieved January 2026)
- Tencent employee count: static.tencent.com (page 52)
- Google engineer count: linkedin.com (Retrieved January 2026)
- Google employee count: sec.gov (page 7)
- Square, Inc. engineer count: linkedin.com (Retrieved January 2026)
- Square, Inc. employee count: sec.gov (page 19)
- Netflix engineer count: linkedin.com (Retrieved January 2026)
- Netflix employee count: sec.gov (page 2)
- Amazon engineer count: linkedin.com (Retrieved January 2026)
- Amazon employee count: linkedin.com (Retrieved January 2026)
- Adobe engineer count: linkedin.com (Retrieved January 2026)
- Adobe employee count: sec.gov (page 13)
- Airbnb engineer count: linkedin.com (Retrieved March 2026)
- Airbnb employee count: sec.gov (page 5)
- Apple engineer count: linkedin.com (Retrieved January 2025)
- Apple employee count: sec.gov (page 4)
- Meta engineer count: linkedin.com (Retrieved January 2026)
- Meta employee count: sec.gov (page 9)
- Uber engineer count: linkedin.com (Retrieved January 2026)
- Uber employee count: sec.gov (page 7)
- Intel engineer count: linkedin.com (Retrieved January 2026)
- Intel employee count: sec.gov (page 15)
- Broadcom engineer count: sec.gov (page 9, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 9)
- Cisco Systems engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 8)
- Salesforce engineer count: linkedin.com (Retrieved January 2026)
- Salesforce employee count: sec.gov (page 10)
- SAP SE engineer count: sec.gov (page 31, referred to as employees in 'development')
- SAP SE employee count: sec.gov (page 100)
- Huawei engineer count: huawei.com (page 72, referred to as employees in 'R&D')
- Huawei employee count: huawei.com (page 1)
- IBM employee count: ibm.com (page 15)