Full-Stack Engineer (Backend Leaning)
1 day ago⚠️ Before applying, please carefully review all the job requirements
- Location:
- Remote
- Work Arrangement:
- Remote
- Job Type:
- Full-time
- Company:
- Eleven Labs
- Salary:
- Negotiable
- Posted:
- 2026-10-14
- High-velocity:
- Rapid experimentation, lean autonomous teams, and minimal bureaucracy.
- Excellence Everywhere:
- Everything we do should match the quality of our AI models.
- Global Team:
- We prioritize your talent, not your location.
- Learning & Development:
- ElevenLabs proactively supports professional development through an annual discretionary stipend.
- Annual Company Offsite:
- Each year, we bring the entire team together in a new location - past offsites have included Croatia and Italy.
- Co-working:
- If you’re not located near one of our main hubs, we offer a monthly co-working stipend.
Job Overview
- A new opening is available for a Full-Stack Engineer (Backend Leaning) - Payments Engineering. According to the listing, this is a remote full-time position. The salary mentioned in the listing is $781. The listing places its emphasis on REST APIs, Git and GitHub, Python, Docker and Artificial Intelligence. For general context: REST APIs let the front end and back end of an application exchange data in a structured way. Git tracks code changes so teams can work on the same project without overwriting each other. Read the details below carefully and use the application link on this page if the role matches your profile.
What These Requirements Mean in Practice
- ★ REST APIs: Designing and consuming HTTP endpoints so a front end, mobile app or another service can exchange data.
- ★ Git and GitHub: Tracking changes, working on branches, opening pull requests and resolving conflicts so a team can share code safely.
- ★ Python: Writing readable scripts and backend or data code using Python's standard library and common packages.
- ★ Docker: Packaging an application and its dependencies into containers so it runs the same way everywhere.
- ★ Artificial Intelligence: A general understanding of how AI systems learn from data, where they are useful, and where they can be unreliable.
Skills to Brush Up Before Applying
- ★ REST APIs: HTTP methods and status codes, authentication basics such as tokens, validation and error responses
- ★ Git and GitHub: branching and merging, pull requests and code review, resolving merge conflicts
- ★ Python: core data structures, functions and modules, virtual environments and pip
- ★ Docker: Dockerfile basics, images versus containers, docker compose
- ★ Artificial Intelligence: supervised versus unsupervised learning, common real-world use cases, limitations and bias
Who May Be a Good Fit for This Role?
- This role may be suitable for candidates who match the skills and experience described in the requirements. Those who are comfortable with REST APIs, Git and GitHub, Python, Docker and Artificial Intelligence and enjoy building practical projects may find the requirements a good match. A remote arrangement may suit people who work well independently and communicate clearly in writing. This is editorial guidance only, and the employer makes the final decision on suitability.
Application Tips
- Applicants may want to highlight relevant experience with REST APIs, Git and GitHub, Python and Docker in their CV. Because version control is mentioned, a GitHub profile with a few well-described repositories can make your skills easier to verify. If you have used AI tools or built small projects with language models, briefly describe what you built and how you checked the results. A short, role-specific summary at the top of your CV usually reads better than a generic profile. These are general tips, not requirements stated by the employer.
Prepare for Your Interview
- These suggested questions can help you prepare for an interview by focusing on the skills, responsibilities, and technical areas relevant to this role. They are for preparation only and are not confirmed employer questions.
- Q: How would you handle authentication and input validation for a REST API you are building?
- Q: What is the difference between git merge and git rebase, and when would you use each?
- Q: How do decorators and generators work in Python?
- Q: What problem does Docker solve, and how do an image and a container differ?
- Q: Where could AI add value to a typical web application, and what risks should you plan for?
- Q: What makes an API RESTful, and how do you choose HTTP methods and status codes for different operations?
- Q: How do you resolve a merge conflict in a shared repository?
- Q: How do lists, tuples, sets, and dictionaries differ in Python, and when would you use each?
- Q: How do you stay organised and communicate clearly when working remotely?
Ideal Candidates Fill the Job Form: Apply Here
