🎁 Antes de se candidatar, treine esta entrevista. Crie sua conta grátis no WorkMundi e ganhe um Treinamento de Entrevista no HelpsYouSpeak — sem custo, sem cartão. Quero meu treinamento →
Software at TRACTIAN The software department at TRACTIAN is at the forefront of innovation, crafting an integrated ecosystem that revolutionizes maintenance and process management. Comprising a dynamic team of experts, the department develops an all-in-one software solution that seamlessly combines predictive maintenance capabilities with a comprehensive Computerized Maintenance Management System (CMMS). This visionary approach empowers maintenance and process teams with a unified platform, enabling them to proactively predict equipment failures, optimize maintenance workflows, and enhance operational efficiency. In daily work the software department drives the convergence of cutting-edge technology and maintenance excellence to propel businesses toward unparalleled success. What You'll Do As a Staff Backend Software Engineer at our company, you will be instrumental in shaping the foundation of our backend infrastructure. You'll play a critical role in building a scalable, resilient, and high-performing platform that supports our innovative product offerings and delivers an exceptional experience to our users. Responsibilities Work with engineers & technical leaders across the company to ship products on strong foundations. Build high quality end-to-end product experiences for platforms. Improve engineering standards, tooling and processes. Develop and lead the team to execute against both short-term and long-term roadmaps. Make effective tradeoffs that consider business priorities, user experience, and a sustainable technical foundation. Identify, scope, and lead large technical projects, laying the groundwork for early-stage products to iteratively evolve and scale, and taming complexity and shoring up reliability of existing systems. Requirements Bachelor’s degree in Computer Science, Engineering, or a related technical field. 5+ years of backend development experience, with a strong focus on platform and infrastructure roles. Deep expertise in backend programming languages (Go, Node, Python). Experience in managing state in distributed systems and understanding of microservices architecture. Proficient in backend testing frameworks and knowledge of system testing best practices. Experience working across engineering teams and other functions in building alignment, driving decision making, and communicating transparently. Experience mentoring and helping in the development of engineers and peers. Bonus points Track record of leading backend platform development in a high-growth tech environment. A portfolio or GitHub repository showcasing backend architectural expertise and contributions to middleware, APIs, or server-side applications. Fluent in English.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.