> Markdown version of [/jobs/ext/4783697-software-engineer-ml-infrastructure](https://www.wearedevelopers.com/jobs/ext/4783697-software-engineer-ml-infrastructure). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer, ML Infrastructure - **Company:** The Fundbox - **Location:** New York, NY, United States (Remote available) - **Experience:** Expert - **Salary:** $180,000 - $230,000 - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Amazon Web Services, Computing Platforms, Microsoft Azure, Software Quality, Code Review, Continuous Integration, Information Engineering, Data Infrastructure, Database Design, Software Debugging, DevOps, Distributed Systems, Django Web Framework, Monitoring of Systems, Python (Programming Language), Queueing Systems, Standard Sql, DataOps, Azure Machine Learning, Software Engineering, Data Streaming, Management of Software Versions, Data Logging, Feature Store, Feature Engineering, Flask (Web Framework), Reliability of Systems, Backend, Fastapi, Event Driven Architecture, Containerization, Kubernetes, Data Lineage, Low Latency, Real Time Data, Apache Kafka, Machine Learning Operations, Drift Detection, Restful APIs, Docker, Microservices - **Published:** November 19, 2026 - **Apply:** https://www.careerbuilder.com/job-details/software-engineer-ml-infrastructure-new-york-ny--3ab2f97c-e99e-42a6-a380-2a18e91bb928 ## About the Role Software Engineering, Small Business, Loans, Embedded Systems, Business Growth, Distributed Computing, Application Programming Interface (API), Software Engineering, Code Reviews, Politics, * Bring energy and drive to their work * Have an ownership mentality and see problems through to completion, not just to the ticket being closed * Have a service mindset: enjoy helping internal partners, answer questions clearly and patiently, and treat a confused stakeholder as a signal to make things better * Show intellectual curiosity: ask good questions, think through edge cases, want to understand the "why" * Have a bias toward action and are comfortable with ambiguity Experience: 5+ years of software engineering, with production backend services as your foundation and hands-on data or ML infrastructure work along the way. Required: * Strong backend engineering in Python, our primary language (Java, Go, or another statically typed language also works) * Designing and building RESTful APIs and services in a microservices / distributed systems environment * Hands-on data engineering or ML infrastructure experience: feature pipelines, model serving, training pipelines, or real-time data systems in production * Strong SQL and experience with database design and performance * AWS (or GCP/Azure) and containerization (Docker, Kubernetes) * Solid CI/CD practice, and care for code quality, testing, and system reliability * Clear communication with non-engineers: you can explain data and technical details to data scientists, risk analysts, and business partners * Comfortable collaborating across time zones with a remote engineering team Nice to have: * MLOps tools and frameworks such as SageMaker, MLflow, or Kubeflow * Feature stores, streaming, or event-driven architectures (message queues, Kafka or similar) * API frameworks like FastAPI, Flask, or Django * Model monitoring and drift detection in production * Fintech, lending, credit, or payments experience * Experience in an internal platform or developer-facing role where other teams were your customers * Contributing to system design decisions ## Description A background that fits well: You spent your early career building backend systems at a startup or fintech, then gravitated toward the data and models those systems depended on. You can debug a slow API and a stale feature in the same afternoon, and you'd rather own the whole path than one slice of it.What makes this role different: * Both sides of the wall: You'll write product backend code and ML platform code in the same quarter, often in the same system. Few roles let you do both seriously. * Models that move money: Our models decide who gets capital and on what terms. Latency, correctness, and reliability have real financial consequences. * Close to the people who use your work: Data scientists and our risk team rely on the features and pipelines you build. You'll be their go-to partner for questions about how features work, where data comes from, and why a number looks the way it does. * Global collaboration: You'll work closely with the core platform team in Tel Aviv, plus engineers in Tbilisi: different perspectives, follow-the-sun development, a truly distributed engineering culture. * Early-stage influence: You'll get architectural ownership earlier than you would at a big tech company, with direct influence on how our ML and data platform evolves as we scale. What you'll build: * Credit infrastructure: Services for real-time credit evaluation, underwriting, and decisioning, where model outputs become lending decisions. * Partner integrations: APIs that let software platforms embed Fundbox, and the data flows that come back from them. * Financial products: Lending products like term loans, lines of credit, and merchant cash advances, and the application, approval, servicing, and repayment flows behind them. ML and data platform: * Feature pipelines: Robust, scalable systems for feature engineering that serve both online (real-time) and offline (training and batch) inference, with consistency between the two. * Model deployment and serving: Reliable paths for taking models from a data scientist's notebook into low-latency production services. * CI/CD for models: Pipelines that support continuous model updates, versioning, and safe rollouts and rollbacks. * Monitoring: Logging and alerting that catch data drift, model performance issues, and pipeline failures before they reach a credit decision. * Support for data science and risk: Work with data scientists to develop and refine features, and be the first stop for questions from data science and the risk team about feature definitions, data lineage, and model inputs. When the same question comes up twice, you improve the docs or tooling so it doesn't come up a third time. * Core platform partnership: Work with the core platform team in Tel Aviv on shared services and infrastructure, and with DevOps and DataOps to fit ML into our broader AWS stack.