1st month Review - AI Research Engineer QLU Employee Review

5.0
29 Aug 2025
Recommend
CEO approval
Business outlook

Pros

Amazing Environment: Respectful, Comfortable, Enjoyable. Working on New technologies giving freshers a chance to boost their skills and career growth. They focus on delivering work rather than being fancy.

Cons

Sometimes Work Load and Pressure can take your peace your away but the best thing is, you will never feel you are not compensated, or your efforts are overlooked.

Explore other reviews about QLU

3.0
30 Aug 2025
Recommend
CEO approval
Business outlook

Pros

-Good Salary -Quarterly increments -unlimited leaves

Cons

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.

2
1.0
30 Aug 2025
Recommend
CEO approval
Business outlook

Pros

Good salary quarterly increment don't know

Cons

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.

11
See reviews by: Helpful|Rating|Date|All