Millions Advisory

Millions Advisory Millions Advisory is a Search firm specialising in Lateral and Leadership hiring for Tech, BFSI, MFG & Engg, and Healthcare companies across India.

Millions Advisory is a Search firm offering Recruiting services to customers across India. Industries serviced include IT, IoT, Semiconductor, BFSI, Healthcare. As part of our USP, our team has a solid expertise into Digital Recruitment and Leadership Hiring.

21/08/2026

Strong candidates at the 8-15 year level are not just evaluating your role during the hiring process. They are reading your organisation through every interaction from the first message to the final round. And they are drawing conclusions you do not know you are broadcasting.

A few specific signals that experienced candidates notice — and what they conclude from them.

How long it took to respond to their reply. A candidate who responded to your outreach within 24 hours and waited five days to hear back has already formed a view about how the organisation values responsiveness. They have not said anything. But the clock started when they replied, not when you followed up.

Whether the interviewers had read their background. A panel that asks questions clearly answered by a five-minute review of their profile is not just inefficient. It signals that the process is not designed around them. A candidate with twelve years of specialist experience has sat in enough interviews to know the difference between a panel that prepared and one that is evaluating generically. Generic evaluation is itself a red flag about how the role was scoped.

Whether the people they met seemed energised by the work. This one is harder to manufacture. Candidates pick up on the difference between a team that is excited about what it is building and a team that is managing obligations. They cannot always articulate it, but they feel it in how people talk about the problems they are working on, in whether the conversation goes longer than scheduled because someone got genuinely engaged, in whether there was any intellectual friction in the room.

Whether feedback arrived at all. A candidate who completed two rounds and received no feedback — not a rejection, just silence — has not just had a bad experience. They have updated their view of how the organisation treats people when there is nothing to gain from the interaction. They will share that view in the networks where your next shortlist lives.

None of these signals are managed through an employer branding campaign. They are managed through process design and the behaviour of the people running the search.

For hiring leaders: which of these signals is your current process broadcasting without knowing it?

19/08/2026

Most GCCs track the cost of a bad hire. Almost none calculate the cost of a vacant specialist role. These are not the same number, and the second one is usually larger.

When a mid-senior specialist seat sits empty for four to six months, the costs are real but distributed in ways that do not show up on a single line in anyone's budget.

The first cost is senior leader time. Someone is absorbing the responsibilities of the vacant role. At the 8-15 year specialist level, that someone is almost always a person who costs more per hour and whose attention is already committed elsewhere. Every week the seat is empty, your most expensive people are doing two jobs. The quality of both degrades, usually quietly.

The second cost is decision delay. Specialist roles exist because organisations need specific judgment applied to specific problems. When the seat is empty, those decisions either do not get made, get made by someone who is under-qualified to make them, or get escalated upward into a layer that was not designed to hold them. Product decisions slip. Technical choices get deferred. Timelines built on assumptions about team capacity become fiction.

The third cost is team drift. Junior members in a specialist function without a senior anchor start calibrating their standards, their output, and their professional development against whoever is available rather than whoever is right. Six months of this is recoverable. Longer than that, it compounds.

None of these costs appear on the invoice for the eventual hire. They accumulate invisibly in the background while the search runs, and they make the business case for moving faster much stronger than most TA conversations acknowledge.

If your organisation is running a six-month specialist search and treating urgency as a sourcing problem, the conversation worth having is about what that vacancy is costing week by week, not just what the hire will cost when it closes.

For TA and business leaders: how do you currently quantify the cost of a vacant senior role in your planning conversations?

17/08/2026

Every GCC with an AI mandate is hiring right now. A significant number of them are conflating two roles that have almost nothing in common except the word AI in the title.

The ML Engineer: This person builds and deploys machine learning systems. They work at the intersection of software engineering and data science — writing production-grade code, building training pipelines, managing model versioning, optimising inference, and ensuring that a model which works in a notebook also works reliably at scale in a live system. Their job is to make AI functional, stable, and maintainable. They think in systems and edge cases. When a model behaves unexpectedly in production, this is the person who finds out why.

The AI Product Manager: This person defines what the AI system should do and why. They translate business problems into AI product requirements, work with engineering and data science teams to scope what is feasible, own the roadmap, manage stakeholder expectations, and ensure that the AI capability being built is solving a real problem rather than an impressive-sounding one. They do not train models. They determine whether the model being trained is the right bet to make.

Both profiles are genuinely scarce in India. Both are critical as GCCs build out AI functions. And both will respond to a JD that says "AI Lead" or "Head of AI" because organisations consistently write mandates that blur these two responsibilities into one impossible role.

The consequence of conflating them is predictable: you either hire a strong ML Engineer and then wonder why there is no product thinking in your AI roadmap, or you hire a strong AI PM and then wonder why nothing ships reliably into production. The gap does not announce itself. It shows up six months in, quietly, in the wrong ways.

The diagnostic question before opening the mandate: is the primary problem that we do not know what AI capability to build, or that we cannot build and ship the one we have already defined? One answer calls for a PM. The other calls for an engineer.

AI and technology leaders: how clearly are you separating these two profiles in your current AI hiring mandates?

14/08/2026

A strong first outreach message gets you a response rate, not a hire. What happens in the next two touches determines whether a conversation actually starts.

Most recruiters do one of two things after no reply to a first message: they send an identical follow-up that says "just checking in" or "wanted to bump this up," or they give up entirely. Both are wrong for the same reason. Neither adds new information. Neither gives the candidate a new reason to respond.

Here is how a three-touch sequence actually works at the specialist level.

Touch one: the specific pitch. This is the message we covered last week — role, scope, comp band, city. One specific thing about their background that makes this relevant. No fluff. The goal of this message is not to start a conversation. It is to be specific enough that ignoring it feels like a deliberate choice rather than an easy delete.

Touch two, five to seven days later: the angle shift. Do not repeat the pitch. Add something the first message did not have. This could be a piece of context about why the role exists now — a new product line, a leadership change, a mandate that just got executive sponsorship. It could be a specific piece of information about the team they would be joining. The goal is to make touch two feel like a different reason to engage, not a reminder that you sent touch one.

Touch three, another five to seven days later: the clean exit. This is the most underused message in recruiting. Something like: "I did not want to leave this without one last note. If the timing or scope is not right, no pressure at all — I will close this out. If there is a version of this role or a future conversation that would make sense, happy to stay in touch." A clean exit does two things: it creates a final opportunity to respond, and it leaves the relationship intact for the next search. Candidates who were not ready this time often come back for the next one if the last message they received was respectful rather than a sixth identical follow-up.

Three touches over two to three weeks. Each one adds something. The sequence stops when you get a response or complete touch three, whichever comes first.

TA practitioners: what does your current follow-up sequence look like after a non-response?

12/08/2026

Every offer decline is a diagnostic. Almost no GCC treats it that way.

When a candidate declines an offer, the standard response is to note it in the ATS, restart the search, and move on. The reason given — competing offer, personal reasons, location — gets logged and filed. What almost never happens is a structured conversation about what the decline is actually telling you about your process, your positioning, or your comp strategy.

Offer declines at the 8-15 year specialist level cluster around a small number of root causes, and most of them are visible in hindsight if you look for them.

The competing offer decline is rarely just about money. At this level, a candidate who had a better offer on the table was in two processes simultaneously. That almost always means your process was slow enough to let a competitor complete their cycle while yours was still running. The decline is telling you something about velocity, not compensation.

The personal reasons decline is often a scope problem. A candidate who withdraws citing personal reasons at the offer stage frequently received an offer that did not match the role they thought they were evaluating. Either the JD evolved during the search, the panel communicated different expectations across rounds, or the offer itself reframed the scope in a way that no longer made sense to the candidate. The personalness of it is real — but it was triggered by a process failure.

The counter-offer acceptance is the most instructive of all. A candidate who accepts a counter from their current employer was never fully committed to leaving. That signal was almost always present earlier in the process — in how they talked about their current role, in their urgency, in how they engaged between rounds. The counter-offer did not create the outcome. It revealed something that was there from the start.

If your TA team is not holding a structured debrief on every specialist offer decline within a week of it happening, you are discarding the most specific feedback your hiring process will ever generate.

For TA leaders: what does your last three offer declines have in common?

10/08/2026

Every GCC is building a security function right now. A large number of them are getting the first hire wrong because two very different roles are travelling under nearly identical labels.

The Security Analyst: This person operates within a defined security environment. They monitor, detect, investigate, and respond. They work with SIEM tools, run threat hunts, triage alerts, and escalate incidents. Their job is to keep watch and act fast when something breaks through. They are reactive by design, and that is not a limitation — it is the function. A GCC that needs to operationalise its security monitoring and build an alert-response capability needs this profile first.

The Security Architect: This person designs the security environment that the analyst will operate in. They make decisions about identity and access frameworks, network segmentation, data protection controls, cloud security posture, and how the organisation's security investments fit together into a coherent whole. They work in principles and trade-offs more than in tools. Their output is a security posture that reduces the attack surface before an incident occurs, not a faster response after one does.

Both will have certifications. Both will list similar tools on their resumes. Both will apply to a JD that says "Senior Security Engineer" or "Information Security Lead" without much hesitation. The difference emerges in what they actually do with their day and what kind of problem they are equipped to solve.

A GCC that hires a Security Analyst when it needs an Architect ends up with excellent monitoring of a poorly designed environment. One that hires an Architect when it needs operational coverage ends up with a well-designed environment that nobody is watching closely enough.

The diagnostic question is straightforward: does the security environment exist and need to be operated, or does it still need to be designed? The answer tells you which profile to open the mandate for.

Security and infrastructure leaders: how clearly are you separating these two profiles when you scope a security mandate?

07/08/2026

Every GCC is hiring cloud talent right now. A significant number of them are hiring the wrong profile for what they actually need.

The problem is that two very different roles are travelling under the same label.

The Cloud Architect: This person designs the infrastructure strategy. They decide how workloads are structured across cloud environments, how security and governance are built in from the start, how the organisation's cloud spend is governed, and what the platform looks like three years from now. They work in concepts and decisions more than in implementation. Their output is a blueprint that others build from. When a GCC is setting up its cloud foundation or making a major architectural shift, this is the hire that determines whether the next five years of infrastructure is sound or expensive to undo.

The Cloud Engineer: This person implements, operates, and optimises what the architect has designed. They are hands-on with the actual cloud environment — provisioning, automation, monitoring, cost optimisation, incident response. They are the ones who keep the infrastructure running at the quality and cost levels the architect planned for. Their output is a working system, not a document.

Both are technical. Both carry cloud certifications. Both will apply to a JD that says "Cloud Architect" or "Senior Cloud Engineer" without much distinction. The hiring manager who does not separate these profiles clearly will interview candidates for one role while actually needing the other, and the shortlist will feel consistently wrong without anyone being able to say why.

The diagnostic question before opening the mandate: is the GCC's cloud foundation already designed and proven, or is it still being defined? If the former, you need engineering depth. If the latter, you need architectural judgment first.

Getting this wrong at the foundational stage is one of the most expensive hiring mistakes a GCC can make, because everything built on top of it inherits the problem.

Cloud and infrastructure leaders: how explicitly are you separating these two profiles in your current hiring briefs?

06/08/2026

Most recruiter outreach messages to mid-senior candidates follow the same template. And most of them get ignored for the same reason.

Here is what the average first-touch message looks like:

"Hi [Name], I came across your profile and was impressed by your experience. We have an exciting opportunity with a leading MNC that might be a great fit for your background. The role offers excellent growth prospects and a competitive package. Would you be open to a quick call to discuss?"

Every word of this is doing the opposite of what it intends. "Came across your profile" signals a mass search. "Impressed by your experience" is unverifiable flattery. "Leading MNC" and "exciting opportunity" are placeholders that could describe any role at any company. "Competitive package" defers the only question the candidate actually has. "Quick call" asks for time before giving a reason to spend it.

A candidate with twelve years of specialist experience receives versions of this message multiple times a week. The delete rate is near-total.

Here is what a message that gets a response looks like:

"Hi [Name], I noticed your work on [specific project or domain] at [current company]. We are running a search for a [specific title] at a [brief, specific description of the GCC or org] in [city]. The role owns [one specific thing]. The comp band is [range]. Happy to share the full brief if the scope is relevant to where you are headed."

The difference is not tone. It is specificity. Every line answers a question the candidate is silently asking: did you actually read my profile, what is the role, what will I own, what does it pay, and why should I spend fifteen minutes on this.

The first message optimises for the recruiter's effort. The second optimises for the candidate's time. At the 8-15 year level, only one of those gets a reply.

TA practitioners: what is the one change that made the biggest difference to your outreach response rates?

05/08/2026

Referrals are the most trusted sourcing channel in most GCC hiring teams. They are also the least audited.

Here is the problem nobody talks about.

At the early-career level, referrals work well. The pool is large, the stakes per hire are lower, and a warm introduction genuinely improves conversion. But at the 8-15 year specialist level, referral networks have a structural flaw: they are deeply homogeneous.

The people your current team refers are overwhelmingly from the same institutes, the same previous employers, the same professional circles, and frequently the same geography. This is not a character flaw. It is how professional networks form. People refer people they know, and they know people like themselves.

The consequence for GCC hiring is invisible until it compounds. You build a team that is technically strong but draws from an increasingly narrow slice of the available talent market. You miss specialists who came up through less conventional paths. You replicate the same thinking patterns, the same blind spots, and the same professional assumptions across your senior layer. And because referrals feel like a quality signal, you never question whether you are actually accessing the best candidates or just the most accessible ones.

There is a second problem. Referral candidates at this level often come with an implicit social contract. The person who referred them is watching. Giving honest, specific rejection feedback becomes uncomfortable. Hiring managers soften their reasoning. The search team loses calibration data they need to sharpen the next shortlist.

None of this means referrals are bad. It means they should be one input among several, not a default first move for specialist roles. The GCCs that build the strongest senior teams use referrals to access warm introductions, not to define the boundaries of their search.

For TA leaders: when did you last audit what percentage of your specialist hires came through referral versus independent sourcing, and what that split is doing to your team's range?

31/07/2026

After years of conversations with mid-senior candidates who were being courted by multiple organisations simultaneously, a pattern becomes clear. Compensation closes very few of them. Three things actually do.

The first is scope clarity. Not what the role is called. Not what the JD says. What decisions this person will own, what they will not own, and how much of that is actually settled versus aspirational. A candidate with twelve years of experience has seen enough role descriptions to know the difference between a mandate that is real and one that is still being negotiated internally. Vague scope is not intriguing at this level. It is a warning sign. The organisations that consistently attract strong mid-senior candidates can answer, specifically, what this person will be accountable for in month six. Not month one. Month six.

The second is who they will report to. This matters more than most hiring managers expect. A strong specialist at the 8-15 year level is not just evaluating the role. They are evaluating whether the person above them is worth learning from, worth being associated with, and worth navigating a difficult quarter alongside. If the hiring manager cannot articulate what they bring to that relationship beyond title and org chart position, the candidate notices. The best candidates have options. They will choose the manager as much as the role.

The third is whether the GCC feels like it is building something. This is harder to manufacture. Candidates at this level have an instinct for whether an organisation is genuinely investing in its India centre or using it as a cost-arbitrage vehicle. They pick this up through the quality of the conversation, the ambition of the problems being described, and whether the people they meet during the process seem energised or fatigued. Culture is not a slide in a presentation. It is a signal that comes through in every interaction from the first outreach message to the final round.

Compensation is assumed. These three things are earned. The organisations that get this right do not lose the candidates they want.

For TA and hiring leaders: which of these three is hardest to get right in your current process?

Address

Plot No. 37 (Old No. 110), Door No. 5A, Chateau D Ampa Building, 2nd Floor, Nelson Manickam Road, Aminjikarai
Chennai
600029

Opening Hours

Monday 9am - 8pm
Tuesday 9am - 8pm
Wednesday 9am - 8pm
Thursday 9am - 8pm
Friday 9am - 8pm

Telephone

09894066373

Website

Alerts

Be the first to know and let us send you an email when Millions Advisory posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Millions Advisory:

Shortcuts

Share

Category