
Xsolla Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 56 interview experiences · FREE TO READ
Which role are you interviewing for?
27 roles · 56 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Xsolla.
QA Lead
I was contacted directly on LinkedIn to start the interview process. It included a recruiter screen, an interview with a senior engineer, and a final interview with a QA person who was in Eastern Europe. Everything went well, and there were no issues during the process, but then I was ghosted. No decision or feedback or closure. I even followed up with an email asking for an update and got nothing back. It's really unprofessional and shows no respect for candidate's time. If this is how they hire, I can only imagine how they work internally.
- Are you familiar with Docker?
Accounting Assistant
I sent in my application via the company website and heard back about a month later with an interview request. It was a virtual interview and they told me there's just one interview session, which I thought was pretty quick and saved a lot of time.
- Can you describe how you manage stress?
- How do you approach conflict resolution?
- What kind of team environment do you thrive in?
Customer Service Representative
First, I did an assessment and answered some questions by email before the actual interview. Then, I met with two interviewers. We talked about how my skills fit the job, why I wanted to work there, and other typical interview stuff. They really paid attention and asked follow-up questions based on what I said. It was a really good and interesting chat.
- Given that your current pay is higher than what we can offer for this role, what's motivating you to apply?
- Tell me about your skills and how they relate to this job.
- What makes you want to apply for this role?
Product Designer
The interview process took about 4 months. The first two interviews were good. After that, communication was poor, and I had to chase them for scheduling, sometimes with very little notice. The interviews themselves were fine, but the scheduling and email communication were difficult. They initially indicated I was a strong candidate and nearing an offer. However, another interview was required, which again took a long time to schedule. After the final interview, I was told feedback was positive and we moved to budget negotiations. Ultimately, I learned there was a hiring freeze and budget issues, preventing them from hiring me despite the extended process. It was frustrating given the time invested, and I'm unsure why the process wasn't stopped sooner.
- What were your motivations for this role?
Xsolla Interview Questions
Quoted word for word from Xsolla interview reports.
“what are the window functions in SQL?”
Read reports →“Can you explain the implementation of slices in Golang?”
Read reports →“Can you explain the difference between server-side rendering and client-side rendering?”
Read reports →“Can you explain how stdin/stdout/stderr work on a Linux machine?”
Read reports →“Can you tell me about any recent developments in the gaming world?”
Read report →“What are your thoughts on ReactJS class-based components?”
Read report →“Could you tell us about machine learning algorithms?”
Read report →“Can you explain the principles of Object-Oriented Programming?”
Read report →“Do you enjoy playing games?”
Read report →Formats, difficulty and experience
Across all 56 Xsolla interview reports.