good working environment - Engineer Complyance Employee Review

I joined as a Backend Developer with Java, and slowly I learned Spring Boot by working on real tasks. After some time, I started fixing bugs and picking backend-related features. Later, I also got the opportunity to work on frontend along with backend, which helped me gain more confidence. This is a good place to upskill if you are really interested in learning. The team gives opportunities to explore different areas, including backend, frontend, and even some DevOps-related work. If you are willing to take ownership, the doors are open to learn and grow. Another good thing is that ideas and suggestions are considered from a product point of view. You can understand the product end-to-end and contribute beyond just your assigned task

Sometimes timelines can be tight, especially when working on new tasks or learning something new while delivering. In those situations, extra effort is needed. Time management is very important when picking up new responsibilities

Working at Complyance gave me real ownership from day one. As the sole QA engineer, I built the entire automation framework from scratch — Playwright + TypeScript, Fixture Object Model, parallel execution across 21 microservices. The domain itself is niche and challenging (ZATCA Phase 2, PEPPOL, PINT, EN16931), so you grow fast technically. The product serves enterprise clients across multiple countries, so the scale and quality bar are genuinely high. Small team means your contributions directly impact the product.

Being the only QA person means you wear a lot of hats. Can get intense during compliance deadline cycles. Work-life balance depends on the sprint.