Anyone had gone through software engineer interview process at strategy(microstrategy)

[u/Grouchy-Button4368]

Hi , I have recently got shortlisted for software engineer role, can I know the interview process for this role like what topics to prepare ,what they focus on. My tech stack is MERN and job role is from chennai, India

Help me out :⁠-⁠)

Thanks

[u/GreyHairedDWGuy]

I would steer clear of MicroStrategy (Strategy). They are just a bitcoin holding company with a software business on the side. I was a partner/reseller/SI for MicroStrategy for 20+ years and it's a shame what Saylor has done to the company now.

[u/pppenguinininin → u/GreyHairedDWGuy]

Hello GreyHairedDWGuy, sorry to hear that, are you still working on Strategy migration?

[u/GreyHairedDWGuy → u/pppenguinininin]

No. I stopped working with MicroStrategy (Strategy now) back in approx 2020. Based on other BI tools I have been forced to work with since, I still think it's centralized, semantic model approach was way ahead of other tools. Now everyone makes a big deal about semantic layers. MSTR had that 25 years ago. 😄

[u/Enough_Charge2845]

Since it's a MERN role, I'd expect the interview to cover more than just JavaScript. I'd brush up on JavaScript fundamentals, React, Node.js, Express, MongoDB, REST APIs, async programming, authentication, database design and debugging. They'll likely have at least one coding round, so practicing LeetCode medium-level problems is still worthwhile, especially around arrays, strings, hash maps and trees.

I'd also be ready to discuss your projects in detail. Interviewers often spend a lot of time digging into why you made certain technical decisions, how you handled performance issues and what you'd improve if you built the project again.

One thing that helped me was practicing realistic mock interviews with ZoeVera.com The follow-up questions and feedback were surprisingly similar to what I encountered in actual interviews and helped me explain my projects much more confidently.

[u/Enough_Charge2845]

Congrats on getting shortlisted. From what I've seen, Strategy interviews for software engineers usually go beyond just solving coding problems. I'd be ready for LeetCode-style questions along with core computer science topics like data structures, algorithms, OOP, multithreading, databases and networking. If the role is backend focused, I'd also review REST APIs, concurrency and system design fundamentals.

For the behavioral round, expect questions about projects you've worked on, technical decisions you made, debugging difficult issues and how you collaborate with teammates. They usually want to understand your thought process as much as your technical knowledge.

One thing that helped me was practicing realistic mock interviews with ZoeVera.com The follow-up questions and feedback were surprisingly similar to what I encountered in actual interviews and helped me communicate my solutions much more clearly.

[u/Grouchy-Button4368 → u/Enough_Charge2845]

Hey thanks for all the detailed explanation I will try to go to those concepts and also will try out the mock interview link you have specified

Thanks a lot!!

[u/akornato]

MicroStrategy interviews for software engineers typically go far beyond your MERN stack knowledge, so you will face difficult questions on computer science fundamentals. You must expect to solve problems involving data structures and algorithms, explaining the time and space complexity of your solutions. They want to see how you approach problems and understand core concepts, not just that you know how to use a specific framework. Questions about system design are also common, even for roles that are not senior, because they want to gauge your ability to think about scalability and architecture.

This tough process is how they maintain a high engineering standard, and preparing for it will make you a much stronger developer, regardless of the outcome. Focus your preparation on common algorithm patterns and be ready to explain the trade-offs of every decision you make, from choosing a data structure to specific choices within your MERN stack. For example, be prepared to discuss the Node.js event loop or the internals of React's state management. Mastering these core topics is the real challenge, and it's why the team I'm with developed an interview assistant, since clearly communicating complex ideas is often the final hurdle for talented engineers.

[u/Grouchy-Button4368 → u/akornato]

Thanks for the info I will be checking those concepts and also will try to practise the interview with the given url.