LivePerson
Java Backend Engineer
New York, New York$150k–$170kfull-timemidAdded yesterday
About this role
LivePerson seeks a Java Backend Engineer to design and build high-performance, scalable backend services for their conversational AI platform. You'll develop low-latency REST APIs, troubleshoot production systems, and collaborate with the Bots & Automation team in a fully remote role.
What you'll do
- Design and develop high-volume, low-latency backend applications for mission-critical systems
- Design and implement REST-based backend services
- Debug production issues and maintain existing codebases
- Write technical specifications and documentation
- Participate in on-call rotations for production support
- Collaborate with Bots & Automation team on next-generation bot runtime platform
What they're looking for
- Java Spring Boot with multi-threading expertise
- REST API design and development
- Database management (SQL, NoSQL, Cassandra, MySQL)
- Data processing tools (Kafka, Airflow, Apache Spark, Hadoop)
- Distributed microservices debugging
- Kubernetes
- Git and Jenkins
- Third-party API integration
Benefits
- Medical, Dental, and Vision Insurance
- 401(k) retirement plan with 4% employer match
- Employee Stock Purchase Program (ESPP)
- Flexible Paid Time Off (PTO) and paid public holidays
- Generous parental leave and fertility services
- Access to Employee Assistance Program (EAP)
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.
LivePerson
LivePerson builds high-performance backend systems and cloud infrastructure for bots, automation, and conversational platforms. The company is hiring Java Backend Engineers and DevOps Engineers to develop and maintain its scalable services and cloud operations.
- Website
- liveperson.com
Likely interview questions
- Walk us through your experience building high-volume, low-latency systems and how you optimized them for performance.
- Describe a production issue you debugged in a distributed microservices architecture—what was your approach and what tools did you use?