LATAM Principal Software Engineer (Python/Go)

As a LATAM Principal Software Engineer at Praxent, you will lead development teams to ensure sprint commitments are met, architect complex systems, and establish DevOps processes. You will also conduct technical reviews to maintain quality, propose new processes to improve delivery, and evaluate potential candidates during the hiring process.

To qualify for the LATAM Principal Software Engineer position at Praxent, candidates should have 8-12 years of professional experience, strong proficiency in Python or Go, and a solid understanding of microservices and cloud-based deployments. Experience in people management and the ability to communicate technical concepts to clients are also essential.

At Praxent, the company culture is centered around autonomy, collaboration, and respect. As a LATAM Principal Software Engineer, you'll enjoy a healthy work-life balance and the freedom to work in environments that suit you. With core values that promote teamwork and personal development, you will find yourself surrounded by a supportive and innovative team.

Praxent is committed to supporting the professional development of its employees, including the LATAM Principal Software Engineer. The company provides financial assistance for classes, conferences, and other educational opportunities. Additionally, the culture of learning is encouraged through various development cohorts throughout the year.

The salary range for the LATAM Principal Software Engineer position at Praxent is between $3,791 and $4,830 USD per month. This range is based on role, level, location, and factors such as skills and experience, ensuring fair compensation for all team members.

Discuss specific projects where you've utilized Python or Go, emphasizing your contribution and impact on the project. Highlight any challenges you faced and the solutions you implemented to show your problem-solving skills.

Share a detailed process you use to plan sprints, allocate tasks, and maintain team motivation, including examples of how you ensure open communication and address any blockers swiftly.

Talk about the importance of conducting technical reviews, establishing testing protocols, and promoting a culture of accountability among team members to ensure high-quality outcomes.

Detail your familiarity with various cloud platforms, mentioning any particular projects where you've architected solutions using cloud services, and how that benefited the client's needs.

Discuss your mentorship style, including regular code reviews, pair programming, and providing constructive feedback, as well as specific instances where you guided someone to improve their skills.

Provide a clear explanation of microservices and their benefits. Share examples of how you've implemented this architecture in previous projects and the impact it had on the effectiveness of the software.

Illustrate your methodology for breaking down projects into manageable tasks, estimating timelines, and involving the team in discussions to ensure everyone is aligned and committed to the project plan.

Share your approach to simplifying complex technical concepts, using visual aids or analogies, and the importance of focusing on business value to ensure clarity and buy-in from the stakeholders.

Discuss the techniques and tools you use to diagnose performance issues, including profiling, monitoring, and conducting load tests, along with your strategy for implementing effective optimizations.

Relate your values to those of Praxent, emphasizing what excites you about their innovative approach in the financial services industry and how your skills will contribute to their mission and culture.