TRM Labs
Software Engineer, Backend | Product Engineering - US
About this role
TRM Labs seeks a backend engineer to build scalable APIs and systems supporting AI-powered crime investigation platforms. You'll own complex technical projects across product engineering, collaborate with internal and external stakeholders, and help shape the company's backend infrastructure serving billions of users.
What you'll do
- Design and maintain public APIs as part of TRM's API Product suite
- Build scalable backend systems and web services (Node.js backend preferred but not required)
- Collaborate with cross-functional stakeholders to translate vision into technical roadmaps and outcomes
- Enable internal business units through shared engineering services and infrastructure
- Lead projects as technical anchor with full ownership and accountability
- Participate in on-call rotation for internal tools support and customer issue triage
What they're looking for
- Scalable system and API design
- Relational database experience (PostgreSQL preferred)
- Analytical database knowledge
- Backend web application development
- Customer pain-point analysis and translation to technical requirements
- Cross-functional collaboration and stakeholder management
- Problem structuring and prioritization
- Technical communication to both technical and non-technical audiences
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
TRM Labs
TRM Labs builds AI-powered intelligence products designed to detect and disrupt financial crime through advanced machine learning and investigative tools. The company is hiring backend engineers, ML infrastructure engineers, AI research engineers, and AI agent engineers to develop scalable platform infrastructure, GPU-backed systems, model optimization capabilities, and LLM-based agentic applications.
- Website
- trmlabs.com
Likely interview questions
- Describe a time you designed an API that had to scale significantly—what were the key architectural decisions and trade-offs?
- Tell us about a project where you had to understand customer needs and translate them into technical requirements. How did you validate your understanding?