Infra Engineer

About Finosu Finosu is an AI-native loan servicer. What is that? A servicer handles the communications and payment rails for lenders. The servicing industry services over 10 trillion dollars of debt a year. Loan servicing is the perfect application for AI. Borrowers want help on their time, not during call center hours, and AI makes 24/7 support real for the first time. It also makes compliance better, not worse: every interaction follows the rules, every disclosure is delivered, and everything is logged and auditable. What makes us different is how we measure success. We are not judged on generic CSAT scores. We are judged on dollars generated for our lenders, and it turns out the two go together: borrowers who are treated well perform better. We know this problem because we lived it. Our founders built a $200M consumer lender together, owning the end-to-end stack from origination through servicing and collections. We felt every broken part of it firsthand: the vendors that didn't care about outcomes, the compliance gaps, the borrowers who fell through the cracks. So we are building the thing we wished we had. Things to Know We are a start-up and our processes are in flux. Priorities might shift more abruptly than at a more establish company.

• We’re in office, we have found that collaboration especially in a context-rich field is important
• You will own and be intimate with our AWS infrastructure that runs on K8. In addition, you will help optimize our other resources like our Postgres, Redis and NATS instances.

About the Role This is a infra/product role to start. However, as we scale, it will be more focus on infra. The reason we think it’s good to start 50-50 is because we think that sometimes the best thing to do from an infra perspective involves having a good idea of the business requirements and potentially rearchitecting the product. In this role

• Scale our AI agents. Figure out to bypass vendors caps whether by clever orchestration or moving to self-hosting when relevant
• Identify needless spend from SaaS bloat and cut off unneeded vendors
• Implement an observability stack so we can understand how each component of the system is doing

Projects people in this role have taken or will take:

• Migrate from Datadog to Grafana. Dear lord, that saved us so much money, and we would love to do that again in other places
• K8 optimization. Figure out the optimal number of servers and dynamically scale off certain metrics since CPU and Memory aren’t the bottlenecks
• Figure out why Postgres prepared statements are causing a memory leak.

About You

• While we do have a roadmap, we expect you to contribute and push back if you feel there are more important projects to work you. We love tension and conflict if it creates a better product
• An ability to learn fast, we don’t care about experience as much as slope. The world is changing underneath us, 2 years ago it would be weird if an engineer locked himself in a room and talked to the computer to make software, but here we are…
• Love observability. A lot of our need comes down to understanding why things happen, so observability is important

About You

• While we do have a roadmap, we expect you to contribute and push back if you feel there are more important projects to work you. We love tension and conflict if it creates a better product
• An ability to learn fast, we don’t care about experience as much as slope. The world is changing underneath us, 2 years ago it would be weird if an engineer locked himself in a room and talked to the computer to make software, but here we are…
• Product minded, do you think the product manager discipline is outdated and engineers should be leading these decisions? While we refuse to comment on things that might get us in trouble in the future, we love engineers who want to make product decisions. In this role, you will be the product manager of the projects you own