Senior Software Engineer

Loop3; United States; Remote; USD 100,000 - 134,000; Full time

Benefits offered by this job

Remote-first

Performance bonus

Salary in USD

Flexible schedule

PTO + holidays

MacBook Pro

Tech budget

Learning budget

Career path

High trust

Job summary

Winclap seeks a Senior Software Engineer to own the architecture behind AI dealmaking: real-time signals, agent systems, and a scalable platform. The role is remote-first with Argentina-based teammates and paid in USD.

You’ll work on distributed systems, streaming data, and cloud infrastructure (AWS/Azure/GCP) with hands-on ownership of trade-offs and delivery. Expect a rigorous interview process and competitive compensation.

Qualifications

• 5-7+ years backend with system design ownership.
• Experience in distributed systems and data consistency.
• Ability to turn business requirements into scalable architectures.

Responsibilities

• Own architecture and projects behind AI dealmaking.
• Lead end-to-end system design and trade-offs.
• Collaborate with stakeholders and align roadmaps.

Skills

Backend with system design

Architecture ownership

Stakeholder collaboration

Tools

Node.js

TypeScript

Python

AWS

Azure

GCP

SST

Terraform

LangGraph

LangChain

CrewAI

SageMaker

AI SDK

Mastra

Hermes Agent

OpenAI SDK

Anthropic SDK

OpenRouter

Vercel AI Gateway

Snowflake

Next.js

React

Job description

Engineering Remote · Argentina Paid in USD Full-time

Senior Software Engineer

Someone has to decide how the system is shaped before anyone can build in it. You'd own the architecture behind AI dealmaking: real-time signal processing, agent systems that reason about opportunities, and a platform that grows without the rewrite everyone saw coming.

The 30-second version

You'd own

The architecture, and the projects built on it

Experience

5-7+ years backend with system design ownership

Compensation

USD, discussed on call 1

Process

3 calls, decision inside 2 weeks

Node.js / TypeScriptPythonCloud architecture & infrastructure (AWS, Azure or GCP)SST / TerraformAI frameworks: LangGraph, LangChain, CrewAI, SageMakerAI agents: AI SDK, Mastra, Hermes Agent, Google ADKLLM providers & gateways: OpenAI / Anthropic SDK, OpenRouter, Vercel AI GatewaySnowflakeNext.js / React Nice: streaming infrastructure, data platforms at scale

Fit check

Nothing is sent anywhere. This is for you, not us. Six statements, honest answer only.

Nothing ticked yet. This one is written for someone with scars. The semi-senior role may be the better conversation.

I've designed systems that scaled, stayed on them afterwards, and have the war stories to show for it. Distributed systems, data consistency and performance trade-offs are production experience for me, not reading. I can turn an ambiguous business requirement into an architecture that survives contact with reality. I know when to over-engineer and when simplicity wins, and I can defend either call. I've led a project end to end. I got everyone aligned on what it was for, set the delivery cadence, and reset expectations out loud when the plan met reality. I can hold a room of business stakeholders in English and make a technical decision make sense to them.

How a normal week actually splits

• 45% building
• 20% architecture
• 20% with stakeholders
• 15% multiplying

Thinking, then building

Still hands on keyboard. Intelligence APIs, agent systems, the parts of the platform nobody else should have to touch first. Most of it is deciding what the right thing is. The code is what a good thought process leaves behind.

Architecture

Deciding how it should be shaped, writing the trade-off down, and being the one accountable when it is wrong.

Leading the project

Product, business, and the funds themselves. You align them on what a project is for, set the cadence, and own the expectations. You shape the roadmap in those rooms rather than receive it afterwards.

Multiplying

Review, pairing, mentoring. Review here means making sure what we ship actually works, not only that the diff reads well.

Three things you'd ship in your first year

• A platform that survives its own success

  Prototype to production without the rewrite. You pick the boundaries and live inside them.

• An agent system that reasons, not just summarises

  Memos, signals and deal data in; a judgement a partner will actually act on out.

• A team that ships better than when it started

  Standards, review culture and the architectural taste that outlasts any one feature.

You'll do well here if

• You’ve owned architecture in production and stayed for the consequences.
• You’d rather shape the roadmap than be handed it.
• You think in trade-offs and can write down why you chose one.
• Your best work makes other engineers faster.
• You’ve run a project, not just the code in it. Scope, cadence, expectations.

Be honest, probably not for you if

• Senior means “stops coding” to you.
• You want the architecture decided before you arrive.
• Telling a stakeholder the date moved is someone else’s job.
• Explaining a technical call to a business stakeholder feels beneath the job.
• You need a large team’s process around you to feel safe shipping.

What you get

Same for every role, every level.

• Remote-first

  Work from anywhere in Argentina. If you live near Buenos Aires or Córdoba, you’re in the office two days a month.

• Performance bonus

  On top of your salary, tied to how you perform.

• Salary in USD

  Paid in dollars, every month, reviewed twice a year.

• Flexible schedule

  Objective-based, with real adaptability. A few hours of overlap with US clients is the only fixed part.

• 14 days PTO + holidays

  Taken, not accrued and forgotten. Local holidays on top, and the week between Christmas and New Year’s off.

• Working equipment

  A MacBook Pro to work on, provided by us.

• Tech budget

  The tools that make you faster: Cursor Pro, Claude Pro, ChatGPT, whatever you’ll actually use.

• Learning budget

  Courses, training and conferences that matter to the work. Ask, don’t petition.

• A path past senior

  Written levels and what each one expects. Lead and staff tracks exist and are open.

• High trust

  Autonomy in exchange for excellence. Nobody checks whether you were online at nine.

How hiring goes · about 2 weeks, start to offer

• Intro call – 45 min

  What you’ve built, what you want next. We name our clients here.

• System design, together – 90 min

  An architecture problem from actual work, argued out loud. No leetcode, no take-home over your weekend.

• Founders + the team – 45 min

  Mutual diligence. Ask us the uncomfortable questions about money, clients and churn.

• Answer either way – Offer or a real reason, within a week of the last call.

  Offer or a real reason, within a week of the last call.

Who you'd be working with

We keep you updated at every stage of the process.

• Cande Monti – Step 1: your intro call
• Lautaro Gonzalez – Step 2: the system design interview
• Nico Pisani – Step 3: the final call