Software Engineer, Iru

• 2+ years of professional software engineering experience, with meaningful time spent building backend systems
• Backend engineering experience in Python, with the ability to read and contribute to a FastAPI codebase. You do not need to be a Python expert, but you should not be starting from scratch
• Familiarity with integrating external APIs: making HTTP calls, handling authentication, parsing responses, and dealing with errors gracefully
• Solid SQL fundamentals: writing queries, designing schemas, and reasoning about how data flows through a system
• Exposure to asynchronous patterns such as task queues or background workers (production experience is a plus, not a requirement)
• Full-stack capability: you have shipped production UI in React with TypeScript and can own a feature end to end, including its interface
• Willingness to work through ambiguity and ask for help when you need it
• Clear written and verbal communication
• Required to work on-site 3x a week in our Miami office (Coral Gables)

Desirable

• The Connect team is building an integrations platform from scratch
• Most integration platforms require hand-written code for each connector
• Connect takes a declarative approach: you define connectors as structured specifications, and the platform validates and executes them
• Product teams embed integrations through an SDK
• End users access them through a separate gateway
• The platform handles credential management, execution, and reliability for both paths
• As a Software Engineer on this team, you will spend most of your time in the backend: implementing connectors as declarative specs, building services that talk to third-party APIs, and working on the platform infrastructure that makes those integrations reliable
• The problems are real and varied: OAuth flows that differ across every provider, webhooks that arrive out of order, rate limits that change without notice
• You will also build features in the React and TypeScript frontend
• The admin product serves internal operators, and the interfaces you build need to be production-quality
• You will carry features from API to interface without a handoff
• Expect a split of roughly 70% backend and 30% frontend, stable over time. The role suits engineers who want to grow their backend skills on real infrastructure problems, are comfortable working across the stack, and care about shipping well-built software
• Day-to-day work falls into the areas below. Backend platform work carries most of the weight; frontend work serves the systems you build
• Build connectors and platform services. Implement integrations as declarative specs and build the backend services that execute them. Each new connector teaches you something about how third-party APIs actually behave
• Handle the realities of third-party APIs. Work with OAuth flows, webhook ingestion, rate limiting, and retries. Learn to debug failures in systems the team does not control
• Write code that handles state carefully. Work with connection management, sync state, and workflow execution where correctness matters more than speed
• Contribute across the stack. Build features end to end, including the React and TypeScript frontend, and keep frontend patterns coherent as the product matures
• Participate in technical decisions. Contribute to design discussions, ask good questions about tradeoffs, and develop your judgment for when simple solutions outperform clever ones
• Grow through ownership. Take on well-scoped projects, deliver them end to end, and expand your scope as you build confidence with the platform
• Collaborate closely with a small team. Engage in code reviews and design discussions, give and receive feedback, and help the team maintain high engineering quality