We work with people and organisations that have ambitious missions. With software delivery at our core, we specialise in digital product and service innovation. We help businesses make the organisational changes (advisory, delivery and service models) required to be successful in the digital era.
ThoughtWorks currently has 0 opportunities.
Select the following options:
If you’re interested in working at ThoughtWorks, understanding when they have opened up applications for their graduate programs, graduate jobs and internships is helpful knowledge to have so you know when you might need to apply. Use the below information to see when ThoughtWorks hires graduates, but more importantly what graduate degree’s and other student attributes they target for their jobs.
If you have stumbled across us and have no idea who we are, ThoughtWorks is a global software consultancy with 7000+ employees spread across 43 offices in 14 countries.
We’re also an amazing collection of humans, hired for our passion, integrity and special powers. The company was founded as a social experiment – what happens when you hire really smart, passionate people and set them loose on really tough problems? More than 25 years on, this collection of people has helped shape the IT industry.
It’s not that straightforward though. If you ask anyone who works here what we do, they’ll give you a different answer. ThoughtWorks is very much what you make of it, and your experience will be shaped by the projects you’re on and the people you work with.
Since we started, in a basement in Chicago over 25 years ago, we have made many mistakes, and have learnt a lot about how to build software, but more importantly, how to work effectively. We’re fanatical about helping our industry to get better and we do this by writing books, blogging, and talking at conferences. But the biggest way that we help is the work that we do with our clients.
ThoughtWorks offices all over the world hire and support passionate graduate consultants. Graduates can take training courses, or develop their skills as a consultant in guided programs that aim for continuous learning and support in a safe-to-fail environment.
Joining ThoughtWorks straight from university is an amazing experience, and it’s definitely not your average entry-level program! Yes it's designed for people with little-or-no work experience, and those moving into the world of software, but that's where the similarity ends. You won't have months of shadowing and being treated like you know nothing and you’ll be working with real-life clients in your first couple of months.
A core part of the experience is spending five weeks at ThoughtWorks University (TWU) with ThoughtWorkers from all over the world, discovering the values, practices and principles that have made ThoughtWorks successful. This is an intensive, hands-on experience, learning how to build working software from week one. Your dedicated trainer is an experienced ThoughtWorker and will support you through your learning journey. By the end of the program you'll have real experience in what you do. TWU won’t teach you everything but will provide you with the foundations to become a successful consultant with us.
TWU takes place at a TWU campus in India or China. It's here that you can experience undiluted ThoughtWorks, eat more delicious food than you'd ever thought possible, and live communally with your fellow trainees , completely immersing yourself in the ThoughtWorks culture.
There are 4 intakes each year - February, April, August and October!
1. Online Application
All we need is a CV and Cover Letter. Tell us about yourself - your educational background, any prior work experience (tech or not), internships, part time roles, community involvement and anything else you wish to share with us.
2. Phone Conversation
Our recruitment team will schedule a quick chat to find out more about you and why you are interested in joining ThoughtWorks. It’s also an opportunity to find out more about us and our opportunities.
3. Technical Assessment
Here we will assess your technical foundations. We don’t expect you to be an expert but we want to ensure we’re able to provide you with the right level of support with what we offer at TWU.
4. Pairing Interview
Meet our ThoughtWorkers for a Paired Programming interview. They will collaborate with you on a code to better understand your capabilities and potential. This is an interactive session and you might be able to teach us something too!
5. Cultural Conversation & Presentation
This is less focussed on your technical skills but more about you as an individual, as a peer and as a potential ThoughtWorker. We want to really get to know you and what’s important to you. We’ll also give you a topic to present on. You are free to prepare slides, sing, do a dance, bring props...it’s up to you!
6. Offer & TWU
Welcome to the ThoughtWorks family and get ready for your TWU adventure!
Safira joined ThoughtWorks as a Graduate in 2018. We asked her a few questions about her journey.
What does a Graduate Software Developer actually do?
When I think about what my responsibilities are, I think about myself putting on two different hats:
- Being a graduate, I have the opportunity to learn on the job from some of the smartest people in the industry, while focusing on adding as much value as I can to ThoughtWorks. This could be addressed by being involved in an initiative like LevelUp or by pitching into internal office projects (software development or otherwise).
- As a software developer, I believe that it is my job to contribute to delivering technical solutions to business problems while advocating for software engineering best practices and agile ways of working.
When merged into a single role, I think my main focus as a graduate developer has been to be a team player and to continue to upskill technically (in programming or otherwise).
What does your typical day look like?
Coffees are crucial to start my morning. More often than not, a stand up would shortly follow that, and if it’s a Monday, I would send out an email with a list of meetups that are happening in Melbourne that week.
That said, I think those are probably the most constant routine of my days, because they really vary, regardless of whether or not I am on a client. Sometimes I would find myself spending the day watching tutorials on a new technology that I am interested in. Other times, I would find myself pair programming, doing a spike, or fixing tech debt. As a graduate, I tend to go about my day reactively, offering a helping hand where needed as opposed to having a solid, personal agenda to follow.
What’s the most challenging part of your job?
The most challenging part for me is actually something that I love about my job as well, which is the fact I more or less get to define my own career path. As a graduate developer, it is my job to define what I can bring to the team; not in a “are you good enough?” kind of way, but more like a “what are you so passionate to learn about that you’d do anything to master it?” way.
With the amount of context switching and all of these exciting technologies around me, I find it a little difficult to find that path, one that allows me to bring the most value to ThoughtWorks first and foremost, but also one that allows me to do things that bring me the most joy.
What’s your favourite part about your role?
The constant exposure to new technologies and ridiculously smart individuals. I love the feeling of being surrounded by people who are passionate about what they do and are more than happy to share that with others. Perhaps it’s the fact that I am quite a novice in this industry, but I feel like I have been learning something new every day that I come to work.
In the short year that I have been at ThoughtWorks, I have been involved in engagements that required different specialisations (e.g., infrastructure, front-end development, data visualisation), not to mention knowledge of different domains, and I was always exposed to new tools and frameworks every time.
What are you measured on?
I ask myself the questions, “How have I been adding value to the team? What tangible evidence can I collect to support that?” To answer those, I usually ask for feedback directly from the people that I work with. It’s not just about how strong my technical skills are, (although that is quite important), but it’s also about my development as a well-rounded consultant.
What makes a good Graduate Software Developer?
Having the ability to learn and adapt quickly is probably one of the most important traits. One piece of advice that I always get as a graduate is to hang on to the core software engineering principles, design patterns, and best practices instead of clinging onto a specific tech stack.
I love programming, I really do, but I think it’s also important not to forget about being a consultant as well. My job is not just to write code; it also involves facilitating a workshop, speaking in a showcase, conducting user testing sessions. Being proactive, interactive, and taking initiative are good traits to have as a team member, as well as having the courage to challenge the status quo where appropriate.
How do you manage different stakeholder needs?
As a graduate, I haven’t been exposed to situations where I handle external stakeholders frequently, but when I do, I would identify what role that stakeholder plays in that particular situation and who else is involved in it. These questions help me to identify whether I should involve a more senior ThoughtWorker in the conversation. When the situation requires me to handle it myself, I would express honestly and transparently about what I’m currently doing, what the blockers are, and what I think needs to be done in the effort of satisfying their needs.
On your current project, what has you most excited?
The chance to stretch both my consultant and developer muscles. I’ve had the opportunity to interact directly with potential end users of the product while having the creative liberty to code a prototype (using React!).
I love being a consultant because…
Switching contexts excites me; I believe no two engagements have been the same for me so far. I love playing that puzzle of how to best design/develop/synthesize a solution to solve a specific problem.
We are ThoughtWorks… A community of passionate individuals whose purpose is to revolutionise software design, creation & delivery, while advocating for positive social change.
Wherever we are in the world, ThoughtWorkers share the same cultural characteristics and imperatives. We come to work as ourselves. We enjoy each other’s company. We value honesty and transparency. Appearances and backgrounds aren’t important to us; ideas and doing the right thing are.
We come to work as ourselves. We encourage and support each other. We value honesty and transparency. Ideas and doing the right thing are more important than appearances and backgrounds. We abhor and reject discrimination and inequality and promote diversity in all its forms. We proudly, passionately and actively strive to make both ThoughtWorks and our industry more reflective and inclusive of the society that we serve. Our Code of Conduct reflects our values and outlines how we conduct ourselves and treat each other.
We are seeking graduates with a real PASSION for learning that are CURIOUS and often CHALLENGE the status quo. Attitude, aptitude and integrity are central to all successful applicants.
In the past ThoughtWorks has made great strides in increasing diversity at all levels, from graduate hires to senior leadership, through a variety of programs and approaches.
Today, we stand with those committed to driving real change to make technology reflective of the world around us and building a more equitable and inclusive future for all technologists.
Gender diversity is something we care about in particular. Australia stands out across our global regions at 46% for the last few years. As a team, we continue to prioritise diversity in our hiring activities and ensure that we continue to have a diverse representation of candidates throughout our hiring pipeline.
Fostering equality has long been a strong value of our business. We have undertaken a program of intentional focus and investment on the diversity and inclusivity of our workforce. We applied a deliberate diversity lens across all of our business decisions and processes and built that way of thinking into our ongoing operations and behaviours.
Introduce yourself to our community!
My name is Kirstyn and I am a Graduate Developer at ThoughtWorks. I started in batch 68 in October of 2019. I atteneed TWU in Pune.
How much coding experience did you have before attending TWU?
Before starting at ThoughtWorks and going off to TWU, my experience with coding was minimal. I majored in UX/UI design at university and so the coding I had done was mostly front-end web development. I felt that I was at a disadvantage to the people who studied computer science for instance. As soon as I got to TWU I realised that everyone was at different levels of experience and ability, some being completely new to programming and others having some work experience already.
What was your experience at TWU like?
TWU was an amazing and enriching experience, we learnt all the agile processes and practices while experiencing how an ideal agile project should be. It was a super effective hands on learning approach and we had so many resources available to us, for example the amazing trainers that were there whenever we needed help or guidance. It was amazing to have a safe environment to try new things and practice the skills we were learning.
Being able to work with grads from all over the world was a big bonus. We all built such strong friendships and now we all have a network of colleagues from around the world! (best believe I will visit them all).
What have you been working on post-TWU as a Graduate Consultant?
I was on a client project for just over 3 months working with a team to build a mobile application. During this time I was able to apply some of the things I had learnt at TWU while learning new technologies and skills.
I was on the beach (TW term for when you’re not on a project) for a while after my engagement ended and I took the time to do some self-learning and got involved helping out where I could.
How did you adapt to remote working this year?
The shift to work from home was difficult at first. Not having the casual conversations and active movement was the biggest struggle for me. When working in a project team and pairing, the remote work has worked well, but being on constant zoom calls means that you end up sacrificing the social calls to get away from the computer screen. When on the beach and doing a lot of individual work, work from home can get very lonely and demotivating very quickly. I find that having casual zoom catch-ups helps a lot.
What are your tips for any Graduate starting their career?
All graduates add value even if you feel you don’t know as much as everyone else. Don’t doubt yourself, we all start from different levels of experience.
Never be afraid to ask questions and seek advice from others. We all struggle with similar things.
When working from home it's hard to meet people. Don’t be afraid to just message or schedule a casual catch-up to meet other people in the company.
At ThoughtWorks you are Free to Make Your Mark, and part of this is coming to work as yourself.
We don’t have a dedicated LGBTQI+ program in ThoughtWorks Australia because we don’t need one….it’s part of our DNA. We are an inclusive employer - all ThoughtWorkers are encouraged and empowered to come to work as ourselves.
Everyone is welcome here. This is not just policy. This is practice.
We believe that no matter who you are or how you identify, you deserve respect, empathy and equal opportunity to succeed. We work hard to ensure everyone at ThoughtWorks—and everyone we work with—is treated this way.
We are also one of only a handful of Australian companies (and the first ThoughtWorks country) with a dedicated policy and guidelines in place for supporting trans and gender diverse employees.
The goal for each is clear: to make ThoughtWorks a better home for all.
A Grad who started their journey remotely
Introduce yourself to our community!
Hi I’m Eu-Loong, I’m originally from London and did a career change from Investment Banking into coding last year where I attended a Full Stack coding bootcamp and applied to ThoughtWorks (TW) as a graduate developer consultant in Oct 2019. I joined remote ThoughtWorks University (TWU) APAC in April 2020 as part of TWU #70.
How much coding experience did you have before attending TWU?
I completed a 9 week Full Stack Web Development bootcamp with Le Wagon here in Melbourne in June 2019 and continued my self study until I started with TW.
Before attending TWU I had to complete a coding assignment to assess my level of coding knowledge and working practices. You get assigned a reviewer from your office who helps to provide feedback and passes on their assessment to the TWU core team.
One of things I found reassuring was that you are not judged on your coding background and the focus is on your potential as a developer and how you can become a better developer.
How did you adapt to remote learning for TWU?
In terms of my physical setup, I had to make sure that I had a good chair and that my screens were at the right level as I knew we would be in front of the screen for most of the day. I was lucky that I could use my spare room as an office so having a quiet space away from distractions is highly recommended for learning. I also made sure that I could tether to my phone for the times when my internet connection was a bit unreliable.
I had already gone through remote onboarding at TW the week before TWU and this was a good way to practise using Zoom and working with others remotely.
How would you describe your experience at remote TWU?
It was challenging and intense but fun and rewarding.
The week before TWU was spent onboarding - getting our laptops set up and gaining access to the team resources online whilst balancing this with the first week of remote induction at TW.
As part of TWU APAC my cohort consisted of trainees from Australia, Singapore and China. Trainees in North America, Latin America, Europe and India were in a separate cohort. To match up time zones between Australia, China and Singapore we started at 10am and normally finished around 6:30pm.
We all worked as part of a cross functional agile team consisting of a mix of Developer (Devs), Business Analysts (BAs), Experience Designers (XD) and Quality Assurance (QA).
Each team had two go-to trainers, normally a BA/QA trainer and a Dev trainer. Different trainers would also pair when delivering the lectures and it was a really good way to see pairing in action.
The daily routine normally consisted of a TWU wide lecture in the morning followed by hands-on lessons in our teams and then we would spend the rest of our day working on our client engagement project.
We had regular breaks during lessons and used Zoom for all of our meetings and lessons, the core TWU team put a lot of effort into making the content remote friendly and leveraged the tools available in Zoom.
In our teams we also would organise team activities after hours to help connect and for team building. Also in our end of day team sessions we shared our personal journeys to TWU, it was a really good way to gain some insights into everyone’s backgrounds.
How did remote TWU benefit you as a Consultant?
It helped me to practice patience and active listening.
When pairing remotely you can’t point to the part of the screen you’re talking about or rely on non-verbal cues as when you are physically co-located.
We all had to be understanding and made use of tools such as on-screen annotations in Zoom and to make sure we were specific in our verbal descriptions.
Even though we didn’t have the full fidelity experience of travelling to India or China, I was still able to build a strong relationship with my team and we still chat remotely.
What have you been up to since finishing TWU?
Well, it’s been pretty busy!
After a few days after returning from TWU I went straight onto a 3 week Infrastructure and Data fundamentals course to learn about AWS, Terraform, Docker, Kubernetes, Python, Data Science, Data Engineering and Machine Learning.
I’ve also been continuing my self study on Java and Test Driven Development (TDD).
There have also been remote catch ups with other TWers and getting involved with various grad activities.
What are your tips for any Graduate starting their career remotely?
It’s just too easy to blend into the background whilst working in the current remote situation (you can’t even go to meet someone face to face for a coffee).
Make yourself visible by getting in touch with people to build your network within the company - book catch ups with them and ask them about their experience at the company. If there’s something you don’t know or are unsure about, just ask; people will be always willing to help.
Volunteer your time to help out on activities and ask to shadow or pair with someone on a piece of work.
Lastly, if you see things that need improving - make some suggestions or build your own solutions!