Innovation
The best ideas here start in a customer call, not a roadmap meeting. Seniority does not decide whose idea wins.
Vero is a small team of operators and engineers rebuilding how lenders fund, service and monitor dealer inventory. The problems are unglamorous and enormous, the customers are real, and nothing you ship here sits on a shelf.
Transform how financial institutions deliver asset finance by providing innovative technology solutions that enhance efficiency, reduce risk, and improve customer experiences.
Vero builds VeroOS, one platform covering the full wholesale finance lifecycle: taking an application, funding a unit, tracking inventory, clearing a title, running an audit, watching risk, and servicing the account through to payoff. Twelve modules, one data model.
Our customers are banks, captive finance companies, OEMs and distributors, auctions and independent lenders. Before Vero, most of this ran on spreadsheets, email and a core system built in another decade. When a release goes out here, somebody's Monday changes.
It is a real category with real constraints. Money moves, titles are legal instruments, and auditors ask questions later. That makes the engineering more interesting, not less.
These decide what gets built, who gets hired, and what a good week looks like here.
Continuous improvement based on partner feedback and industry trends.
The best ideas here start in a customer call, not a roadmap meeting. If you watch someone do something in eleven clicks that should take two, you are expected to say so and then go fix it. Seniority does not decide whose idea wins.
Functioning as an extension of our clients' teams.
We sit inside our customers' operations, not across a table from them. Everyone here talks to the people using the product, whatever their title, and nobody gets to describe a workflow they have never watched somebody run.
Streamlining operations and reducing complexity.
We take work off people's desks, starting with our own. That shows up in the product as fewer screens and fewer handoffs, and internally as short meetings, written decisions, and a strong bias against process that exists to reassure somebody.
Enterprise-grade security and compliance.
Regulated lenders put live portfolios on our platform, and auditors ask about them afterwards. Careful work is not a drag on velocity here, it is the product. We move fast around the things that matter, never through them.
Scope here is unusually wide because the team is small. People own a module, a customer program or a function outright, decide how it should work, and answer for how it turns out. That is uncomfortable at first and it is the main reason people stay.
Engineers and product people sit in on customer calls. Servicing and delivery file the sharpest product feedback we get, because they run the workflows every day. No layer of translation between the people using VeroOS and the people changing it.
Four offices across two continents means decisions, reasoning and procedures live in writing, not in whoever happened to be on the call. Good written thinking is a hiring criterion here for every role, not just the technical ones.
Releases go to lenders who are funding units that week, so the work is not finished when it merges. We watch what we ship in production, on real portfolios, and we fix what we broke before we start the next thing.
Four offices, one team, and a short distance between noticing a problem and being the person who fixes it.
The best ideas here start in a customer call, not a roadmap meeting. Seniority does not decide whose idea wins.
Everyone here talks to the people using the product, whatever their title. Nobody describes a workflow they have never watched somebody run.
Short meetings, written decisions, and a strong bias against process that exists to reassure somebody.
The basics, done properly, for every full-time employee.
Six functions, one product. We hire into these areas as customer programs grow, which is rarely on a tidy schedule. If one of them is your background, introduce yourself before a posting exists.
The platform, the APIs and the integration surface behind VeroOS. Backend services that move money and collateral data, the front-end surfaces lenders live in all day, and the pipelines that keep 40+ third-party connections honest.
Introduce yourself ›Turning lending workflows into software the desk actually prefers to its spreadsheet. Product managers here own a module end to end and spend real time watching the operation they are designing for, not reading a summary of it.
Introduce yourself ›Enterprise sales into banks, captive finance companies, OEMs and distributors, auctions and independent lenders, plus the channel partnerships that put a Vero-powered program in front of their dealers.
Introduce yourself ›Customer success, run the way Vero works: as an extension of the lender's own team. Owning adoption, health and expansion after go-live, and carrying what you learn straight back into the roadmap.
Introduce yourself ›Getting a lender live and keeping the launch honest: data migration, configuration, integration work, testing and training, from signed contract to the first funded unit on VeroOS.
Introduce yourself ›The operators. Credit analysis and underwriting, portfolio and risk monitoring, audits, titles, collections, and the managed-services team that runs entire lending programs on a client's behalf.
Introduce yourself ›Product and engineering in the US and India, servicing in the Carolinas, headquarters in New York, everyone on the same platform.
Leadership, go to market and partnerships. Where most customer conversations start.
Product and engineering, working the same hours as the desks they build for.
The servicing and managed-services operation that runs lending programs.
Engineering and quality, overlapping US mornings and owning the same surfaces.
Most roles are based in one of these locations. Remote work available based on position.
Send us a note anyway. Tell us which of the six teams you belong on and what you would want to own.
The same shape for every role, adjusted for seniority. You will always know who you are meeting next and why.
A short call with the hiring manager. What you have built, what we are building, and whether the problems line up.
Two or three conversations with the people you would work with, including at least one outside your own function.
A time-boxed piece of real work in your discipline, scoped to a couple of hours. No trick questions, no weekend project.
A conversation with one of Vero's co-founders about where the company is going and where you would sit in it.
References, offer and a start date. Once we are sure, we move quickly, and we tell you either way.
Vero Technologies is an equal opportunity employer. We consider all qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status, genetic information, or any other characteristic protected by applicable law. If you need a reasonable accommodation at any point in the hiring process, let us know and we will arrange it.
No posting for you yet? Send a note anyway. It goes to the team directly, not into an applicant tracking system nobody opens.