OSMOSYS Interview Experience for Software Engineer role (On campus)

Hello! My academic journey is accentuated by leadership roles, like heading the ANOVA Data Science Student Club, and notable performances in hackathons.

Setting The Stage

Recently, I had the unique opportunity to participate in an online interview with Osmosys. The process was facilitated on-campus through our dedicated placement coordinators. The company’s search was focused on finding a frontend engineer, someone proficient with technologies like JS, Angular, Swift, React, and the like. Here’s the twist: my expertise wasn’t exactly aligned with what they were seeking. My comfort zone has always been around HTML, CSS, Flask, and of course, the vast expanse of Data Science, Machine Learning, and Deep Learning. Yet, I decided to dive in, banking on my problem-solving skills.

The Aptitude Test

The journey began with an aptitude assessment. The test had a mix of 25 questions, oscillating between aptitude challenges and basic C programming tasks. To my delight, I navigated through this round with ease, tackling data interpretation problems and foundational C coding challenges head-on.

Technical Dive: The Second Round

A brief pause and two days later, I was ushered into the technical round. This was a deep dive, lasting a good 75 to 90 minutes. The focus? Everything that adorned my resume. My choice of Python as my mainstay language opened up a series of questions. A total of ten basic Python-related queries were thrown at me, followed by four problem-solving tasks. Not to boast, but these challenges felt manageable. From identifying palindromes, reversing sorted arrays, to other questions reminiscent of LeetCode’s easy to medium levels, this round was a well-rounded assessment of technical prowess.

The CEO’s Perspective: The Final Round

The climax of this journey was an interaction with the company’s CEO. A direct, no-nonsense approach defined this conversation. We delved into discussions about my background, my aspirations, and even something as unique as my typing speed. He expressed a keen interest in any live, real-world projects I might have spearheaded. A swift yet insightful 20 to 25 minutes, and the round concluded.

Reflection: My Take on the Experience

In retrospection, the entire process was a learning curve. If I were to rate it, I’d peg it at a 3.5 out of 5. This score is purely a reflection of my personal experience and isn’t a critique of the company or its ethos. Every interview is a stepping stone, a learning opportunity, and this was no different. It’s experiences like these that shape our professional journey, and I’m eager to embrace more such challenges in the future.

Thank you for joining me on this recollection. Until next time!