Enable javascript in your browser for better experience. Need to know to enable it? Go here.

Infrastructure or as some call it "DevOps" is about promoting a culture where operations and developers work very closely to achieve a common goal, for example to build & run stable software applications. It's about empowering cross-functional teams so that they can take ownership of their parts of the infrastructure. 


Thoughtworks infrastructure developers are responsible for the knowledge, ideas, and hands-on implementation skills needed to deliver and run software services. They help our clients adopt DevOps approaches, break out of rigid, traditional ways of working and move to a more customer-focused and agile approach.


At Thoughtworks, Infrastructure Developers have a hands-on involvement in building CI/CD ecosystems, infrastructure automation using practices like infrastructure as code and infrastructure support services such as logging, monitoring & alerting.

Even with the best tools, DevOps is just another buzzword if you don't have the right culture."

Martin Fowler, Chief Scientist

Web Conference: Infrastructure as Code

Infrastructure Code Projects Are Terrible 

by Kief Morris

Why is nearly every infrastructure project I've run across a big ball of mud? We're still in the early days of infrastructure as code tooling, so we're struggling with messy glue code, configuration files, and weird custom scripts and tools. What can you do on your project to cope with the current state of tooling? And what should we, as an industry, do to level up?

Your Dashboard sucks - and how to fix it

by Moritz Heiber

Take a look at your desk. Now take a look at the wall. Now take a look at your hallway. If you're working in IT delivery or infrastructure chances are your eyes have at least met one dashboard, if not more, while your gaze was wondering.

How often do you actually look at said dashboard(s)? How much of the information it presents is tailored towards you? Is the dashboard actually helpful... is it... valuable... to you?

Third-Party Infrastructure as Code

by Raquel Guimarães

While implementing cloud Infrastructure as Code you might have come across the problem of dealing with third-party resources. This is most common in complex environments where most of the resources live in a cloud provider (GCP or AWS for example) and there are some SaaS solutions to integrate with (Datadog and Pingdom for example). In this talk we will expose the problem and explain a solution that is currently being used by one of our key clients in Spain.

Podcast suggestion

In this episode of the Thoughtworks Podcast, Neal Ford explains to Johannes Thönes what architectural considerations can be derived from the DevOps movement.

This episode is a quick introduction to what Microservices are, what kind of architectural principles can be used to implement them, what a good test strategy for microservices can can look like. We also explain why you should have a continuous delivery practice running before starting to develop Microservices.

Insights Articles

Meet some of our Infrastructure colleagues

Khushboo Saxena
Khushboo Saxena

Throughout my time at Thoughtworks, multiple infrastructure projects exposed me to a breadth of functions, technologies, clients and industries all packed in a professionally challenging and intellectually stimulating environment. There are no predefined templates or boundaries and you could be surprised how autonomous and entrepreneurial our jobs at Thoughtworks might look despite being in client facing roles.

We have an amazing support system embedded within Thoughtworks in the form of sponsors and global developer communities. A culture of sharing honest and constructive feedback is the foundation of all the interactions that enables an environment of trust where people from all cultural and professional backgrounds can easily transition and settle into. I have immensely benefited on this journey and couldn’t imagine being on the same learning curve if I had ended up in another firm.

Katharina Dankert
Katharina Dankert

Why Thoughtworks? The paradigms of continuous deployment and delivery, and of applying good coding practices such as testing to infrastructure code was what I had eagerly read about and aspired to from a technical perspective. The thing that resonated with me on a career level though was Thoughtworks’ dedication to cooperative problem solving. I wanted to think, plan and accomplish tasks – whatever they may be – as a team. To work in a culture of continuous, cooperative learning was the deciding factor.

At Thoughtworks I can just do. Whatever it may be, I can plan a project, a talk, a conversation, a text, ask for interested peers and pairs and get cracking. There is room to be active, not just reactive, especially with regard to issues close to my heart, while not having to do it alone, is what makes me feel empowered and in control.

Matthias Scholz
Matthias Scholz

I am a passionate computer scientist and technology enthusiast. I love working with people in teams to build complex systems led by simplicity. Infrastructure topics, in general, are an interesting area since the rise of advanced APIs in conjunction with services CSPs are offering. At Thoughtworks specifically, it is the variety of clients,the broad spectrum of possibilities and technologies that interest me most.

What makes Thoughtworks special for me is the risk of making errors but using these as a source for learning. It is the sharing of mistakes and gained knowledge. It is talking about ideas even if they sound unconventional. It is being opinionated while being open to other points of view.

Moritz Heiber
Moritz Heiber

The most interesting part about Infrastructure Development at Thoughtworks is the variety, both of project challenges as well as opinion and experience within the Thoughtworks business portfolio and community. I've probably tried over a dozen other languages I had never considered before (or, without Thoughtworks, ever would have) and it helped me gain a better understanding of the overall problem space I was in and turned me into a better consultant.

I’m proud of being a Thoughtworker because it is a community I get to be a part of, that shares my values and actively encourages a culture of openness, courtesy and understanding, as well as a company that champions diversity and is actively engaged in using technology for creating a more economically just world. A safe environment has been created through Thoughtworkers and their considerate practises, as well as a commitment and focus on creating a diverse and engaged community of passionate technologists.

Interested in joining the community? Apply now!

Sorry, there are no jobs available