QA Engineer

Andersen is a global software development company with over 18 years of experience supporting businesses worldwide in their digital transformation. Headquartered in Poland, it operates development centers across Germany, the USA, the UK, Lithuania, Hungary, Kazakhstan, Georgia, Azerbaijan, Cyprus, and the UAE. It offers end-to-end IT services including custom software development, API integration, system architecture, legacy modernization, and long-term support. Andersen harnesses AI, Machine Learning, Data Science, Big Data, and Visual Technologies to create tailored digital products. It serves industries such as Healthcare, FinTech, Logistics, Automotive, Manufacturing, E-commerce, Multimedia & Entertainment, among others, with a team of 3,700+ experts across 16+ global locations.

• Experience as a QA Engineer in Game Development for 4+ years.
• Hands-on experience with the Unity Editor, including navigating scenes, hierarchy, GameObjects, Transforms, Layers/Tags, and Prefabs.
• Experience with level/map testing specifically: object placement QA, collision/geometry verification, lighting checks in 2D or 3D.
• Ability to work from design documentation and content specs to translate into concrete test scenarios.
• English language skills at intermediate level or above.

Nice-to-haves:

• Experience with mobile performance profiling: FPS, memory, CPU load, battery drain, and analyzing raw profiler output.

• Build and run test sessions from the Unity Editor: assemble builds, execute scenarios, capture logs and performance data.
• Verify object placement against design references, check lighting/rendering correctness, memory usage, prop behavior, and geometry gaps between map blocks.
• Verify traversability of levels/maps, identifying non-traversable areas, geometric holes, and navigation issues.
• Run performance testing across the agreed device matrix: Avg FPS, 1% Low FPS, Memory Peak, CPU Load, Battery Drain.
• Produce performance dashboards and raw profiler logs for engineering analysis.
• Support playtest sessions and feature acceptance requiring engine-level or map-specific expertise.
• Re-test performance and map fixes after they are addressed by the development team.
• Document briefing packs to onboard testers on specific map tasks over time.