Sr. Back-end Software Engineer in TECLA

TECLA is a fully remote software development company with a diverse and highly skilled team of 100+ experts across Latin America. We specialize in AI, cloud, automation, and DevOps, building innovative solutions for high-growth startups and established mid-market technology companies in the U.S.

Our work culture is agile, collaborative, and fast-paced—we take our work seriously while keeping the environment fun and engaging. As a remote-first company, we emphasize strong teamwork and close collaboration, working seamlessly with our U.S. partners as one integrated unit. Whether optimizing cloud environments, developing AI-driven applications, or enhancing DevOps automation, TECLA is at the forefront of technical innovation, solving complex challenges with cutting-edge technology.

Apply exclusively at getonbrd.com.

• Design, develop, and maintain Backend services with a focus on Golang and Node.js.
• Architect scalable APIs, microservices, and event-driven systems.
• Build and maintain robust CI/CD pipelines and Kubernetes-based deployment infrastructure.
• Implement and monitor logging, alerting, and observability systems to ensure service health and rapid incident response.
• Balance engineering trade-offs with business needs to deliver pragmatic, customer-focused solutions.
• Champion best practices in Backend architecture, system security, performance, and maintainability.
• Collaborate cross-functionally with Frontend engineers, product managers, and DevOps to ensure seamless system integration.
• Lead architecture reviews and propose technical improvements grounded in real-world scalability and performance.
• Mentor engineers on Backend design patterns, infrastructure operations, and production readiness.

What Success Looks Like:

• Backend systems are reliable, scalable, cost-efficient, and maintainable under real-world usage.
• Infrastructure and service architecture evolves proactively to meet the needs of product growth.
• Monitoring and observability tools are in place, actionable, and support rapid response to incidents.
• Engineering practices are improved across the team through mentorship, reusable patterns, and thoughtful leadership.

What We Avoid:

• Avoiding ownership of infrastructure, monitoring, or deployments.
• Over-engineering or introducing unnecessary complexity.
• Designing systems without regard for real-world scalability or operational cost.
• Failing to communicate Backend changes clearly across teams.
• Reacting to reliability issues rather than proactively preventing them.