GoMining is hiring a Software Fraud Engineer — Cyprus / Georgia / Latvia / Serbia / Poland / Spain. The overview below is synthesized from the employer posting on apply.workable.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
The listing frames the Software Fraud Engineer at GoMining as a hands-on product role. You'll develop real-time fraud detection systems, risk engines, and automated decision-making services that protect both our users and business.
This is an engineering role focused on building fraud prevention systems — not a manual fraud operations position.
Responsibilities
Day-to-day scope for the Software Fraud Engineer as described in the posting:
Fraud Detection
- Design and develop fraud detection systems for payments, wallets, authentication, and user activity.
- Detect account takeover, payment fraud, bonus abuse, multi-accounting, and other abuse scenarios.
- Build real-time fraud pipelines and event processing systems.
- Develop automated fraud prevention mechanisms.
Risk Engine
- Build and improve fraud rules, velocity controls, and dynamic risk scoring.
- Design decision engines for transaction approval, review, or rejection.
- Continuously optimize fraud detection accuracy while minimizing false positives.
- Improve fraud models using behavioral and transactional data.
Data & Analytics
- Analyze transaction patterns, user behavior, device intelligence, and risk signals.
- Work with large-scale event streams and transactional datasets.
- Create internal investigation and monitoring tools for Fraud, Support, and Compliance teams.
- Investigate emerging fraud patterns and rapidly deploy countermeasures.
Engineering
- Develop scalable backend services supporting fraud prevention.
- Build APIs and internal tooling for risk evaluation.
- Optimize latency for real-time fraud decisions.
- Collaborate closely with Product, Payments, Data, and Platform teams.
- 4+ years of software engineering experience.
- Experience building fraud prevention, risk, payment, banking, fintech, or security systems.
- Strong backend development experience (Go, Java, Kotlin, Python, or similar).
- Experience working with distributed systems and event-driven architectures.
- Strong SQL skills and experience with large datasets.
- Understanding of payment flows, authentication, and transactional systems.
- Experience designing real-time decision engines.
- Strong analytical and problem-solving skills.
- Fluent English.
Nice to have
Additional experience noted as a plus:
- Experience in crypto, Web3, or blockchain.
- Experience with Kafka, ClickHouse, Redis, Elasticsearch, or similar technologies.
- Experience with machine learning models for fraud detection.
- Knowledge of AML, KYC, or payment risk systems.
- Experience with device fingerprinting, behavioral analytics, or identity verification.
- Professional growth: support for courses, conferences, and English learning (up to 100% coverage).
- Work-life fit: remote or hybrid format with flexible hours across international teams.
- Paid leave: up to 20 vacation days + 8 company holidays + 5 personal days per year
- Recognition programs: structured performance reviews and team awards.
- Team culture: retreats in international locations (for example, company apartments in Cyprus).
Build a standout application
For the Software Fraud Engineer at GoMining, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.