What does a Principal Software Engineer do?
As per the definition,
“A Principal Software Engineer is a technical professional who develops, documents, and tests software to make sure software meets the business goals and end-user requirements. They carry out technical strategies to enhance efficiency and integration and provide technical guidance to the development team.”
And Why hire a Principal Software Engineer?
Principal Software Engineers offer an upper hand in the technical aspects of software development. We require them to:
- Make quick architectural-based decisions
- Prevent technical debt by foreseeing the correct technical approach
- Become great mentors to software engineers
Aditya, a new addition to the Tech Team brings 17 years of technical industry experience to MoEVing. He joined as a Principal Software Engineer, and we ensure that our product is in experienced hands.
Let’s hear from Aditya about his experiences and any learnings he can offer to people starting with software engineering roles.
- Tell us something about yourself and your connection with science?
Science and technology are Aditya’s best friends.
“I was always interested in science and technology as a child, and I decided to work in either theoretical science or applied science. Initially, when I gave the exam, I had to choose between aeronautical physics and computers, and I went ahead with computers.
I have enjoyed programming since school, and I was interested in its mathematics and theoretical aspects.”
Aditya has worked as a software engineer for prestigious companies such as Microsoft, Huawei, McAfee, Agoda, and Pitney Bowes.
Other than software and tech, he finds interest in music, traveling, reading, playing drums, and admiring nature.
2. What does a typical workday for a Principal Software Engineer look like?
Primarily, I work as a backend developer.
The feature I am working on is Driver onboarding, where drivers can register themselves through our MoEVing app.
Apart from that, I am looking at existing backend projects including, MoEVing charge, DevOps, and infrastructure on AWS and data warehouse, mostly on backend API and database, etc. These are some things I work on a day-to-day basis typically.
Also, I attend meetings with team members where coordination is required on the projects.
3. Who is your inspiration? What inspires you or motivates you to do what you are doing?
“Study nature, love nature, stay close to nature. It will never fail you.” — Frank Lloyd Wright
I was also interested in mathematics and fascinated with the works of Ramanujan, and he inspired me to study mathematics.
If I talk about MoEVing, we are in the EV space, which also inspired me as it would actually make a difference to fossil fuel-based automobiles. With the transition to electric vehicles, there will be an improvement in air quality and a reduction in environmental pollution.
4. According to you, why is technology valuable in today’s world?
Technology is valuable as long as it leads to evolution, consciousness, knowledge, and wisdom for the human race.
It gives a wide berth to people and expands their awareness levels. The information is readily available and accessible to people due to the internet.
There are other technologies like automobiles and aircraft which also contribute to world development.
5. What’s the coolest as well as the hardest part of your job?
The Coolest part 😎
We are making an impact from the ecological standpoint, most importantly, making life better for drivers and people working on the ground. It’s an honor to work for people and help in improving their lives. Apart from that, it’s always cool to learn new tech and meet cool people within the team.
The Hardest part 😓
Sometimes there are quite a lot of open issues that one has to keep track which is also a challenge in itself. In a startup environment, one has to be more dynamic. It can be a tedious task, but apart from that, it is all part of fun and games.
6. What technologies have you worked on, and what do you expect to work on in MoEVing?
So far, I have worked with various technologies. I started with Java, moved to C++, and worked for a long time with C sharp, Javascript, and PHP. Also, I have practical experience with react and MODJS.
And with MoEVing, I have a fair idea of the technologies and languages I will work on. I am working with Python on the backend. I might work with Javascript, SQL, DevOps, and big data in the future.
I expect to continue working on the same technologies and also looking for a chance to explore new technologies like Rust and other programming technologies in the future.
7. How do you like the work culture? What do you find most interesting about working at MoEVing?
I love the work culture at MoEVing. People are friendly and easily approachable. There are no barriers to communication.
We can work at a flexible pace. Apart from synchronization meetings, there is a lot of flexibility in how one arranges their space.
The environment is anti-corporate. The culture is dynamic that is intentional because we don’t want to move in a very rigid manner.
One advice on remote working,
In a remote environment, one has to be self-disciplined and proactive while communicating with others. It’s better to over-communicate than under-communicate. In face-to-face meetings, one ends up communicating all the time. So, we have to take initiative to do that in a remote environment.
8. What are some of the specific advice related to a career path in software engineering that you give the future MoEVers?
As for the career path is concerned, it is too early to say what one really wants out of their career. Sometimes, as time goes by, people change their opinion.
So, I would say, people should not make any pre-conceived notions and explore all possibilities and make an informed decision on what they see they can do down the line.
9. Any learnings you want to impart to the generation from your experience?
Be honest and sincere in whatever you do.
Do something and do it well, or don’t do it at all.
Everybody makes mistakes, the only thing is, one has to learn from them and never repeat them.
One should define what one considers success is. It won’t be something that other people think is a success. One’s definition of success would be different from others.
Go with what your heart tells you where other people may be saying something else, but you know what your heart says.
If you want to be a part of a leading team and grow along with experienced and supportive mentors, join us now.
