Senior Software Engineer, Backend Engineering

View full description

Requirements:

• Proven experience as a technical lead for backend services and cloud infrastructure, guiding the team in delivering high-quality solutions.
• Proficiency in programming languages such as Python, Go, or Typescript, with a strong ability to write clean, maintainable code.
• Hands-on experience with Google Cloud Platform (GCP), Amazon Web Services (AWS), and/or Microsoft Azure.
• Demonstrated expertise in integrating third-party APIs to expand application capabilities.
• Solid understanding of API design principles and best practices.
• Excellent problem-solving skills, with a focus on delivering scalable and efficient solutions.
• Strong knowledge of database design and optimization techniques.
• Exceptional written and verbal communication skills, with the ability to effectively collaborate with team members and stakeholders.

Responsibilities:

• Lead the team architecting, building, and optimizing our backend services and cloud infrastructure.
• Collaborate with cross-functional teams to gather requirements and architect solutions that align with business objectives.
• Mentor and guide junior engineers, fostering a culture of collaboration, learning, and growth within the team.
• Develop and maintain RESTful APIs and services to enable seamless integration with various applications and third-party platforms.
• Integrate 3rd party APIs to enhance the functionality and capabilities of our applications.
• Ensure the security and scalability of backend systems, implementing best practices for data protection and access control.
• Monitor and troubleshoot production systems, proactively identifying and resolving potential issues.
• Stay up-to-date with the latest developments in cloud technologies and leverage them to enhance our infrastructure and services.
• Conduct code reviews and provide constructive feedback to maintain code quality and adherence to coding standards.
• Communicate technical concepts and project updates effectively to both technical and non-technical stakeholders.