Rewritten
Backend Engineer, Payments Team
We're looking for a Backend Engineer to join our Payments team and help build the infrastructure that powers transactions at scale. You'll work on systems where reliability and correctness aren't optional — every line of code has real financial impact.
Responsibilities:
- Design, build, and maintain backend services powering our payments infrastructure
- Collaborate closely with product and other engineering teams to ship reliable, scalable features
- Write clean, well-tested code in Node.js, working with PostgreSQL-backed data models
- Participate in code reviews and help uphold engineering best practices across the team
Qualifications:
- 3+ years of professional backend engineering experience
- Strong proficiency in Node.js and PostgreSQL
- Experience with payment systems or financial infrastructure is a plus, but not required
- Comfortable working in a remote-friendly, collaborative environment
We offer a competitive salary, equity, and a remote-friendly culture built around trust and ownership.
About this tool
Writing a job posting from a blank page is slower than it should be, especially when you already know exactly what the role needs — you just haven't turned it into polished, candidate-facing copy yet. This tool takes rough role details, whatever level of detail you have, and produces a complete posting with a compelling summary, responsibilities, and qualifications sections. It sits at the opposite end of the hiring pipeline from job-posting-to-interview-questions, which works from a finished posting rather than producing one.
Frequently asked questions
How much detail do I need to provide?+
The more specific detail you give (team, tech stack, seniority, must-haves vs nice-to-haves), the more tailored the posting will be — but even a short, rough description will produce a usable draft.
Will it include salary information?+
Only if you include salary details in your input — the tool won't invent compensation figures, though it will reference general compensation language like "competitive salary" if you don't provide specifics.
Can I use this for non-technical roles too?+
Yes, it works for any role type — just describe the responsibilities and qualifications relevant to that specific job.