Pros
I’ve been at QLU for the past 6 months, working with the Neptune team, and it’s been a great experience. I’ve learned so much, from coding to leadership skills. The work can be challenging, but the rewards—both in learning and salary—are worth it.
Kontras
Only those with a relentless grind mindset thrive here.
Pros
-Good Salary -Quarterly increments -unlimited leaves
Kontras
The company’s product management is largely non-technical. Their primary role often seems limited to collecting updates rather than adding strategic value to the product. Requirements are frequently created without proper feasibility checks, seemingly to impress leadership, which results in wasted time and effort. Leadership itself is also non-technical, and many initiatives are driven by random, impractical requests. Feasibility concerns are usually realized only after significant development time has already been invested. The so-called VPs primarily give feedback on superficial aspects like UI/UX design, but there is little to no focus on proper system design, architecture, or long-term scalability. The codebase of existing applications is poorly structured and lacks maintainability. Instead of embracing challenging problems, most senior members tend to avoid them and delegate without proper guidance. The company clearly needs more experienced professionals who have spent years in the industry and understand both technical depth and organizational growth. This culture makes it difficult to grow as an engineer, as innovation and technical excellence are not encouraged.
Pros
Good salary quarterly increment don't know
Kontras
The company’s product management is largely non-technical. Their primary role often seems limited to collecting updates rather than adding strategic value to the product. Requirements are frequently created without proper feasibility checks, seemingly to impress leadership, which results in wasted time and effort. Leadership itself is also non-technical, and many initiatives are driven by random, impractical requests. Feasibility concerns are usually realized only after significant development time has already been invested. The so-called VPs primarily give feedback on superficial aspects like UI/UX design, but there is little to no focus on proper system design, architecture, or long-term scalability. The codebase of existing applications is poorly structured and lacks maintainability. Instead of embracing challenging problems, most senior members tend to avoid them and delegate without proper guidance. The company clearly needs more experienced professionals who have spent years in the industry and understand both technical depth and organizational growth.