FluffyNoodle
FluffyNoodle
8mo
by

Trending @Infosys; Pathetic experience at Infy

I had a pathetic experience at Infy in recent days. Worked for a top class client (payment domain) for 3 yrs in 2 different teams. Due to contract completion,I was released from that client. On bench right now. Was giving internal interviews. Mostly internal rounds were happening. Managers were not hearing back from the client mostly. The lead who is responsible for sharing profiles for getting onboarded to clients was mostly sharing my profiles with clients where we need to work at night shift. Lead never asked about my preference for shifts. Ofcourse,when the interviewer used to ask if I am comfortable to work in night shifts,i said no due to health concerns. Later,I also texted the lead that I am not comfortable with night shifts clients. Also, lead doesn't respond to me mostly. But when lead calls me even if I am away , expects me to pick up the call everytime. I had an internal rounds for one of the clients. And the interviewer gave bad feedback about me.In another client, only childish scenario based questions were asked , strength, weakness questions and conclusion was drawn very quickly. This lead mailed me keeping 4 other people(gp project managers mostly and manager who give me rating) in cc and said that they are sharing my profiles with multiple accounts (even if lead is not sharing my profiles much) and getting this feedback about me. I think, Lead used it as a shield to protect self so that nobody reaches out and held lead responsible for having me on bench for more than a month. I am sharing my perspective regarding the feedback and recent internal interview experiences, as there seem to be several misjudgments that do not reflect my true skills, contributions, or potential. Feedback from Client Interview:

  1. Claim: No experience in test case design ➤ I have designed test cases extensively across multiple sprint cycles for various features. Each test case was reviewed and approved by developers and product owners before execution.
  2. Claim: Less understanding of testing process and phases ➤ I’ve worked on functional, regression, smoke, integration, sanity testing etc in every sprint cycle during my 3+ years at payment domain client, a top-tier fintech client. A vague question like “What are phases of testing?” could’ve been interpreted in many ways — I even asked for clarification during the interview but wasn’t given any.
  3. Claim: Only worked in test environments ➤ I worked in QA environments as per client protocol. Access to staging or production was restricted to other teams. This does not reflect my capability but is based on client access policies.

Feedback from Internal Round for one of the client:

  1. Claim: No advanced Java knowledge ➤ I was given 3 coding questions. I successfully solved the 1st and 2nd. For the 2nd one (find max-min difference), I did solve it, but the interviewer had a different unexplained expectation and couldn’t clarify the requirement or the expected output. Didn't get any clarification for 3rd question as well. Was only given a matrix but what to do with it, didn't tell me. Judging someone based on a poorly framed question is unfair. I’ve regularly used Java (OOPs, Collections, File handling, exception handling, etc.) in my automation work.
  2. Claim: No knowledge of API & SQL ➤ I was barely asked any API or SQL questions. One SQL query asked was answered correctly. It’s unreasonable to conclude my lack of knowledge based on 1 or 2 surface-level questions.
  3. Claim: No Selenium knowledge ➤ I’ve used Selenium for 3+ years. I might forget exact syntax in an interview, but that doesn't mean I lack hands-on knowledge. Reading data from Excel is more of a utility task, not a fundamental Selenium concept.
  4. Claim: No automation experience ➤ I’ve spent my entire time with the payment domain client working in extensive automation. I handled: Automation using Selenium, Java, Cucumber, TestNG.API testing using REST Assured, Karate and SOAP APIs with SoapUI.Integrated automation with a cloud based platform, managed configs, pod restarts, service validation. Performed performance testing using JMeter. Frequently recognized by client managers and engineers for my ownership, speed, and accuracy. Received client appreciation emails, including from directors and managers from both the teams. Examples of Poor Interview Conduct: 1.Was asked: Why does String start at index 0? It’s only for arrays — which is factually incorrect. The manager had to correct the interviewer. 2.Asked: Does System.setProperty exist in Selenium 4? — it’s a Java concept, not Selenium-specific. 3.Asked: Why is WebDriver an interface and ChromeDriver a class? — theoretical language design choices aren’t practical assessment tools. 4.One interviewer ended the interview in under 10 minutes after just 3-4 questions. 5.When I explained hard vs soft assert, I was interrupted and shouted at: “Give real-life examples! You should know this with 3 years’ experience!” — I did give examples, and the answer was later accepted. But the behavior was unnecessarily harsh. Other Facts to Highlight: 1.There were internal interviews where I was told I did well, and my profile would be shared with the client. But many times the client didn’t get back, or selection couldn’t proceed due to billing/role constraints — things outside my control. 2.I’ve always taken feedback seriously and keep trying to upskill. But interviews must be fair, clearly communicated, and considerate — especially if the goal is to evaluate actual work potential and not trivia. 3.I am committed to improving wherever needed. But misrepresenting my capabilities or concluding from unclear or incorrectly conducted interviews damages both morale and fairness.
  5. I’m reaching a point where continuing in this environment is becoming extremely difficult for me. I mailed them by all explaining most of the points , didn't respond too much fearing termination. But, this mail has taken a serious toll on my motivation and mental well-being.
8mo ago
SparklyHamster
SparklyHamster

Send this in reply to that mail. And most importantly SWITCH.

FluffyNoodle
FluffyNoodle
8mo

Yes ..

WigglyPenguin
WigglyPenguin

I feel here only lead is not responsible. The very next to the lead, probably any manager is involved to ask the lead to do all. The lead mostly say yes to yes so they would be in safe side. Its a indication to switch job as soon as possible.

DancingLlama
DancingLlama

Client Hsbc?

FluffyNoodle
FluffyNoodle
8mo

No

SnoozyDumpling
SnoozyDumpling

Client 🍎

Discover more
Curated from across