Svitla Systems Interview Questions
& Process

The whole hiring process spanned nearly a month. It started with a brief and pleasant chat with HR. However, getting the technical interview scheduled was a hassle; it took about three weeks, and I had to nudge HR twice. The hiring manager was super busy. Interestingly, they told me I was causing delays when I mentioned I couldn't make it on Thursday or Friday, which felt a bit off considering the earlier scheduling issues. The technical interview itself wasn't bad and didn't involve any live coding. But a few things were weird: 1. When we discussed Django signals, the interviewer claimed a custom signal could automatically fire on bulk operations (like bulk_create/update). I was surprised by this. 2. I asked them to repeat a question about Python garbage collection, and they suggested moving on. Later, this came up in the feedback negatively. 3. The feedback also pointed out gaps in my knowledge of E2E testing and specific database tools, even though we hardly discussed these. Oh, and at the start, the hiring manager asked me to adjust my camera so I was looking straight at it, maybe because I use two monitors. That was a first for me. On the plus side, HR was responsive post-interview and gave me detailed feedback when I asked, which was great. All in all, it was a polite and professional experience, but the scheduling and some parts of the technical chat could definitely be smoother.

The job posting for a senior PHP engineer role looked good, mentioning modern tech like Laravel, Redis, GenAI, OpenSearch, and APIs, and described duties like building scalable APIs, integrating services, and contributing to architecture. However, the interview felt more like a PHP exam than a skills assessment. It started with requirements discussion, then quickly turned into theoretical questions about PHP internals, SOLID, PSRs, and abstract classes, focusing on memorization rather than practical experience. The interviewer seemed frustrated when I couldn't recall every minor PHP version change, emphasizing the need to 'know these concepts in depth.' This theoretical focus, rather than on real-world application in Laravel or problem-solving, made me lose interest. The final straw was a question about regex, which I could answer practically, but the interviewer seemed to expect more theoretical responses. The whole process felt like a gatekeeping exercise, not an evaluation of my ability to build scalable, secure applications. They mentioned a second interview with the client to check for actual skills after this theory test, which seems flawed as practical skills weren't assessed initially. The system seems designed to filter out those who can't memorize documentation, ignoring the practical knowledge expected of senior engineers. The lack of focus on practical skills, security, and real-world problem-solving was frustrating. They seemed obsessed with pointless technicalities, rewarding book smarts over engineering expertise. If you're a seasoned developer focused on building systems and solving problems with modern tools, this process isn't for you as it evaluates theoretical recall over practical expertise and real-world application.

The interview process was easy, with 3 stages for this position. First, a recruiter from Ukraine checked my work experience, expectations, and English. Then, I had a session with a Software Engineer and the hiring manager, covering SOLID principles, OOP, SQL, and .NET basics, but no coding challenge. The final stage was with the client, focusing on behavioral and cultural fit without coding questions. Although I reached the client stage, another candidate was chosen. The process was quick, about 2 weeks. The contract is project-based, not for a talent pool, but the salary is good and paid in USD.

I went through an interview for a Senior Security Analyst role. It was a good experience, and the process was organized. First, there was a recruiter call where they explained the job and company. Then, I had a technical assessment by a Svitla Technical Leader covering Java, algorithms, and SQL, which were challenging but fair. After that, the client I'd be working with conducted a second, more difficult technical assessment. This involved practical, real-time tests for about an hour, requiring deep knowledge of the required technologies.