Skills this job asks for
PythonPostgreSQLAWSRust
Add your CV (free) to see which of these your CV is missing.
Where you can work from
Location not specified
The listing does not say where you can work from. Missing information is not the same as worldwide: check before applying.
The company's headquarters is not the same as where you may work from. Visa sponsorship only matters if you would relocate; see below.
Visa sponsorship, if you would relocate
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal: ask the recruiter.
-
?
No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
Before you apply
Sponsorship unknown
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →
About the role
About Payflows
At Payflows, we build software that helps large companies manage and automate their payment workflows. It’s not the flashiest part of a business, but it’s one of the most critical: invoices, approvals, payments, and controls. When these things slow down, the whole company feels it.
But our ambition goes further than just building a better workflow tool.
We believe the future of finance operations is not faster clicking: it’s no clicking at all 🫳 🎤
Finance teams shouldn’t spend their days moving data from one screen to another. Software should do the operational work, and humans should focus on reviewing, approving, and making the decisions that matter.
That’s the direction we’re building toward: an agent-driven finance platform , where intelligent agents handle the repetitive tasks, and users stay in control.
We started in 2022 with a small team and a rough first version of the product. Three years later, we’re working with major companies across France, the UK, and the US while choosing to keep our team small and human-sized.
We moved fast, shipped a lot, and not everything was built in a perfect way. But it helped us learn quickly, sign real customers, and prove that the problem we’re solving truly matters.
In 2024, investors trusted us with a $25M Series A. That gives us the chance to keep growing while also strengthening our foundations and building the system that will power this agent-driven future.
Today, we’re about 35 people from many different countries, and we’re looking for a few amazing humans to join the next chapter. 🤗
🚀 What you’ll actually do
You’ll help build a product that real finance teams rely on every day.
For us, engineering is not just about clean code, it’s about reliability, clarity, and trust, especially when money and automation are involved.
In a typical week, you might:
• Design and implement new services for a product feature.
• Refactor an early service to make it more robust.
• Investigate a performance or production issue.
• Work with product and frontend to shape a new feature.
• Review code and help teammates improve.
• Build backend tools that our AI agents use to perform real finance operations.
• Design safe, deterministic workflows where agents propose actions and humans review them.
Your time will be split between building new features and improving what already exists . Both matter.
You won’t just build endpoints. You’ll help shape the execution layer that our agents rely on: the APIs, data models, and workflows that let them act safely in production.
You’ll work closely with product, frontend, and customer-facing teams. We expect engineers to take ownership of parts of the system and help make them more reliable over time.
💻 Our current tech reality
Our stack evolves based on our challenges, but we care more about good design than trendy tools 🙏
Python is our core language. It helps us move fast, keep the code readable, and fits naturally with our AI-driven approach. A growing part of the system is built around agents that use our backend as a set of reliable, deterministic tools.
• Core language: Python
• Backend: FastAPI + Pydantic
• Data: PostgreSQL
• Infra: AWS, serverless when it makes sense
• Performance: some Rust for critical paths
• Architecture: multi-service backend, simple enough to reason about
Some parts of the system are clean and well-tested. Others were built quickly and need love. That’s the phase we’re in.
Over the next year, we’ll focus on:
• Turning core workflows into reliable tools for our agents
• Simplifying services
• Improving tests and observability
• Making performance more predictable
• Cleaning up early code
We know we’re not perfect, but we care a lot about improving step by step.
✨ Who’s going to thrive wi
View original listing ↗