Senior Software Engineer, Technical Leadership / Platform (Remote)

Role Overview<p>This is a <strong>Senior Software Engineer </strong>role with a Technical Leadership / Platform specialization, focused on system design, reliability, and long-term platform evolution. You will help the team understand how our systems should behave under load, during failures, and as they scale, ensuring the platform foundation remains healthy over time. The role involves a significant architectural focus (30-50%) while remaining fully hands-on: you take ownership of the most complex or high-risk backend work, and act as the technical representative for API/SDK integrations with third-party vendors and clients, during and after the integration.</p>Key Responsibilities<ul><li>Design and evolve core platform services, focusing on reliability, data integrity, and clear service boundaries aligned with business requirements</li><li>Identify architectural risks, scalability limits, and weak points before they become production issues; recognize when existing tools (queues, storage, frameworks) reach their limits and propose pragmatic, incremental improvement or migration paths</li><li>Own the technical relationship with partners as the primary technical point of contact: lead solution reviews, troubleshooting, and roadmap alignment; document technical decisions and integration details; ensure partners understand expectations, timelines, and constraints</li><li>Design and improve reliability mechanisms: retries and backoff, timeouts and idempotency, handling of partial failures, degraded and fallback modes</li><li>Drive improvements in observability (metrics, logs, tracing, operational visibility) and participate in production incident analysis</li><li>Contribute during the Discovery stage of projects: build PoCs, validate ideas, analyze third-party vendor APIs and proposed integration flows</li><li>Implement the most complex and high-risk backend components using TypeScript and Node.js, owning correctness under partial failure scenarios</li><li>Raise the overall technical maturity of the team, including senior engineers: thoughtful code reviews, decomposition of large or ambiguous problems, knowledge sharing through pairing and documentation</li></ul>Required Qualifications<ul><li>6+ years of professional backend development experience</li><li>Deep hands-on experience building and operating crypto infrastructure: custody, wallets, exchange, payment, or settlement systems. You have designed and run production systems that move real funds. Integrating a crypto API into an existing product, or building UI on top of one, does not meet this bar</li><li>Strong backend expertise in TypeScript and Node.js</li><li>Deep experience in distributed system design: microservices architecture, service boundaries and data models, REST APIs and API contracts, queues and asynchronous communication</li><li>Hands-on production experience: incident response, debugging, API failures, data issues</li><li>Experience owning services end-to-end, from design to production support</li><li>Excellent knowledge of SQL (PostgreSQL) and understanding of other storage types</li><li>Strong reliability mindset and experience with failure scenarios; experience improving observability and investigating production incidents</li><li>Proficient daily use of AI coding tools (e.g. Claude Code, Copilot), with the ability to review AI-generated code quickly and critically</li><li>Ability to mentor engineers, including senior-level, and to evaluate trade-offs and propose practical solutions</li><li>High agency: you treat problems in your scope as yours by default, act before being asked, and escalate with a proposed plan when a decision is above your level</li><li>Excellent communication skills, with the ability to bridge technical and business conversations; strong written and verbal English</li></ul>Preferred Experience<ul><li>Experience leading architecture work across timezones in a distributed team</li><li>Experience in regulated financial environments (licensing, audits, compliance-driven engineering requirements)</li><li>Experience with queues and event-driven systems (Kafka, RabbitMQ, SQS, etc.)</li><li>Redis or other in-memory data stores</li><li>Familiarity with Docker, Kubernetes, and AWS (user-level understanding)</li><li>Experience shaping team practices around AI-assisted development</li></ul>Reporting Structure<p>Reports to the Engineering Manager. This role does not include direct people management, only technical influence.</p>Why This Role<ul><li>Own the technical foundation of a crypto payment platform being built now: architecture decisions you make will define the platform for years</li><li>Full technical ownership of the highest-risk, highest-impact work in the company, with direct influence on how the whole engineering organization builds</li><li>AI-first engineering culture where your leverage multiplies through the team</li></ul>Location<p>Remote. USA, Argentina, or Brazil. The role works US business hours (Eastern Time). A minimum of 4 hours of daily overlap with Central European working hours is a requirement.</p>Compensation and Benefits<p>As an independent contractor, you'll enjoy the flexibility to determine how and when you deliver your work, while partnering closely with our team to meet agreed milestones and business objectives. Compensation and engagement terms will be outlined in your contractor agreement.</p><p>Additional Benefits</p><ul><li>Company issued laptop</li><li>Technology Accessories</li><li>Annual In-Person Full-Team Meetup</li></ul>

Back to blog

Other Jobs To Apply

No other job posts for this day.

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...