CareersQuality Engineering

You decide what is safe to ship.

As a CREA-KO quality engineer you own the assurance behind systems that cannot fail quietly. You make correctness demonstrable — verification engineered into delivery, not a checkpoint at the end — so an institution can depend on the system the day it goes live and every day after.

You are the gate a change passes before it reaches an organization’s environment. You work with software and platform engineers whose work you verify, and delivery engineers who carry the result into operation trusting that it holds.

All disciplines

What you own

The evidence a change is safe.

The verification itself
You build the automated and structured verification that proves a system behaves as required across the paths that matter under real load.
The go / no-go call
You decide whether a change carries the evidence to be deployed into an environment an organization runs on.
Assurance across the lifecycle
You own quality past release — into the maintenance, updates and evolution that keep a long-lived system trustworthy for years.
The edges others leave
You hunt the quiet failures and boundary conditions — the last ten percent where consequential systems actually break.

What your work reaches

What your assurance covers.

  • Institutional systems under load

    High-volume, document-heavy operations where correctness has to hold at real scale, not in a demo.

  • The continON platform

    A configurable platform whose flexibility must never become a path for defects to reach production.

  • Controlled release paths

    The governed pipelines where your verification is the gate every change passes.

  • Support, maintenance & evolution

    Assurance that continues as systems are updated and modernized long after first delivery.

What excellence looks like

The relentless finisher.

Evidence, not opinion
The best work makes a release trusted because it can be shown to be safe — demonstrable, never asserted.
The last ten percent
Excellence is closing the edge cases and quiet failures others walk past — the part that decides whether a system is truly dependable.
Mastery of what fails
Over time you develop an instinct for where consequential systems break — and become the assurance an organization relies on to sleep.