EMPIRE is looking to solve the problem of tracking and managing finances associated with music projects by building and maintaining backend systems and integrations with third-party financial systems.
Requirements
- 5+ years of professional backend engineering experience, including at least 2+ years leading PHP/Laravel development efforts.
- Strong hands-on experience with PHP (vanilla and Laravel), relational databases (MySQL/PostgreSQL), and API design.
- Proven ability to lead and mentor backend engineering teams.
- Experience building and integrating with third-party financial platforms (e.g., ERP, expense management, payments).
- Strong understanding of budgeting, expenses, approval workflows, and payment processing.
- Knowledge of standard terminology, deal structures, and royalty collection and payment flows within the music industry.
- Proficiency in automated testing frameworks (PHPUnit, Pest) and backend QA practices.
Responsibilities
- Own the architecture, design, and implementation of backend services and APIs for financial features of our proprietary ERP systems that serve musicians, record labels, and publishers.
- Build scalable, secure, and maintainable backend code using PHP (vanilla + Laravel).
- Develop and maintain integrations with third-party financial systems (e.g., BREX, NetSuite, Bill.com).
- Implement workflows to tie expenses, invoices, and payments to project budgets with role-based approvals.
- Drive backend performance, reliability, and compliance across financial data pipelines.
- Establish and enforce best practices in code quality, testing, database design, and deployment.
- Mentor and guide backend engineers, providing technical direction and career growth support.
Other
- Collaborate cross-functionally with finance, product, and engineering teams to deliver features aligned with operational and compliance needs.
- Contribute to technical strategy and long-term planning for backend architecture to support financial workflows and company growth.
- Excellent leadership, collaboration, and communication skills in cross-functional environments.
- Comfortable context switching between legacy code and newer codebases.
- Bachelor's degree or equivalent experience (not explicitly mentioned but implied)