“I get caught in nostalgia sometimes, remembering how things were before smartphones demanded unrelenting attention,” sighs Vamsee Krishna.
The digital engineer and senior VP at Qualitest recalls when MTV still showed music videos, computers were just a distant idea, and AI hadn’t changed everything.
“I was recently thinking about how product engineering is entirely unrecognizable from what it was 10, five, or even one year ago. When I stop and consider how quickly things change, it’s easy to understand how people can get left behind,” he said.
“Cloud computing, DevOps, AI, machine learning, and IoT have joined the party and are here to stay,” Krishna added.
To avoid getting lost in these changes, the thinks the industry has “to master our relationship” with them and make sure everyone, from veterans to newcomers, is best prepared to face this new beast and harness new skills to be better, more agile engineers.
“Every stage of evolution in the product engineering realm has required a new set of skills, and this is no different; rewriting the job description has been the only constant,” Krishna argued.
“From agile methodology to cloud computing and DevOps, developers have made quick learning a priceless talent. However, the required skills take a turn off the beaten path this time.”
Throughout the typical changes, innovations have required various technical skills and the ability to embrace new working methods and cultivate a mindset that transcends technical expertise.
Now, “collaboration is the name of the game,” Krishna continued, especially in small, self-managed teams that work together.”
Customer focus, accountability for product success, agile and DevOps integration, automation proficiency, and security and UX awareness, among others, have brought many more factors into play.
“Since product engineering now involves many teams from all business areas, technical and not, playing nicely has become a top priority,” he wrote in a recent TNS analysis.
“We all know the age-old jokes about IT staff and engineers being awkward and antisocial. The teams hunched over keyboards in the dark corner of the office. When asked for help, they would offer explanations that only one of their kind could understand, not exactly the pinnacle of communication skills. This engineer boogie monster was surely needed but not necessarily enjoyed,” Krishna recalled.
He added that no one probably thought that this group would soon be at the forefront of collaboration, but “here we are.
“Dirt paths between departments have become highways, and the dividing walls are crumbling.”
– Vamsee Krishna
Skills that were often overlooked are now in the spotlight, he pointed out.
“Engineers must now become masters of both the technical and the expressive worlds, on top of the new skills demanded by AI. Teamwork is everything, and excellent technical skills alone aren’t enough anymore.”
What Krishna sees is that many might find themselves clarifying concepts they never thought they would have to explain, vocalizing new needs, and relying on others in new ways.
“Complex technical concepts need to be articulated in ways accessible to non-technical stakeholders,” he noted.
Excellent cross-departmental communications skills and top-tier team working skills are an absolute necessity.
In a study in France, engineering students who participated in interdisciplinary thinking programs showed a higher capacity for exploring, analysing, and understanding complex phenomena.
These skills were considered “essential to prepare for their professional career.”
In other words, “take time to nurture this skill, and your career will benefit,” Krishna said.
“Adaptability and learning agility have become priceless in a world of rapid change. We must consider and empathize with many new perspectives, such as data-driven decision-making, user experience, and security,” he continued.
“Forgetting or undermining the importance of intentionally developing these skills can be serious; your work and abilities now affect more teams and areas than ever,” Krishna shared.
Collaboration
It may be a cliche but for an interconnected, digitised world collaboration and communication skills are increasingly important, particularly in large organisations such as banks and insurance firms.
“Many of us may feel lost by the idea of ‘just getting better at collaboration.’ So what can we do to succeed in this new world? It’s easier than you might think,” Krishna argued.
“Sometimes, we can picture collaboration as more complex and social. But in reality, it can be relatively straightforward: keep to your deadlines and promises; this will cultivate respect and nurture relationships.”
Also aligning on goals is vital, the industry veteran continued.
A study with Intuit Canada found that engineers collaborating in broad, unclear environments felt frustrated and uncomfortable, but once the missions became aligned, implementation was quickly achieved.
Alongside a new need for collaboration, a few other key areas have been affected by the latest changes that should be noticed, according to Krishna.
“With more projects moving across teams, security has become even more important,” he stated.
“Increased shared information can also increase cybersecurity risks; popular collaboration tools have become targets for data attacks.”
Education around data breaches and cybersecurity threats and how to prevent them needs to be integrated at every phase of the product lifecycle, he argues, adding that proper training and education have been found to decrease cybersecurity incidents.
“Everything and everyone has become more user-centric.”
– Vamsee Krishna
Therefore, the QA space also needs to keep User Experience (UX) and the principles of good design in mind during development.
“UX/UI designers should collaborate closely to help us make informed decisions that improve usability and accessibility,” he explained.
“UX professionals discussed how to best collaborate with product engineers and emphasized the importance of clear product roadmaps, user empathy maps, and robust feedback loops.”
Krishna was quick to add that: “Remember to keep everything in context with intentional product thinking. Understanding the market, competitive landscape, and evolving needs makes an engineer highly valuable.”
Different than before
Krishna said that some in the QA space have stayed the course through many waves of change and may see this “as just another step forward.”
However, he believes these innovations are different than any the industry has encountered before, and “we need to be especially vigilant,” as Krishna singled out two areas.
“First, leave no man behind,” he stated firmly. “Everyone responds to change differently, but reactions can usually be divided into three categories: enthusiastic adopters who jump right in, excited but unsure adopters who need guidance, and those who just feel lost.”
Second, “take a breath before diving in. New, exciting programs and strategies are exploding daily, and implementing innovations can sometimes be addicting,” Krishna stressed.
He remembers being amazed at teams from big companies who push out changes every five minutes.
“How exciting would that be if my team could do that? A competitor implemented a new AI program that looked shiny. But it wouldn’t align with my needs. Every business and its needs are unique. Comparison can be dangerous.”
He added: “Take a breath and look at your needs before diving into new systems.”
Finally, Krishna was keen to stress that the industry should not be too obsessed or solely focused on artificial intelligence. “AI Is not the only thing on the horizon.”
He explained that “as much as I’m impressed by how far things have come, I’m also excited about the unlimited innovations,” as Krishna said he is looking forward to IoT, AR/VR integrations, and blockchain involvement.
“I’m sure they’ll be here before we know it. On our horizon are new teams to collaborate with, new skills to learn, and new fears to overcome. Product engineering — or whatever we might call it in the future — is an industry that is born to change,” he concluded.
NEXT MONTH

DO NOT MISS

QA FINANCIAL FORUM LONDON 2024: RECAP
In September, QA Financial held the London conference of the QA Financial Forum, a global series of conference and networking meetings for software risk managers.
The agenda was designed to meet the needs of software testers working for banks and other financial firms working in regulated, complex markets.
Please check our special post-conference flipbook by clicking here.
READ MORE
- Automation is rapidly taking hold of banks’ QA strategies
- ‘Let’s redefine what quality assurance means’, says QA Mentor CEO
- Deep Dive: why do most AI testing projects fail to scale?
- Leapwork co-founder warns ‘AI is not in a state we can rely on’
- Ozone API eyes Australian banks with ProductCloud deal
Why not become a QA Financial subscriber? It’s entirely FREE
* Receive our weekly newsletter * Priority invitations to our Forum events *