Showing posts with label Information systems. Show all posts
Showing posts with label Information systems. Show all posts

Tuesday, January 11, 2022

Ageism in corporate world : It’s a Goldilocks paradox

 Those of us who have been in the IT sector for any number of years have probably observed the Goldilocks paradox at work. According to the popular fairy tale, “Goldilocks and the Three Bears,” little Goldilocks tries the three bowls of porridge and sets aside the big bow as it is ‘too hot,’ the second as ‘too cold’ and eats the porridge from the third bowl that it thinks is ‘just right.’

Tech recruiters and hiring managers are like little Goldilocks, wanting their candidates neither too young, nor too old, just the right age. The media and analysts have been focused on the high turnover in IT sector, but a closer look shows how this Goldilocks paradox is playing out – the demand is highest for those with at least a few years’ experience in a specific technology, gradually tapering off for more experienced candidates who are likely to be higher paid, hitting a glass ceiling at the top.

One of the reasons for this is the cost to company (CTC) that candidates expect. Indian IT has evolved an archaic “Years of experience and salary” formula that recruiters seem to use, with an equally obtuse number of two-hundred thousand rupees for every year of experience. By this formula, a candidate with 10 years’ experience will be expected to draw two million in annual package, while the one with 7 years can expect only 1.4 million. Negotiating an exception can be a contentious and long-drawn affair.

Ageism at the bottom of the pyramid

Recruiters and their filtering software are quick to reject graduates with little or no experience, creating a vicious cycle – young techies unable to obtain relevant experience without the first job, while most entry level jobs require experience. A viral twitter post from Sebastián Ramírez (@tiangolo), the creator of FastAPI succinctly highlights this paradox

“I saw a job post the other day. It required 4+ years of experience in FastAPI. I couldn’t apply as I only have 1.5+ years of experience since I created that thing.”



The glass ceiling at the top

At the other end, the glass-ceiling for experienced (read older) tech workers is also equally pronounced. Most recruiters are unwilling to evaluate candidates with 15 or more years’ experience creating an implicit bias against older workers. Social forums like Quora, Reddit or even LinkedIn groups frequently debate the question over such ageism with a common theme: when is a person ‘too old’ to be hired at a tech company? Are folks in their forties or fifties considered ‘too old to hire’?

Having explored a job-change while in my forties after relocating back to India a few years ago, I am probably well-qualified to answer this question. My job-search was unique in another way – unlike many of my peers out to showcase their credentials in managing ‘large,’ teams, I was essentially selling my skills as an individual contributor, albeit one who could help organizations navigate a breath of technologies.

It took me a few months of serious networking, contacting hiring managers and recruiters before I began getting calls for interviews. The feedback was simple: my peers were all “IT Director” level folks who could showcase their project or team management skills; so, I had to emphasize my business partnering skills and the knowledge of a breadth of technical skills.


The way forward – get over the conscious bias


The IT industry is maturing, especially in India, where there are over 5 million people in the IT–BPM sector. The average age of professionals has steadily been increasing over the years. By some accounts the average Indian techie is between 27 and 30 years old, which also happens to be the sweet spot where the industry is seeing a hiring frenzy.

It is time for hiring managers and recruiters to set aside their blinders and look beyond the Goldilocks paradox. Doing so will not only ease the pressure on hiring; but casting a wider net for talent will also drive a more inclusive and diverse work environment.


Originally published in  Express Computers 

Monday, August 14, 2017

Enterprise Architecture 101: Digital Strategy Execution enabled by an ARB

A while ago, I had blogged a Pulse article about Digital Strategy Execution (ref link). This is a topic I continue to observe and reflect on since organizations continue to execute their corporate digitization strategies.

The Editor at Cutter Consortium reached out to me asking if I could expand on the topic, especially in the context of Architecture governance. This viewpoint - Digital Strategy Execution via Architecture Review Board (ARB) - was recently published as an executive update by Cutter Consortium.  I realize the report is firewalled, so for those without access to Cutter’s subscription, here is a detailed summary. I have also posted some of the diagrams from the report in a slideshare (link)
Enabling digital strategies requires CIOs, Enterprise Architects and IT leaders to engage with business stakeholders. Such engagement of IS with business stakeholders must be governed by the organization’s processes, operating model, and technology governance to ensure robust, scalable architectures. The resultant roadmaps should also be governed by a well-functioning ARB.

Digitization and Information Systems

There are lots of discussions and viewpoints on ‘digital strategies,’ and they must be contextualized for an organization. Examples of such user stories include medical insurance companies motivating consumers to video-chat with doctors, auto insurers offering “usage-based insurance” after analysis of driver data from devices on cars, and banks minimizing foot traffic at the branches while enhancing digital transactions. As an enterprise architect responsible for governance at a multinational organization, I had an opportunity to review several digital transformations. Most of them seem to fall into three distinct categories (see Figure):




  • Lights-on digitization (a.k.a IS led digitization)
  • Digital excellence
  • Customer-centric digitization

    Most lights-on digitization efforts - like migrating application platforms to cloud hosting, introducing new software as a service (SaaS), enhanced data management, automation of existing processes etc - are driven by IT leaders, who should take the opportunity to align these with other transformations.

    Technology and business leaders continually scan the external landscape for new and innovative solutions. Digital excellence initiatives include the introduction of innovative vendor solutions that can drive business growth. Examples include use of blockchain technology, tools to analyze big/unstructured data; speech recognition and interactive voice response (IVR) enabled processes, and incremental use of virtual assistants and transcription or translation services.

    Customer-centric digitization programs aim to enhance digital engagement with the company’s customers, business partners, vendors, suppliers, and other third parties. These initiatives require strong business insights and are generally sponsored and steered by senior executives. IT leaders facilitate ideation and technology foresight, and ensure seamless introduction of these solutions.

    Customer-centric digitization might also be designed to address threats from digital innovators. For instance, the travel and hospitality industry is reacting to disruptors like Uber, Lyft, and Airbnb. Innovations in robotics, Internet of Things, and artificial intelligence–driven planning and modeling are beginning to disrupt the existing ways of working in manufacturing industries.
    In the report, I expand the context of Architecture Governance (figure) and execution that requires executive support and an operational cadence. Digital strategies and roadmaps continually evolve and change in response to economic conditions, changing customer preferences, competitive pressures, and external market forces. Therefore, the basic design of an ARB should be simple but extensible. Please feel free to review the references:

    Thanks for reading! 
    Please share your views on Digitization & Governance. You may Like, Share, Tweet and Comment below to continue this conversation | Reposted from my Linkedin Pulse blog |

    Sunday, May 28, 2017

    IT Career advice from Mohan

    Here is a recent question from an online forum: What would you advise to a CSE undergraduate from India in the current scenario when Indian IT companies are laying off lots of employees?

    My response follows -

    Having spent the past couple of decades in the vibrant field of IT, my advice to CSE undergrads is simple: Be prepared to reskill yourself while staying grounded on the fundamentals.
    Advise like “re-invent yourself” and “constant reskilling” is an oft repeated mantra, so much so that it starts to sound clichéd.
    For instance, I started as a Windows developer (back when computing was ‘client server’) and switched to programming on mainframes (MVS, CICS, DB2 etc), learnt EAI, Integration and TIBCO and later moved to web-servers and middlewares before I morphed into an Enterprise Architect and continue to observe and learn about ERPs (SAP) Cloud platforms, SaaS customizations, integrations etc etc.
    Did I have to ‘reinvent’ myself every-time? NO. I was merely adding to my experience.
    If one has strong grounding in the fundamentals of computing, most of what one continues to learn is incremental and doesn’t necessarily involve a ‘reboot.’ For instance, the database-101 skills I used in DB2 are just as relevant as I review SQL and Big-data.


    What this means to you is the same: try to get a very good grounding in the fundamentals of computing because this is what you will continue to build on during your career.

    Wednesday, March 15, 2017

    Career Q&A on Enterprise Architecture

    Career Questions from an online forum: 

    Q1: How can I transition from enterprise architecture to business consulting?


    My response:  


    Interesting question; I say interesting since many people from consulting move to corporate EA.
    For this response, I will assume you are a corporate EA with some consulting background. While moving to Business consulting you will need to
    • Highlight expertise in functional domain - This could be expertise in domains like Finance, Supply Chain, HR or others that you may have worked on
    • Emphasize your consulting background - e.g consulting with projects and programs in your organization.
    • Demonstrate flexibility to learn and think on your feet
    Message me if you need further inputs.



    Q2: What positions can being a Java technical architect lead to?



    My response:
    Sorry to sound clichéd but it really depends on where you want it to lead. Let us look at two main kinds of jobs:
    • Consulting firms - A Java Technical Architect could grow into a senior Architect, Senior consultant or relationship manager, engagement leader etc. Along the way, you could pick up other technical skills in Big Data, AI etc etc
    • IT Shop at an organization - Let us assume, you join as a Java Technical Architect at a large bank. You could continue to grow in the technical track (towards Enterprise Architecture) and expand into other technologies being used in the organization, or grow in the management track
    As I said earlier, it really depends on where you want your job to lead to.