About Decibel:

Decibel is an exchange where equities, real world assets, commodities, indices and crypto trade around the clock, weekends included, all from one margin account. Matching, margin and liquidation happen onchain, so a trader can check our numbers instead of taking our word for them.

We launched in February 2026 and crossed $5B in cumulative volume in July. We are not building only for crypto natives. We are building for people who already trade equities and commodities and have never touched a wallet, and for anyone who wants access to more financial products, in more hours, than their current venue offers.

The team is small, scrappy and ambitious, and it runs financial infrastructure that does not close. Markets are open 24/7/365 and so is the venue, which means the team operates the same way: someone is always awake, releases go out on the day they are ready rather than on a Thursday, and the person who finds a problem is usually the person who chases it down. Many functions here are being built by the first person hired into them.

Less structure, more ownership, and your work reaching real traders within days.

About the role:

This is our first QA hire in Medellín. Release testing and live system monitoring already run across our Asia and Europe teams. You extend that into the Americas and bring a product focus to it: sitting with the product before release, in Bogotá hours, alongside engineering and product, deciding what to test and why.

The role has two halves.

You are the product's most active user. You are in the app every day with live positions, on desktop and on a phone, across equities, commodities and crypto, in market hours and at 3am when Seoul is open. You know what the funding rate did last night. You know which market has the widest spread right now. You use the product more thoroughly than anyone else on the team, and that is what makes your reports worth reading.

You are the person who finds out why. When something is wrong, you do not stop at the screenshot. You open devtools, check the WebSocket messages, read the API response, look at the logs, query the data, and work out whether the number is wrong, the feed is stale, or the UI is rendering a correct number badly. Then you write the ticket, with reproduction steps, evidence, and a clear read on who it affects and how much.

Our engineers are senior and they ship fast. What they need is a ticket they can start on without coming back to ask a question.

Because you are the first in this seat locally, you will also shape how QA works here as the team grows: what gets tested before every release, what the regression suite covers,



how a bug moves from report to fix to verification. That is scope you will define rather than inherit.

What you will own:

- Release quality. Every release gets reviewed by you before it reaches traders. You decide what needs testing based on what would actually hurt if it broke, not based on a checklist. You have the standing to say a release is not ready, and we expect you to use it.
- The trading surfaces. Order placement and cancellation, partial fills, reduce-only, leverage changes, margin and collateral behaviour across positions, liquidation and auto-deleveraging, funding, fees, and whether the PnL on the screen matches the PnL in the ledger. These are the places where being wrong costs a trader money, so they get the most of your attention.
- The money-movement paths. Deposits, withdrawals, onboarding, and funding an account for the first time. Our standing target is fiat to first trade in under fifteen minutes. You run that path repeatedly, on a real phone, on a bad connection, and tell us where it can be better.
- Real-time correctness. Market data, WebSocket feeds, charts, the position list, balances. Stale data, feeds that reconnect wrong, numbers that disagree between two screens, values that are right on refresh and wrong on update. This is where the most interesting bugs live, and the hardest to catch with a script.
- The mobile and browser matrix. iOS and Android, Safari and Chrome, small screens, and the wallet and onramp flows that behave differently on each.
- Bug intake, end to end. How a problem gets from a trader in Telegram or a support message into a Linear ticket that gets fixed. Triage, reproduction, severity, dedupe, chasing the fix, and verifying it in production afterwards, working alongside our QA lead in Asia so coverage follows the sun.
- The QA practice. A regression suite for the paths that must never break. A defined release check. A written bug template. A monthly read on what broke, what class of thing it was, and what to change upstream. You define these, and you build them to work across three timezones.

What we are looking for:

- 3 to 5 years in QA, product quality, or a technical support or trading operations role where finding and diagnosing product problems was the job
- A background in a real-money product. Trading, brokerage, CFDs,



prop firms, payments, neobanking, lending, or real-money iGaming. You know what a production incident feels like when users' money is involved
- Technical literacy to look under the hood. Comfortable in browser devtools and the network tab, reading logs, calling an API by hand in Postman or similar, and writing SQL well enough to check a number against the data. You can read a codebase to work out what a feature is supposed to do, even if you would not write the fix yourself
- You write bug reports an engineer can act on immediately. Reproduction steps, expected against vigente, evidence attached, scope and impact stated
- You read specs and designs critically and find the gap before the code is written, not after
- You work without being handed a plan. Given a new feature and no test cases, you explore it, read the docs, ask the right questions and decide what is worth testing
- Comfort with leverage, margin, funding, spreads and fees. You can explain how a liquidation happens and roughly how an exchange makes money
- Fluent working English, written and spoken, B2 or above. Specs, tickets and all conversation happen in English
- Based in Medellín, and available four days a week in the Milla de Oro office

Nice to have:

- Experience in iGaming, sportsbook or casino QA. Real-money edge cases, 24/7 production, a large device matrix, go-live support as a normal duty, and the habit of checking whether the maths of a product pays out what it claims. Funding rate and liquidation maths is the same instinct pointed at a different product
- Ability to read Rust well enough to follow what a service is doing. Our trading API and indexer are written in it. You do not need to write it
- Practical use of AI coding tools, Claude Code in particular, to read unfamiliar code, reproduce an issue, or write a quick script that checks a number. This is how the rest of the team works, and it is the difference between testing the surface and going a layer deeper
- Experience with crypto, wallets or onchain products. Not required. If you have never opened a wallet, say so in your application. We will teach you the parts that matter

Compensation

COP 6,000,000 to 8,000,000 per month, depending on experience and the depth of domain knowledge you bring. The top of the band is for someone who arrives with real product depth plus demonstrated ability to read code and use AI tooling to go a layer deeper.

Markets never close, but this is not an on-call role. Normal Colombian business hours, with occasional evening overlap around a release or an incident.

We move quickly on strong candidates.

📌 QA / Product Quality Analyst (Medellín)
🏢 Decibel
📍 Medellín