StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Home
  2. Companies
  3. Sequoia Consulting Group
Sequoia Consulting Group

Sequoia Consulting Group

sequoia.com

HR + Employee Benefits, Insurance

53tools
3decisions
0followers
OverviewTech Stack53Dev Feed

Tech Stack

View all 53
Stack by Layer
Application & Data26
Utilities8
DevOps14
Business Tools5
Application & Data
26 tools (49%)
Utilities
8 tools (15%)
DevOps
14 tools (26%)
Business Tools
5 tools (9%)

Application & Data

26
R LanguageGoogle BigQueryownCloudNode.jsPythonMySQLNGINXSassJavaJavaScriptSwiftGolangAmazon EC2Amazon S3Amazon RDSAmazon Route 53MongoDBRedisFlaskDockerAmazon EC2 Container ServiceReduxTypeScriptGraphQLSnowflakeAWS Glue

Utilities

8
ShinySisenseAmazon SESPostmanMicrosoft TeamsAmazon SNSAmazon SQSAirflow

DevOps

14
WebpackJiraVisual StudioXcodeGitHubJenkinsJestCypressMochaTerraformVisual Studio CodeKibanaLogstashDatadog

Business Tools

5
MarketoSalesforce Sales CloudReactConfluenceFigma

Latest from Engineering

View all
Anonymous
Anonymous

Jul 18, 2019

Needs advice

We have decided to make use of R for ML and Shiny for UI. We are debating usage of self hosted shiny server v/s shinyapp . Our Decision to go with R was to do with Sizes of data and availability of tools. R Shiny

14.7k views14.7k
Comments
Vishwa Bhat
Vishwa Bhat

Fullstack Developer at Sequoia Consulting Group

Jul 9, 2019

Needs advice

We use Jira for following Agile methodology and Confluence for maintaining Product and Code Documentations. Microsoft Teams for internal team communication

92.1k views92.1k
Comments
Vishwa Bhat
Vishwa Bhat

Fullstack Developer at Sequoia Consulting Group

Jul 9, 2019

Needs advice

Our new backend micro services are primarily written in Node.js and Go and legacy systems are written in Java. For our new stack decision, we aimed to achieve greater developer productivity, low IO latency and good community so we had couple of technologies in hand to choose but finally we concluded to go for Node.js for API layer and Go for CPU/IO intensive tasks. Currently the inter-services communication is happening via REST but soon to be moved to RPC-based communication.

8.81k views8.81k
Comments

Team on StackShare

3
Vishwa Bhat
vivekseq
Indrajeet Kumar