
Lodestone Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Which role are you interviewing for?
6 roles · 15 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Lodestone.
QA Analyst
It was a good, tough interview experience. It helps new hires prepare with strong knowledge and gain confidence for future interviews. It was a great experience overall with more than 4 rounds, and each round was unique, allowing for learning in every aspect.
- Can you explain the Software Development Life Cycle (SDLC)?
- Could you describe the Bug life cycle?
Search Quality Analyst
The entire interview process felt really disorganized. I spent about 5 hours total in the interview, but only about 2 of those hours were actually talking to the hiring managers. After the interview, I tried to reach out to several contacts, but it took months to get any kind of response. Then, I had a second interview, and I also completed a personality test to figure out which team would be the best fit for me. After I sent in that test, I never heard back from anyone at Lodestone. The whole team seems unresponsive. Ultimately, I decided this company wasn't the right place for me, so I stopped following up. It wasn't a great interview experience overall.
- Review the answers from a prior screening test.
Software Engineer
So out of all interviews I have had, Lodestone was possibly the worst experience I have ever went through. Initially there is a jobinar to give details about the process. Next was a coding challenge that was fairly difficult for the time alotted. 3 coding problems 2 multiple choice. I still moved on despite only getting 1 coding problem fully passed. These steps felt fairly standard, but the rest I had a negative experience. The recruiter for one called several of my peers to check in and confirm interview times (before and after the interview) except for me, not even getting a reply to my email confirming the interview time. The behavioral interview was pretty unprofessional and rude. There were two people, one of which showed up on time that was shadowing for the most part as well as the main interviewer who decided to show up 20 minutes late. The shadower seemed awkward and did not know how to start the process without the main interviewer which I do not believe was his fault. The main interviewer came in uninterested and a negative tone in his voice. For simple questions, he simply did not like me providing background information on the scenario but rather wanted a short 2 sentence answer. In addition, they had the audacity to ask me about working with another interviewee on a project (a peer I had worked with before) during my interview instead of asking about how I worked in the group in general. This made me feel I was given this interview for partially two reasons. One, to get more information on another potential interviewee, and two, to get more experience in interviewing for the shadowers during the interview (the person who showed up on time did not even have a say as the main interviewer rejected me by the end of the interview with no consultation). Overall, Lodestone's interview process was extremely toxic and unprofessional. I personally believe interviewers and recruiters should show unfavored bias from the get go as well as act professional during the process. If there is another agenda, I would prefer to be rejected prior to setting a meeting than waste my time.
- Tell me about a time you had a disagreement with a manager and how you resolved it.
- Can you explain SQL as if you were talking to a 5-year-old?
- What is the estimated time it would take to become proficient in PHP?
Technical Program Manager
They started with a case study before any HR calls or hiring manager interviews, which made me think they really liked my resume. I skipped straight to this tough case study that took days. I then presented my findings and passed that part. After that, I met with the hiring manager, who then told me I lacked sufficient experience as a Technical Program Manager. It's frustrating that they didn't assess this earlier, wasting everyone's time. It feels like a backward process.
- Can you discuss risk management?
- Can you tell me about an end-to-end project you were involved in?
Lodestone Interview Questions
Quoted word for word from Lodestone interview reports.
“Given a 2D grid containing 0s and 1s, write a function that iterates through it. Upon encountering a 1, it should modify the entire row and column containing that 1 to be filled with 1s.”
Read reports →“For the Connect 4 game, how would you implement a check to determine if a player has won horizontally, vertically, or diagonally? Could you also solve this recursively?”
Read reports →“What is the estimated time it would take to become proficient in PHP?”
Read reports →“What do you understand by bugs?”
Read reports →“Describe how you would test the Google search feature, outlining both manual and automation testing steps.”
Read report →“Can you explain what regression testing is?”
Read report →“Can you explain SQL as if you were talking to a 5-year-old?”
Read report →“Can you describe various types of testing, such as smoke testing and regression testing?”
Read report →“Tell me about commands in different programming languages.”
Read report →Formats, difficulty and experience
Across all 15 Lodestone interview reports.