I’ve been working as a software developer for 15 years, specialising in Salesforce development and mentoring for the past 8 years. I joined Triad at the beginning of July 2025 and have been working as a Salesforce Technical Architect since then.
Specialising in Salesforce
I became a Salesforce Technical Architect through years of hands-on experience, continuous learning, and a strong interest in designing scalable, reliable systems.
My career began as a software developer, where I built a strong foundation in coding and problem-solving. I gradually took on more responsibility in system design, integrations, performance optimisation, and technical leadership.
As I specialised in Salesforce, I progressed into a Lead Developer role and later began mentoring and leading technical teams. With increased exposure to complex enterprise solutions, integrations, and platform strategy, I transitioned into a Salesforce Technical Architect role, where I now focus on overall system design and technical direction.
This is a typical career path for a Salesforce Technical Architect, as most architects begin as developers and grow into the role through experience and leadership.
A common path is:
Junior Developer → Mid-Level Developer → Senior Developer → Technical Lead → Technical Architect.
However, there’s no single fixed route. Some professionals move into architecture from consultant or solution designer roles. What matters most is gaining deep technical expertise, strong problem-solving skills, a positive mindset, and the ability to understand both business needs and technical constraints.
Shaping the core architecture
I am currently working as a Salesforce Technical Architect on a compliance project for the Department for Energy Security and Net Zero (DESNZ). Before this, I worked with a Triad team developing a Salesforce portal for the Private Rental Sector Exemption within DESNZ.
As a Salesforce Technical Architect, I enjoy solving complex technical problems and receiving feedback from the team. The role can be intense, as it requires strong coding skills and excellent communication.
The most rewarding parts are shaping the core architecture, contributing to testing, setting up environments, supporting DevOps pipelines, and collaborating with others.
Problem-solving is part of the job
I consider myself a problem-solver. I can spend long hours helping others untangle technical challenges, and I’m always eager to support the team.
Making high-stakes technical decisions can be daunting. Designing a core architecture is challenging, with many moving parts and technologies. When something doesn’t work or isn’t accepted by the client, it becomes my responsibility to fix it, which can be stressful.
I use large language model (LLM’s) frequently to gather technical insights. Asking unusual or exploratory questions has become a hobby of mine.
The Triad team
I make a conscious effort to speak with my team regularly. Every day, I remind myself to message team members just for a chat. It encourages new ideas and strengthens collaboration. I strongly believe this kind of interaction is essential when we’re all working remotely.
At Triad, everyone is always willing to help. I’ve never been disappointed when asking a question. Support is readily available across the team.
What I have learned
I have learned many things over my career. Perhaps the biggest learning is the importance of enjoying what you do for a living. But if I had to give advice to someone starting out on a similar career path to mine, my advice would be:
- Keep track of changes and requirements. Without proper, methodical documentation, systems can quickly become chaotic.
- Write unit tests with the highest coverage possible.
- Use the right tools for the job. Don’t rely on the Developer Console’s anonymous window for coding or debugging. That’s a firm no.
- Communicate openly and regularly with your team.
If you have a question for Himanshu or the Triad team, please get in touch.
