Software Engineer - Full Stack

**The Mission** AI agents are ready to run the economy, and PayOS is readying the financial infrastructure for it. **The Opportunity** We are looking for a Full-Stack Engineer. We need you to own core systems end-to-end - from backend services and APIs to the user-facing product. This is a role for a "10x" builder who wants to make a difference in commerce & fintech. All experience levels are welcome - including new grads. * Are you entrepreneurial and/or have you ventured on your own before? * Do you feel like you have it in you to be a General Manager of what you will build — build, sell, support? * And when you build, do you obsess over UX? * Are you the engineer who knows what's the next big thing the world needs? If yes, please apply immediately. **Your Stack & Responsibilities ** * Full Stack Ownership (TypeScript/JavaScript First): Our core stack is TypeScript, JavaScript, and Node.js — from backend services to React/Next.js on the application layer. Python is our secondary language, and fluency there is a plus. You can take a feature from database schema to polished UI without hand-offs. * Backend & API Design: You will design and build the services, APIs, and data models that power PayOS. You know how to build systems that are performant, well-structured, and easy for other engineers (and customers) to build on. * Frontend Craft: You build interfaces that make complex financial workflows feel simple and beautiful. You care about the details — states, edge cases, latency, polish. * Infrastructure & DevOps: You are comfortable owning deployment, CI/CD, monitoring, and cloud infrastructure. You ship, and you keep what you ship running. * Reliability & Testing: In fintech, 90% accuracy isn't enough. You know how to build automated tests, observability, and safeguards to ensure correctness before money moves. * AI-Leveraged Development: We maximize leverage by embracing AI. You use tools like Claude, Gemini, and ChatGPT to amplify your output far beyond what is typically possible for a single person. * Forward-Deployed Engineering: You will frequently partner with customers to integrate our platform. You will build custom demos, integrations, and workflows that prove the value of PayOS. **Our DNA (Who You Are)** * Passion & Agility (High Intensity): We move incredibly fast. We are a team that does "whatever it takes" to move the needle. This often means working with high intensity and being responsive outside of traditional hours because we are deeply invested in our mission. * Concrete Outcomes > Activity: We don't care about "effort"; we care about solving our customers' problems and building the services they need. You measure your success by the concrete value you bring to the company every day. You ship code that works, not just code that looks good. * Deep Product & Market Fluency: You must go beyond the code. You need to deeply understand the products we have and exactly what the market demands. Success here means identifying customer gaps and architecting solutions that resonate immediately. * Ownership & Autonomy: We don't have playbooks. You are a self-learner who spots a problem and solves it immediately without waiting for instructions. You roll up your sleeves and wear multiple hats. * One Team, Zero Politics: Because we are small, chemistry is everything. We prioritize total transparency. If you face a roadblock, you share it early. We view challenges collectively: an issue you face is an issue for all of us. **Benefits & Perks** * Top-Tier Healthcare: 100% Employee-Covered Health, Dental, and Vision insurance. * Meaningful Equity: You are joining an early-stage team with real ownership. * Direct Mentorship: Work directly with a world-class engineering team. * Cutting Edge: Work on the absolute frontier of Fintech x AI. **How to Apply** We do not want a standard cover letter. Please send an email to hiring-ops@payos.ai with: * Your GitHub/Portfolio. * A link to a LIVE project you have built (deployments > tutorials). * The "Bug Report": A 2-3 sentence description of the hardest, weirdest debugging challenge you've faced and how you solved it.