Engineer, Treasury & Cash Management
Carlyle Group
- Location
- Washington, DC
- Work model
- On-Site
- Level
- Mid
- Posted
- 8d ago
Skills
About this role
Position
Summary The Engineer, Treasury & Cash Management Technology sits within Carlyle’s Treasury & Payments Technology team, reporting to the Treasury & Payments Lead, and contributes hands-on to the implementation, enhancement, and ongoing operation of the firm’s treasury management system (TMS). The team’s initial focus is the TMS rollout in support of Carlyle AlpInvest, going live this year. Over time, the platform is expected to expand to serve Carlyle’s Global Private Equity and Global Credit segments and the firm’s Corporate Treasury function making this a build-once, scale-many opportunity at the center of how the firm manages cash, liquidity, and payments. This is a hands-on engineering role at the center of Carlyle’s treasury technology stack: an engineer who partners directly with Treasury and Finance stakeholders, owns delivery and ongoing operation of the TMS platform they support, and is accountable for the outcomes the system produces accurate cash positioning, reliable payments, clean reporting. You will embed with Treasury, Finance, and operations partners supporting Carlyle AlpInvest and, over time, the broader investment segments and Corporate Treasury to translate treasury and cash management requirements into configured, integrated, well-tested software that goes into daily use. You will own the TMS implementation work in flight and the enhancements and integrations that follow: bank connectivity, accounting and custodian feeds, cash positioning and forecasting, payment workflows, and the reporting that the business runs on. You will work with leading commercial TMS platforms (Hazeltree, Kyriba, GTreasury, or comparable) and the surrounding integration and data tooling required to make them work end to end. You will collaborate closely with Finance stakeholders, end users, and offshore engineering and operations partners communicating clearly, setting expectations, and earning trust across a distributed team. What Success Looks Like In the first 12 months, you will have helped take the AlpInvest TMS live and through its first cycles of daily use, owned the integrations and enhancements that turn the platform into a reliable part of how Treasury operates, and earned trust as the go-to engineer for the Finance and Treasury stakeholders who depend on the system. Your work will be visible at senior levels of the firm. In-Office Requirement: 4 days a week in D.C and NY or Remote Responsibilities TMS Delivery & Enhancement (≈50%) Partner with Treasury, Finance, and operations stakeholders to translate cash management, liquidity, and payments requirements into configured, integrated TMS functionality. Own delivery on assigned workstreams of the AlpInvest TMS implementation — configuration, integrations, data migration, testing, cutover, and adoption — in partnership with your manager, the vendor team, and offshore contributors. Design and build integrations between the TMS and Carlyle’s broader ecosystem: banks (REST APIs, SFTP, ISO 20022 messaging), accounting systems, custodians, fund administrators, and downstream reporting and data platforms. Build treasury reporting and dashboards — cash positions, liquidity, forecasts, payment status, exception monitoring — in Power BI, Tableau, or the platform’s native reporting layer. Extend the platform over time to support additional business segments (Global Private Equity, Global Credit) and Corporate Treasury use cases as the footprint grows. Move at the speed the business needs: scope tightly, ship in weeks, and harden through real use rather than over-engineering up front. Operate & Support (≈50%) Own the day-to-day reliability of the TMS and its integrations — monitoring, alerting, issue triage, root cause analysis, and incremental hardening of the components users depend on. Provide hands-on support to Finance and Treasury end users: investigate questions, resolve data and configuration issues, and improve the system based on what