We help turn existing commercial lenders into online lenders.
We have a highly motivated, paying customer base (20 customers, average ACV $30k) using our existing product and helping us develop our new, flagship product. When the flagship product is completed, our revenue will double from pre-committed customers.
Our CTO has extensive distributed systems experience and previously successfully exited to Twitter, when his AI company was acqui-hired at a high premium.
We have the runway and freedom to focus on creatively and cleanly building our next generation systems.
Our engineering team is small. Our CTO is the primary backend developer and we have a junior front-end developer full-time. In addition, we have two very experienced senior engineers who work part-time, remotely, helping in architecting and reviewing code (both work full time at large silicon valley software companies, and are likely to come join our team full time by the end of this year). We also have a full-time PM with 20 years experience in software startups.
We're an agile shop, using asana for 1 week sprints. we are implementing a continuous integration system.
The flagship product we're developing needs a great deal of functionality and serves a fairly niche market that is unfamiliar to most engineers (secured commercial lending). Simply understanding the user's use case is a major barrier to entry for our competitors — the ins and outs of this market are highly complex. Our current design has largely addressed these complexities, but there is a large amount of creativity still needed to execute that design in a way that is scalable, extensible, and crucially, stable enough to be a financial system of record.
We currently have a mostly-working prototype of the flagship product that's been built in our existing rails backend. We need to complete this with customer input in order to reach a full understanding of the product requirements when we move our development over to our golang back-end. An example for this would be to create a new user category, with a separate log-in flow and reduced permissions, who can only propose changes to specific data. When that user proposes a change, another user with higher permissions must be notified, and can go in to accept or reject the changes.
For migrating our systems to services written in golang, running in kubernetes, we need to build some common tools and components: stats collecting, error alerting, data encryption, request tracing, smoke testing, traffic redirecting.
Before migrating to our new golang back-end, we need to establish a new database schema that eliminates the existing tech-debt of our old back-end. A full re-architecture of the database is currently underway, but additional input is needed.
We're a small and close-knit team, with a high emphasis on openness and professionalism. Our main goals is to build a great product that we can all be proud of, while maintaining a high quality of life.
lunch provided. if you stay late, dinner is also covered
We're working to build a distributed team. as such, engineers can often work from home, and we're open to having fully remote team members
We have an office in SF and an office in Brooklyn, and team members often travel between the two offices. We also have customers around the country, and have opportunities for engineers to visit them on-site to learn more about their day-to-day work.
Interested in this company?
Skip straight to final-round interviews by applying through Triplebyte.