• Design, build, and maintain APIs, services, and systems across Telnyx’s telephony engineering teams. • Work with engineers across the company to build new telephony features at large-scale. • Improve engineering standards, tooling, and processes. • Identify, optimize and resolve issues related to latency, scalability, and performance of core telephony infrastructure.

• Define and document API specifications, endpoints, data models, and protocols (REST, GraphQL) using tools like OpenAPI • Build and implement APIs using programming languages and frameworks such as Java (Spring Boot/Spring Batch), Python, Ruby, and .NET • Ensure seamless integration of APIs with internal systems, external applications, and third-party services • Write unit, integration, and end-to-end tests for APIs • Debug and resolve issues to ensure reliability and performance • Implement authentication, authorization, encryption, and other security best practices to protect data and services • Monitor and optimize API performance, scalability, and reliability using tools like Jaeger, OpenTracing, and GitHub Actions • Manage API versions and ensure backward compatibility as APIs evolve • Work closely with front-end and back-end developers, architects, QA engineers, and other stakeholders to deliver robust solutions • Create and maintain clear, comprehensive documentation for API consumers, including usage examples and best practices • Provide ongoing support and implement enhancements based on user feedback

• Design, develop and maintain backend services (Go/Python) for new and currently existing features of Acronis Cyber Protect & Acronis Cyber Protect Cloud solutions • Translate software requirements into stable, quality, high performance code; write tests, perform code reviews • Collaborate closely with other team members and teams

• Our engineers are responsible for prioritizing, conceptualizing, co-designing, building, testing, and engaging users for any concept we are building out. • We’re generalists in encouraging each other to experience the full stack, • but we’re also aware of each other’s preferences in the stack. • We hope our engineers have more longevity than any one tool we use, • but here is a sampling of our current thoughts about technology: We live on Python/Django and TypeScript/React. • We store blobs in Amazon’s S3, munch on them in Amazon’s EC2, develop in Docker, and deploy containers to Amazon’s Elastic Beanstalk. • We believe PostgreSQL should be the first system you consider when thinking about persisting structured data. • We clean and centralize data in Amazon’s Redshift, and are able to answer almost any question in SQL. • We leverage AI in our product and our internal tooling, and faced with a landscape in constant flux, try to pick the right model or agent on a task-by-task basis. • We have near-full test coverage on the backend, and are making progress on our frontend and integration tests. • We set up continuous integration and deployment because, while this model comes with its own pains, we’ve disliked being on fixed release schedules on previous projects. • We like to move fast and support point-in-time recovery :).