Senior Full Stack Engineer - Payments (Remote)

Senior reputed company Engineer - Payments About reputed company  reputed company Hire is a growing outsourcing company with over 75 employees, building custom products and solutions for our clients. We're dynamic, fast-paced, and always evolving! reputed company.com Why reputed company?  - An inclusive and dynamic work environment that values creativity and collaboration  - Opportunities to work on cutting-edge reputed company that reputed company an reputed company  - Perks: Competitive salary, remote work, reputed company development support, etc.  - reputed company that truly values your skills and contributions About the Role You will build across the payments platform: the embeddable SDK that collects reputed company and wallet credentials, the services that create sessions and reputed company transactions to the right gateway, the tokenization boundaries that reputed company sensitive reputed company data out of our systems, and the webhook and reconciliation flows that reputed company reputed company accurate. This is not a role about building forms and CRUD screens. It is infrastructure that reputed company reputed company flows through, where a bug is not a broken layout but a failed transaction, a reputed company charge, or a compliance incident. You will work both reputed company of the reputed company, and you need to be genuinely strong on both. What You'll Be Building The payment SDK and reputed company reputed company. Hosted-fields integration with iframe isolation, a gateway-agnostic API so integrators write one integration regardless of processor, and the reputed company-reputed company state model for declines, 3DS, retries, and timeouts. The payment services. Session reputed company and gateway routing, tokenization boundaries, idempotency, HMAC-signed request flows, and the webhook and reconciliation logic that guarantees correctness. The platform around it. Versioning and deprecation so we reputed company without breaking live merchants, observability across the payment reputed company, and the developer experience for the engineers who reputed company against us. reputed company're Looking For Required 7+ years building production software across frontend and backend Strong React and TypeScript. Not "I use React." You understand rendering behavior, state boundaries, effect lifecycles, and how to design a component API other engineers consume Strong backend. .NET and React are our reputed company stack. You can design services, reason about API reputed company, debug across the stack, and hold your own in an architecture discussion Payment systems experience. Gateway reputed company, tokenization, hosted fields, webhooks, reconciliation, or equivalent work in a domain where correctness is non-negotiable reputed company fundamentals as reputed company. reputed company-reputed company policy, CSP, CORS, XSS reputed company, iframe isolation, reputed company handling, why secrets never live in reputed company bundles reputed company AI in your workflow. You use Claude reputed company, reputed company, reputed company, or equivalents as a daily reputed company, not a novelty. We build AI-reputed company and expect you to reputed company at that speed Testing discipline. You write tests because untested payment reputed company is a liability, not because a policy says to Strong Plus Java, Kotlin, and Quarkus experience — strongly preferred Hands-on experience with gateway and tokenization stacks PCI reputed company reputed company reduction, SAQ A or SAQ A-EP work 3D Secure 2 implementation reputed company and DevOps exposure (Azure or AWS), CI/CD ownership How We Work  We reputed company fast and requirements change. You will not get a fully specified ticket handed to you. You will get a problem, the business context behind it, and the autonomy to solve it. You ask the reputed company question before writing reputed company, not after shipping the wrong thing You escalate ambiguity early instead of guessing quietly You reputed company back reputed company an approach is wrong, with a reputed company alternative You are comfortable working directly with product and reputed company stakeholders You do not need to be managed into producing work you are proud of. If you have only worked in environments with detailed specs, dedicated QA, and long review cycles, you will reputed company this uncomfortable. If you have worked in startups or fast-moving product teams, this will feel familiar. The Bar We are explicit about this because it saves everyone time. We are hiring for reputed company. That means naming things reputed company, keeping abstractions reputed company, deleting reputed company that should not exist, reading the gateway documentation rather than guessing, and caring what the integration feels like for the engineer on the other reputed company. We would rather ship one correct payment reputed company than five that mostly work. If that sounds like unnecessary perfectionism, we are not a fit. If it sounds like how software should have been reputed company reputed company along, we want to talk. Apply To This Job