This is a software job, not a trading job
Jcom Technologies builds a white-label Forex and CFD trading platform: a trading panel, a personal cabinet, an admin and CRM back office, market-data distribution, and the deployment machinery that puts a branded copy of all of it in front of each licensee brokerage.
So the work is platform engineering. We do not run a dealing desk, we do not have a sales floor calling clients, and we do not hire traders, analysts or account managers, because we do not have any accounts. If you are looking for a job at a brokerage, this is not one.
We do not publish a vacancy list. We read open applications continuously and we get in touch when what you do lines up with what we need. That is honest and it is how the team has actually grown.
What you would actually be building
The product is one shared engine with many branded deployments on top of it. That shape decides most of the interesting problems.
On the engine side: order handling, account and margin state, an audit trail that has to be trustworthy because money decisions are made against it, and a market-data path that fans one upstream feed out to every deployment without drifting. On the surface side: a trading panel that has to stay readable and quick while prices move under it, a personal cabinet that a nervous first-time client can navigate, and a back office that a broker's staff live inside for eight hours a day.
And around all of it: configuration rather than forks. When a licensee wants different leverage caps, a different instrument list, a different palette and a different domain, none of that should require a branch of the engine. Keeping that boundary clean is a large part of the job.
Disciplines we hire
We hire against these areas rather than against a fixed list of open roles. If your work fits one of them, write to us even if nothing is advertised.
Platform and backend engineering
The engine: services, data model, order and account state, margin, the audit trail, and the APIs the panel and the back office run on. Node and TypeScript, a relational database, and a healthy suspicion of clever code near money.
Frontend engineering
The trading panel, the personal cabinet and the admin back office. Real-time data, charts, dense tables, forms that people fill in under pressure. React and TypeScript, and an eye for the difference between a screen that works and a screen that is usable.
Infrastructure and reliability
Deployments, environment separation per licensee, monitoring, backups, incident response, and the boring discipline that keeps a market-hours system up during market hours.
Quality assurance
Automated and exploratory testing across the trading, cabinet and back-office surfaces. Regressions in a margin calculation are not a cosmetic problem, and the job is to find them before a licensee does.
Product and design
Deciding what gets built and what it looks like: the design system, the flows, and the difficult work of making one platform feel like a different product under each brand.
Delivery and client onboarding
Taking a signed licensee from nothing to live: configuration, branding, environment setup, training the broker's staff on the back office, and staying with them through the first weeks.
Support
Second-line support for licensees. Reproducing what a broker's staff reported, telling a real bug apart from a misconfiguration, and writing the ticket an engineer can act on.
How the team works
- Small team. You will own something, and there is nobody to hide behind, which most people find is the good news.
- Based in Nicosia, Cyprus, and remote-friendly. Overlap with Cyprus hours matters more to us than a postcode.
- The engine is shared across every licensee, so a change you make lands in every deployment. That is a strong argument for care, and it is why review and testing are not optional here.
- We write things down. Decisions, incidents and the reason a thing is the way it is, so the next person is not guessing.
- We work directly with the brokers who use the platform. Nobody on the team is more than one conversation away from a real user.
How to apply
There is no form and no portal. A short, specific email is genuinely the best thing you can send us.
- 1
Write to support@jcomtechnologies.com
Put the discipline in the subject line, for example "Frontend engineering" or "Delivery and client onboarding". If none of them quite fit you, say what you do and let us judge.
- 2
Attach a CV, and add a short note
A few paragraphs, not a cover letter. What you have built, what part of it was actually yours, and why this problem interests you. Links to code, a product you shipped or work you can show are worth more than adjectives.
- 3
A first conversation
A call about your background and about what we are building, so both sides can work out quickly whether there is a fit. We will tell you plainly what the role would involve.
- 4
A practical stage
For technical roles, something concrete: a discussion of your own work in depth, or an exercise close to the real problem. We do not use trick puzzles, and we do not ask for large amounts of unpaid work.
- 5
Meeting the team and a decision
A conversation with the people you would work with, then an answer either way. If it is a no, we will say so rather than go quiet.
What we will not pretend
We are not going to invent a benefits list, a headcount, or a page of open vacancies to look larger than we are. What we can tell you is what we build, who we build it for, and that an application sent to support@jcomtechnologies.com is read by a person. Anything about compensation, contract and terms is discussed openly in the first conversation.
Where to next
About Us
What the platform is, who licenses it, and where the software ends and the brokerage begins.
Contact Us
The other channels: sales, licensee support, partnerships, press and legal.
Compliance and Oversight
Why a technology vendor is not a regulated financial firm, and what that means in practice.