ACCEPT01 / 03
Card-present acceptance on phones
Tap2Mobile SoftPOS runs on Android devices used by real merchants. Teams own device telemetry, transaction state, acquirer context, and bank integration boundaries.
CAREERS
Build payment systems that must stay correct
Firisbe teams ship PCI-certified infrastructure for banks, PSPs, acquirers, and fintechs. The work spans card acceptance, orchestration, risk, operations, and evidence, with production ownership from the first quarter.
PRODUCTION CONTEXT
The scale you join is already live
Teams work on regulated payment systems with real throughput, live bank traffic, and audit evidence that has to stand up every year.
M+Transactions per dayAcross live bank and fintech programs
+Tier-1 banks liveTürkiye and selected EMEA markets
%Measured uptimeTracked monthly across production services
PCI certificationsDSS Level 1, MPoC, and Card Production
WORK SURFACES
The problems are concrete
Most work starts from a live payment surface, not a blank canvas. You improve the path from device to acquirer, then make the evidence useful for operators and auditors.
ROUTE02 / 03
Keep acquirer traffic moving
Routing, fallback, provider health, cost rules, and settlement preferences sit in the orchestration layer. A small change can affect authorization quality at production scale.
EVIDENCE03 / 03
Turn incidents into traceable evidence
Support, risk, finance, and compliance use the same logs, dashboards, exports, and audit trails. Engineering work is not done until the operator can explain what happened.
ROLE LANES
Where strong candidates usually fit
We hire around operating boundaries rather than generic departments. If your work touches correctness, uptime, risk, or partner outcomes, there is probably a useful conversation to have.
Backend platform
Authorization flows, ledger-adjacent services, provider integrations, webhook contracts, reconciliation exports, and internal APIs.
Mobile and terminal apps
Android Tap to Phone surfaces, SDK integration quality, merchant app reliability, receipt flows, device signals, and field diagnostics.
Risk and compliance operations
PCI evidence, transaction monitoring, KYC handoffs, access reviews, incident timelines, and audit-ready operating controls.
Partner success engineering
Bank and PSP launches, sandbox enablement, migration planning, production readiness, and technical account ownership.
Reliability and operations
Observability, incident response, capacity planning, release discipline, runbooks, and the boring work that keeps payments moving.
Product systems
Admin surfaces, operator workflows, documentation, internal tools, and the web systems that make complex payment work legible.
WORKING MODEL
Autonomy is paired with production discipline
Firisbe is a small enough team for direct ownership and a regulated enough environment for careful engineering habits to matter.
01
Own a boundary
Teams are accountable for a clear surface, such as SDK state, routing health, reconciliation, support tooling, or audit evidence.
02
Review with operators
Engineers sit close to support, risk, finance, and partner teams so product decisions are tested against real production work.
03
Learn certification deeply
PCI scope, MPoC controls, and QSA evidence are taught through reviews, shadowing, and live procurement conversations.
04
Write for the next incident
Design notes, runbooks, dashboards, and audit trails are treated as part of the feature, not cleanup after launch.
05
Use hybrid deliberately
Maslak office days are for design reviews, launch rooms, incident work, and partner sessions. Focus work can stay quiet.
06
Compensation respects seniority
Offers are calibrated for the Turkish market with private health coverage and equity for roles that carry long-term ownership.
HIRING PROCESS
Four steps, usually two to three weeks
The signal we look for is production judgement: how you debug, make tradeoffs, communicate risk, and leave systems easier to operate.
Scope call
Thirty minutes with the hiring manager to understand your work, the role boundary, and what you want to build next.
Work sample
A practical session around a payment or systems problem. No brainteasers, no whiteboard theatre, no unpaid project week.
Team review
Meet future teammates across engineering, product, or operations. You evaluate the team as much as the team evaluates you.
Offer package
If there is a fit, we send a written offer with salary, equity, benefits, hybrid expectations, and start-date options.
FAQ
Before you email us
Short answers for candidates considering engineering, risk, operations, product, or partner-facing roles.
SEND A SIGNAL
Show us the systems you want to be trusted with
Send a short note, links to relevant work, and the boundary you want to own. A Firisbe hiring manager will route it to the right team.