Quidax

• Design, build, and operate backend services for Quidax platform • Shape technical direction, mentor engineers, and improve engineering practices • Deliver production-ready backend features independently • Lead design and implementation of complex backend systems • Drive improvements to engineering quality, maintainability, and developer experience

• Know the platform, and the people who use it • First 90 days: get deep on the API. Make test calls, read the docs like a merchant would, and find every spot where integration hurts. • Sit with our biggest merchants. Learn why they use us. Map the full journey, from first API call to first live transaction, and mark where people drop off. • Own the roadmap for the API • Make the calls on what we build, what we kill, and what we say no to (kindly). • Own pricing and packaging too. Price it so merchants win and so do we. • Ship it, and keep it boringly reliable • Run delivery with Engineering using rituals that stick: sprints, retros, the good stuff. • Grow the number of live merchants and the volume flowing through the API, and have the numbers to back it up. • Hold the line on uptime, security, and compliance. • Merchants move their customers' money through us. "Mostly works" isn't a thing. • Make integration super simple (the Enablement bit) • Cut time-to-first-transaction. The faster a merchant goes live, the better the product. • Build docs, sandboxes, and support materials so good that merchants barely need to email us. • Give Sales, Solutions, and Support what they need to win deals and keep merchants happy.

• Know the platform, and the people who use it • First 90 days: get deep on the API. Make test calls, read the docs like a merchant would, and find every spot where integration hurts. • Sit with our biggest merchants. Learn why they use us. • Map the full journey, from first API call to first live transaction, and mark where people drop off. • Own the roadmap for the API • Make the calls on what we build, what we kill, and what we say no to (kindly). • Own pricing and packaging too. • Price it so merchants win and so do we. • Ship it, and keep it boringly reliable • Run delivery with Engineering using rituals that stick: sprints, retros, the good stuff. • Grow the number of live merchants and the volume flowing through the API, and have the numbers to back it up. • Hold the line on uptime, security, and compliance. • Merchants move their customers' money through us. "Mostly works" isn't a thing. • Make integration super simple (the Enablement bit) • Cut time-to-first-transaction. • The faster a merchant goes live, the better the product. • Build docs, sandboxes, and support materials so good that merchants barely need to email us. • Give Sales, Solutions, and Support what they need to win deals and keep merchants happy.

• Know the platform, and the people who use it • Own the roadmap for the API • Ship it, and keep it boringly reliable • Grow the number of live merchants and the volume flowing through the API, and have the numbers to back it up. • Make integration super simple (the Enablement bit)

• Own customer issues across fiat and crypto transactions from first contact to resolution, ensuring customers get timely, accurate, and empathetic support. • Handle account, transaction, verification and product related queries while meeting agreed SLA and quality expectations. • Track recurring customer pain points, onboarding drop-offs, inactivity patterns and repeat complaints that may signal churn or low engagement. • Contribute to customer health and retention reporting by turning support interactions and behavioural patterns into useful insights. • Surface bugs, transaction failures, recurring complaints, and operational gaps quickly and clearly to the right internal teams. • Work closely with Product, Engineering and Compliance to investigate customer-impacting issues and move them to resolution. • Contribute to improvements in workflows, support content, SOPs and internal documentation based on recurring customer friction.

• Know the platform, and the people who use it • First 90 days: get deep on the API. Make test calls, read the docs like a merchant would, and find every spot where integration hurts. • Sit with our biggest merchants. Learn why they use us. • Map the full journey, from first API call to first live transaction, and mark where people drop off. • Own the roadmap for the API • Make the calls on what we build, what we kill, and what we say no to (kindly). • Own pricing and packaging too. Price it so merchants win and so do we. • Ship it, and keep it boringly reliable • Run delivery with Engineering using rituals that stick: sprints, retros, the good stuff. • Grow the number of live merchants and the volume flowing through the API, and have the numbers to back it up. • Hold the line on uptime, security, and compliance. Merchants move their customers' money through us. "Mostly works" isn't a thing. • Make integration super simple (the Enablement bit) • Cut time-to-first-transaction. The faster a merchant goes live, the better the product. • Build docs, sandboxes, and support materials so good that merchants barely need to email us. • Give Sales, Solutions, and Support what they need to win deals and keep merchants happy.

• Get across the core Java/Spring Boot services, understand the critical flows, and ship your first meaningful fix. • Own specific features or services end to end, with support from the team where needed. • Independently investigate and resolve reliability issues across APIs, integrations, and transaction flows. • Reduce recurring issues: stuck transactions, failed callbacks, unclear states, and manual escalations. • Improve test coverage across critical flows and leave every area you touch cleaner than you found it. • Add observability where it's weak: better logging, alerts, and debugging hooks. • Participate in code reviews, share what you learn, and support engineers around you. • Grow your understanding of transaction heavy systems: idempotency, retries, state machines, and reconciliation.

• Join a focused team working on the flows that matter most: deposits, withdrawals, partner integrations, and reconciliation. • Get across the RAMP codebase, understand the core flows, and ship your first meaningful fix in the first 30 days. • Own specific features or flows end-to-end by month 3, with support from the team where needed. • Independently investigate and resolve reliability issues across deposits, withdrawals, and partner callbacks by month 6. • Reduce recurring issues: stuck transactions, failed callbacks, unclear states, and manual escalations. • Improve test coverage across critical flows and leave every area you touch cleaner than you found it. • Add observability where it's weak: better logging, alerts, and debugging hooks. • Participate in code reviews, share what you learn, and support engineers around you. • Grow your understanding of transaction-heavy systems: idempotency, retries, state machines, and reconciliation.

• Designing full user journeys, wireframes, and high-fidelity interfaces for your dedicated product area (e.g., Payments, Onboarding). • Planning, executing, and synthesizing usability studies and user interviews to validate your specific feature designs. • Creating detailed developer handoff files and performing "design QA" on builds to ensure the final product matches the intent. • Actively identifying gaps in our component library and proposing new patterns to the Design System Lead.

• Security Solutions Configuration, Review & Optimization • Within 30 days, the Infrastructure Security Engineer should be able to carry out configuration of various security solutions including network firewalls, Endpoint Detection & Response Solutions, Web Application Firewalls, Cloud Native Application Protection Platforms, Security Incident and Event Management, Security Orchestration Automation and Response Solutions, Identity Provider Solutions and Threat Management Solutions among others • Within 90 days, the Infrastructure Security Engineer should be able to carry out reviews & optimizations on various security solutions in compliance with the established policies • Within 180 days, the Infrastructure Security Engineer should review current security baselines & ensure alignment of all security and technology solutions with the security baselines across all environments (cloud, endpoints, network) • Audits & Compliance Reviews • Within 90 days, the Infrastructure Security Engineer should have adequate understanding of our existing infrastructure security systems and technical controls (how they work, effectiveness & gaps if any) to be able to provide insights during audits & compliance reviews • Within 180 days, the Infrastructure Security Engineer should be able to assume roles within our Information Systems Management framework • Within 180 days, the Infrastructure Security Engineer should be able to work with Governance Risk & Compliance to close audit findings quickly and effectively • Access Control Management & Optimization • Within 30 days, the Infrastructure Security Engineer should have an understanding of our Access Control Policies, Processes & Technologies • Within 30 days, the Infrastructure Security Engineer should be able to take ownership of Access provisioning, decommissioning & access management optimization • Within 90 days, the Infrastructure Security Engineer should have conducted a review of the current access management system, identified gaps and propose recommendations • Vulnerability Management • Within 60 days, establish a consistent vulnerability management process across infrastructure and endpoints • Within 90 days, ensure all critical & high vulnerabilities have clearly defined remediation SLAs • Within 180 days, reduce monthly recurring unremediated vulnerabilities by 40% • Provide clear, actionable vulnerability remediation guidance to Engineering and DevOps teams. • Security Monitoring, Detection & Response • Within 30 days, review and be conversant with existing SIEM architecture • Within 90 days, identify and document all areas of improvement in our security event monitoring • Within 180 days, start implementing all areas of improvement to log aggregation, security event analysis and alerting • Within 90 days, identify new playbooks for automated incident response in the SOAR and document the recommendations • Within 12 months, implement the playbooks for automated incident response recommendations in the SOAR • Continuously improve detection coverage and incident response automation and orchestration across cloud, endpoints, and network layers • Secure Cloud & Network • Within 30 days, review and understand services & configurations across multi-cloud platforms • Within 60 days, be able to administer security policies & security services across multi-cloud platforms • Within 60 days, partner with relevant Engineering teams to ensure security is embedded in infrastructure design and configuration from day one • Security Operations & Automation • Within 30 days, review existing automations, test them out and identify areas of for optimization/improvement • Within 180 days, automate at least 30% of repetitive security operations tasks • Continuously evaluate and implement new tools that improve detection, prevention, or efficiency • Continuously improve security policies and enforcement mechanisms • Cross-Functional Security Enablement • Work closely with Engineering, DevOps, and Product teams to embed security into workflows • Provide hands-on guidance during system design, deployments, and incident response • Promote strong security practices across the company — not just enforce them