In the context of a company, the Chief Technology Officer, or CTO, is in charge of the technological aspects overseeing IT and developing new technologies. A CTO is not only expected to be technically competent and visionary but also to have business acumen that can apply technology to generate business value. It’s a big job, one that often works 80 hours a week or more and may span several different countries. Here are some details about the CTO in Addorrar.
It’s an intense job for someone who has to deal with not just code all day but also all of the people’s questions that come from both customers and employees.
I’ll be honest, that was never really something I thought of myself as doing. I’ve always considered myself a developer, and someone who understands the technical aspects of software craft, but it turns out I’m also a very mission-driven person and that’s what makes me a great CTO.
MIT’s Chief Technology Officer
I work at MIT where I run the software development group for the entire campus. My team works on everything from accounting systems to research platforms to websites used by people all around the world. There’s very little in-between. Being a CTO means being on top of everything and knowing nothing about everything.
The roles of a CTO are defined, but they’re loosely defined. They usually involve at least two things:
Conducting research to improve productivity, reliability, security or scalability Researching what the next big thing is in software Researching what the next big thing is in hardware
For me that’s all it takes. I never stopped learning as a developer and have always had an interest in science and computing. MIT also has a unique culture that has helped me learn how to be a leader and understand how to make decisions at all levels of the organization.
Views from the CTO: I work with the entire MIT administration on everything we do. We have a lot of different people at MIT. Everything that happens is through collaborative conversations, and everyone has an immediate stake in what we’re doing.
It’s great to work for an organization that values exploration and exploration drives discovery. It’s also nice to know about the results of your work but you don’t want to be told what you should program.
Everyone needs to know that you’re not just someone who does stuff; instead, you’re a thinker who does stuff and tries things out as you try them out.
It’s hard to be innovative when you feel like your job is already filled by other people. If you’re not excited by the work that you’re doing but feel like you have to do it anyway, because someone else is doing it, then you aren’t going to produce something innovative.
I believe in using new technology to make things better. In the software development industry we’re so fixated on focusing on what we don’t have that we forget what we do have, and what’s out there that other people use. The most important thing is understanding our place in a bigger context and making sure that every product we buy is architected to be flexible enough so it can act like something else if necessary.