Artem Samundzhyan
Trading Technology
Remote · CET overlap · Available nowOpen to relocate: Europe / NetherlandsExecution + Risk + DeliveryAlgo/DMA experience (NDA)

Trading Technology leader who turns chaos into shipping.

I help exchanges, brokers, and prop teams stabilise production and ship prop-grade capabilities: execution flows, real-time risk controls, and fast trader UX. Selected work includes a prop trading terminal used in a high-stakes environment, complex venue connectors, and API collaboration with BitMart (details under NDA). I’m remote-first now and open to relocating to Europe — including the Netherlands — for the right role.

Email meLinkedInPortfolio
Fast response · CET overlapNDA-friendlyRemote-first
22k
Active users reached
Trading API platform (crypto + equities).
Up to 12
Team led
Hiring, performance, and delivery ownership.
3
Trading surfaces
2 desktop terminals + 1 web terminal (plus risk tooling).
10+ yrs
Domain depth
Fintech / exchange stack / prop trading technology.
Focus

What I own

I’m strongest when you need an owner for a critical stream — not a narrow task executor.

Execution (DMA/FIX patterns)
Order lifecycle, safe state handling, latency-sensitive pipelines, production discipline.
Algorithmic trading systems
Complex automation in real markets, guardrails, safe deployment, incident-ready operations.
Real-time risk controls
Limits, exposure monitoring, kill-switch workflows, operational safety and playbooks.
Pro trader UX
DOM/ladder workflows, hotkeys, positions & risk panels, high-speed interaction design.
Leadership & turnarounds
Unblock teams, restore cadence, resolve crises, make tough hiring/firing calls when needed.
Turnarounds

How I pull projects back on track

When things break (incidents, delivery problems, unclear ownership), I bring structure, measurable controls, and a shipping rhythm.

Incidents / market spikes
Stabilize production under volatility
  • Tighten limits and kill-switch paths so failures become safe.
  • Add observability and runbooks so incidents stop being ‘mystical’.
  • Make the execution chain measurable: latency, rejects, risk blocks.
When execution stalls
Get a team back into delivery mode
  • Clarify ownership, remove blockers, reset priorities to measurable outcomes.
  • Handle tough people decisions fast and respectfully.
  • Turn chaos into a cadence: milestones, risk list, release discipline.
Execution / risk / UI
Ship complex trading modules safely
  • Break big work into shippable slices — without breaking trading safety.
  • Design internal APIs so product speed doesn’t kill reliability.
  • Deliver production-ready features, not demos.
72-hour turnarounds

When it’s on fire, I make it controllable — fast

Two examples of what I do in the first 72 hours to stop chaos and restore delivery.

72-hour turnaround: from firefighting to control
Problem
Production instability under market spikes: unclear ownership, noisy alerts, recurring incident patterns affecting trading workflows.
What I did
  • Took ownership of incident response and set a single decision-maker loop.
  • Mapped the market data → orders → risk → venue chain and made failures measurable (latency, rejects, risk blocks).
  • Introduced a minimal runbook: top failure modes, safe fallback actions, escalation rules.
  • Prioritized fixes with maximum stability impact (guardrails + observability, not big refactors).
Result
  • Incidents became predictable and faster to resolve.
  • Team switched from chaos to a weekly shipping cadence.
  • Clearer risk/safety posture under volatility.
Deeper metrics and diagrams available under NDA.
72-hour turnaround: execution chain hardened
Problem
High-stakes trading where edge cases (rejects, partial fills, disconnects, throttling) created operational risk and unpredictable behaviour.
What I did
  • Audited the order lifecycle end-to-end and defined explicit states + reconciliation rules.
  • Added safety gates: limits/exposure checks + an operational kill-switch path.
  • Implemented recovery-first connector behaviour: retries, idempotency patterns, state re-sync after reconnect.
  • Set a production checklist for releases in a latency-sensitive environment.
Result
  • More predictable execution behaviour under stress.
  • Reduced operational surprises and faster recovery when venues misbehave.
  • Safer automation without sacrificing speed.
Venue/strategy details discussed under NDA.
Proof

Selected case studies (high-level, NDA-friendly)

I keep public details intentionally high-level. On a call, I can share deeper metrics under NDA.

High-load trading API platform (crypto + equities)
Led delivery of a production trading API product used by ~22k active users.
Situation
The platform had to stay reliable under bursty market conditions while supporting fast order workflows and integrations.
What I owned
  • Owned architecture decisions across execution flows and trading safety.
  • Improved reliability/monitoring so issues were detectable early.
  • Delivered features in production cadence while managing a growing team.
Outcome
  • Stable high-load operation for active trading workflows.
  • Clear ownership and delivery rhythm for the engineering team.
Trading APIsHigh-loadExecutionReliability
Company / exact details available under NDA.
Prop trading terminal + risk workflows (significant exposure)
Owned execution and risk-oriented workflows for a prop trading terminal used in a high-stakes environment.
Situation
Traders needed extremely fast interaction (orders, hotkeys, positions) while keeping strict limits and operational controls.
What I owned
  • Owned execution workflow design (order lifecycle, states, safety gates).
  • Designed risk-focused UX: limits, exposure view, emergency actions.
  • Introduced incident-oriented discipline: monitoring, runbooks, measurable behaviour.
Outcome
  • Faster trader workflows without sacrificing risk controls.
  • More predictable production operations under stress.
Prop tradingExecutionRisk controlsTrader UX
Details (venues/notional/latency) discussed under NDA.
Complex venue connectors + API collaboration (BitMart)
Built and hardened integrations for real-world exchange behaviour and collaborated with BitMart on API/integration needs.
Situation
Connectivity failures in production are expensive: disconnects, throttling, inconsistent edge cases, rejects/partials.
What I owned
  • Designed connector architecture (market data + order routing) with recovery paths.
  • Hardened lifecycle handling (idempotency patterns, retries, state reconciliation).
  • Closed the feedback loop between real trading usage and API behaviour (NDA-safe summary).
Outcome
  • Fewer production surprises; faster incident resolution.
  • Clearer integration behaviour under load and volatility.
ConnectorsExecutionResilienceBitMart
Scope and artifacts are discussed under NDA.
Engagement

Remote-first — designed for speed

Open to remote full-time and contracts. Clear ownership, fast feedback loops, production discipline.

Remote full-time
Remote · CET overlap · available now
  • Own a critical stream: execution, risk controls, or venue connectivity.
  • Work directly with CTO / Head of Trading Tech.
  • Operate like an internal owner: delivery, reliability, accountability.
Contact
Remote contract (6–12 months)
When you need an owner fast (incl. 12-month term)
  • Take responsibility for architecture + delivery + crisis response.
  • Stabilize production and restore release discipline.
  • Unblock the team and ship production-ready improvements.
  • A 12-month contract term is absolutely fine.
Contact
Architecture / turnaround advisory
1–2 week assessment
  • Execution/risk review + measurable action plan.
  • Observability + incident playbook.
  • Roadmap for ‘active trader’ capabilities.
Contact
What I can own
Pick one stream. I take ownership and drive it to stable production.
Risk controls
Limits, exposure, kill-switch flows, operational safety.
Trader UX
Fast order flows, hotkeys, DOM/ladder workflows.
Execution chain
Order lifecycle, reliability, latency map, correctness.
Observability & incidents
Dashboards, alerts, runbooks, incident response discipline.
FAQ
Are you available to start now?
Yes — I’m currently available and can start immediately (remote).
Employee or contractor?
Either. The best format depends on your needs and timeline.
Time zone overlap with NL?
I overlap with CET daily. Short feedback loops are a priority.
Can you share exact venues/strategy details?
Only under NDA. The public page stays intentionally high-level to respect confidentiality.
Contact

Direct contacts

No forms. Telegram is best for a fast reply.

Reach out
If you're reaching out about a role: share the team size, trading surface (exchange/broker/prop), and what’s currently painful (execution, risk, reliability, or trader UX). I reply fast.
Email
algofinteh@gmail.com
Open
LinkedIn
https://www.linkedin.com/in/samujan
Open
Telegram
asamujan
Open
Quick note template
Hi Artem — we’re building <exchange/broker/prop>. The pain is <execution/risk/reliability/UX>. We need an owner for <stream>. Are you open to remote full-time / contract?
UTC+4 · CET overlap daily · NDA-friendly