Skip to content
NewThe live risk and unusual-trading desk for MT5 brokers
GarnetSync

Careers

Work with us.

There are no openings listed here, because we don't list roles we aren't hiring for. GarnetSync is built by people who run a brokerage, and we'd like to hear from people who know the work: MT5, payments, compliance and product engineering.

How we build

Every release goes through the same six steps.

The discipline is most of the job. This is what happens to every change before a brokerage sees it, whether it is a new screen or one line.

  1. 1

    A branch and its tests

    Branch

    Each change is built on its own branch, with the tests that prove what it claims.

  2. 2

    The whole API suite

    510 tests

    510 tests, every one of them, not only the files the change touched.

  3. 3

    Mutants

    Broken on purpose

    The safeguards get deliberately broken copies. If a test still passes against one, the test is wrong, and it is fixed first.

  4. 4

    Eight walks in a real Chrome

    744 checks

    The CRM and the client portal clicked through end to end, including phone widths and the dark theme: 744 checks.

  5. 5

    Written up

    Release notes

    What changed, how it was verified and how to roll it back, in the release notes.

  6. 6

    Approved, then shipped

    Snapshot first

    A snapshot of the production database, then the release, and only when a person approves it.

Before you write

See what you'd work on.

The company page, the blog and the notes for MT5 administrators say how GarnetSync works, and how we think about it.