System Analyst

Chrona agency•New Castle, VA

1d•Remote

About The Position

System Analyst RemiDe is a managed routing and compliance layer for licensed financial institutions-think "SWIFT for stablecoins". Built for banks, PSPs, exchanges, and licensed wallets. We create a global address book with RemiTags (an IBAN alternative for wallet strings), making it cross-chain, cross-stablecoin, and Travel Rule interoperable. We are centralized by design. Not a bridge or DEX. Audited controls and strict SLAs. Backbone for the new world of compliant global stablecoin payments. Why this matters now The institutional stablecoin market is rapidly scaling as banks and PSPs move from pilots to production. RemiDe builds the backbone for this shift - routing value across chains and stablecoins with compliance built in: RemiTags for addressing, Travel Rule for data, and audit-ready evidence for regulators. As a System Analyst, youll define how these systems fit together and ensure every rule, field, and flow is unambiguous. The role (what you own) Translate founder intent and corridor strategy into clear, testable specifications and flows that engineers can build and auditors can trust. Scope Starting corridor: USDC (CCTP protocol by Circle) Tron USDT Deterministic, versioned policies with full audit trail. Centralized by design and governance. No yield. Not a bridge. Identity and compliance: RemiTag aliasing + Travel Rule relay (IVMS101). PII remains at endpoints; we store encrypted envelopes only. Vendor-neutral adapters for custody and network rails. Observability and ops: traceable, idempotent APIs with test simulation and runbooks What youll do Functional & regulatory design Define the end-to-end payment flow (intent payout) with retries, errors, and finality. Specify Travel Rule / IVMS-101 relay and storage policy. Write the Policy Engine spec: decision tables, versions, escalation paths. Integration & technical contracts Author specs and adapters for MPC custody, CCTP, and chain listeners. Define Treasury & Liquidity controls: rebalancing triggers, utilization targets, evidence mapping. Developer & ops experience Maintain OpenAPI, error taxonomy, and webhook specs. Set observability baselines: dashboards, runbooks, SLOs 99.9 %.

Requirements

47+ years as System Analyst, Solutions Architect, or Technical BA in payments/fintech/crypto infrastructure or compliance tech.
Shipped multiparty, regulated integrations where auditability and policy controls mattered.
Comfortable drafting OpenAPI, sequence/dataflow diagrams, and specifying decision/policy engines.
Practical understanding of eventdriven systems, retries/backoff, idempotency, and webhooks.
Documentation craft that engineers ship from and auditors accept.
You can describe complex payment logic in plain language and diagram it so both engineers and compliance teams agree

Nice To Haves

Treasury netting/rebalancing, routing algorithms, fee/FX inputs.
Familiarity with IVMS101, MiCA context, AML/KYT vendors.
EVM basics, custody/MPC, and ledgering models.
SQL for validation queries; comfort with Postman/Swagger.
Observability and SLO design.

Responsibilities

Define the end-to-end payment flow (intent payout) with retries, errors, and finality.
Specify Travel Rule / IVMS-101 relay and storage policy.
Write the Policy Engine spec: decision tables, versions, escalation paths.
Author specs and adapters for MPC custody, CCTP, and chain listeners.
Define Treasury & Liquidity controls: rebalancing triggers, utilization targets, evidence mapping.
Maintain OpenAPI, error taxonomy, and webhook specs.
Set observability baselines: dashboards, runbooks, SLOs 99.9 %.