Aumenta le possibilità di ricevere una risposta da questo datore di lavoro
Il tuo curriculum e una lettera di presentazione personalizzati, che corrispondono esattamente a ciò che sta cercando.
Outside Hire is seeking a Senior Fullstack Engineer for the Payments platform. You will build the embeddable SDK, routing services, tokenization boundaries, and webhook/reconciliation flows.
This role operates across frontend and backend to ensure money moves securely and reliably. Ideal candidates have 7+ years in production software, deep React/TypeScript skills, strong .NET backend design, and experience with payment systems and security.
About OutsideHire Outside 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! outsidehire.com
You will build across the payments platform: the embeddable SDK that collects card and wallet credentials, the services that create sessions and route transactions to the right gateway, the tokenization boundaries that keep sensitive card data out of our systems, and the webhook and reconciliation flows that keep money accurate. This is not a role about building forms and CRUD screens. It is infrastructure that real money flows through, where a bug is not a broken layout but a failed transaction, a double charge, or a compliance incident. You will work both sides of the wire, and you need to be genuinely strong on both.
We move 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 sharp question before writing code, not after shipping the wrong thing You escal[e] ambiguity early instead of guessing quietly You push back when an approach is wrong, with a better alternative You are comfortable working directly with product and client 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 find this uncomfortable. If you have worked in startups or fast-moving product teams, this will feel familiar.
We are explicit about this because it saves everyone time. We are hiring for craft. That means naming things well, keeping abstractions honest, deleting code that should not exist, reading the gateway documentation rather than guessing, and caring what the integration feels like for the engineer on the other side. We would rather ship one correct payment flow 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 built all along, we want to talk.