Infrastructure Lead (DevOps Champion)

ThoughtWorks is a global software consultancy, made up of around 4,000 passionate technologists across 14 countries. We specialize in strategy, portfolio management and product design, combined with digital engineering excellence.

Here’s what it means to be a Tech Lead at ThoughtWorks:

ThoughtWorks is a global software consultancy, made up of 4,000 passionate technologists across 14 countries. We specialize in strategy, portfolio management and product design, combined with digital engineering excellence. Infrastructure (DevOps) Tech Leads at ThoughtWorks work with a team of infrastructure developers to help our clients create a vision for their delivery infrastructure and a roadmap to implement that vision. As a servant leader, you’ll foster an environment of respect and trust that empowers teams to deliver their best work. Tech Leads aid in the development of team members by removing blockers paving the way for success in each project. This role will require you to draw on your passion for technology, hands-on coding experience and knowledge of latest industry trends in order to influence clients to reimagine the technical landscape for their large-scale enterprise organizations.

As consultants, the specifics will change with every client and engagement. But all of our tech leads are able to analyze, research, discover, and champion solutions for major technology-led initiatives that are transformational for our clients’ businesses operating in large and complex environments.

As an Infrastructure Tech Lead here’s what we’ll be looking for you to bring:

  • Experience with Amazon Web Services or other Public Cloud providers, including work with infrastructure components such as networking, firewalls, DNS, and storage.
  • Operational experience with observability practices and tooling such as EfK, Prometheus, and splunk.
  • Knowledge of the tools, frameworks, and languages used in the TDD of infrastructure as code, such as inspec/awspec, terraform, ansible, packer, vagrant, and python.
  • Familiarity with Docker, Kubernetes or other Container technologies, including commercial offerings and the components necessary to implement containerized workloads.
  • Knowledge of Continuous Delivery practices and tooling, including:
    • Application and infrastructure pipeline design
    • Infrastructure testing and monitoring strategies,
    • Load and performance testing,
  • Awareness of identity and authorization architecture and tools.
  • Awareness of release management practices.
  • Awareness of API development practices.
  • Experience working in agile environments.

From a technical perspective, a tech lead is responsible for:

  • Building a shared architectural and technical vision
  • Advise on implementation architecture decisions, and articulate the pros/cons of different approaches
  • Identifying and addressing technical risks
  • Ensuring that the team understands key system quality attributes
  • Keeping a sharp focus on team productivity, code cohesiveness and consistency
  • Finding the right balance of contributing your own code to the project. It’s important to keep coding to stay grounded to the work, but you’ll need to know when to put it on hold to address more urgent matters and remove roadblocks so that the team as a whole can remain productive.

And on the non-technical end, it means:


  • Leading and mentoring a team. Focusing on team cohesiveness, and finding ways to help each team member connect with each other
  • Encourage people sharing knowledge across the team
  • Connecting developers with opportunities for them to grow, and allowing them to take measured risks

Managing the client:

  • Building great relationships with people outside of the development team including people like Product Managers, Marketing, Sales and CxOs
  • Spending time with a new client on a deep technical review or a complete organizational review, helping them to understand the potential that technology has to solve their most pressing problems
  • Being involved (and sometimes leading) planning sessions with the client
  • Helping non-technical stakeholders to understand technical concepts


Additional Resources:

What I Learned While Becoming a Tech Lead

Three Common Mistakes of a First Time Tech Lead

Five Tips for Being an Effective Tech Lead 

Here’s a little bit about how we work:

  • As consultants, we work on projects across many different industries and bring learnings from one domain to another.
  • No two projects are the same, but the one constant is a team of interesting, curious, and dedicated technologists committed to building the best possible software for our clients, and fast.
  • We want our consultants to feel empowered to make decisions, challenge the status quo, and leverage technology to its fullest. To be most effective, we practice pair programming and highly encourage collaboration and feedback. Our teams are non-hierarchical and everyone truly has a voice.
  • We most often work on site, in our clients’ offices, so that we’re completely immersed with their technical teams.

Here’s what it means to be a “ThoughtWorker”:

  • As a ThoughtWorker, you’ll be a key player in helping our clients all over the world build great software and leap ahead of, or even redirect, their market.
  • ThoughtWorkers will tell you that this is a place to be yourself; where you’ll be empowered to contribute your talents, knowledge, and opinions as both a technologist and a human being.
  • You’ll be joining a for-profit company, but we think of ourselves as for-profit, with purpose. Outside of our day to day work with commercial clients, we believe that we are most impactful by partnering and supporting lots of organisations who are dedicated to social and economic justice.
  • We’re big on feedback and development. In our feedback-rich culture, everyone is required to play the coaching role to an extent: our senior consultants mentor and provide guidance to newer members of the team, and everyone is encouraged to solicit constant feedback from their teammates throughout the year.
  • You’ll develop your career outside of the confinements of a traditional career path by focusing on what you’re passionate about rather than a predetermined one-size-fits-all plan.
  • Constant learning is celebrated and even required. We’re proud that ThoughtWorkers have written over 100 books on tech, and you’ll find ThoughtWorkers blogging, writing, and speaking at tech conferences around the world.

An important note:

We work almost exclusively on customer site providing a mix of delivery and consulting services, so you’ll need to be be flexible about travel, and willing to travel extensively as part of your role.  Many of our consultants travel every week and fly home for weekends. We do everything we can to make life here as easy as possible and do our best to take people’s personal situations into account.


It is the policy of ThoughtWorks, Inc. to provide a work environment free of discrimination. The Company will take affirmative action to ensure applicants and ThoughtWorks employees are treated without regard to race, color, religion, sex, national origin, ethnic origin, veteran status, family status, disability, sexual orientation, gender expression, or gender identity.  This also includes individuals who are perceived to have any of the aforementioned attributes.  ThoughtWorks will adhere to all federal, state, and municipal laws and regulations governing employment.



Meet Some of ThoughtWorks's Employees

Amanda S.

Senior Developer

Amanda develops software for various client projects by traveling to client sites and collaborating with fellow ThoughtWorkers to build viable software solutions.

Molly D.

Lead Developer

Molly writes code for ThoughtWorks and mentors others in how to become effective software developers. She works through problems with her team to give her clients the best possible solution.

Back to top