He had almost bagged the job. But one simple request caused him to lose the job offer: ‘Is this a red flag?’

A software engineer recently shared a troubling hiring experience on the Developers India subreddit, explaining how a nearly secured opportunity slipped away simply because he asked for clarity on his working schedule in written form. His post reflected both frustration and self-reflection after the incident unfolded.

He began by expressing regret for deleting an earlier version of his post. According to him, he had received thoughtful and practical suggestions from others, but removed the discussion during a moment of stress and unease. The situation had left him mentally overwhelmed, prompting a reaction he later felt guilty about.

To provide context, he explained that he had just resigned from a highly unhealthy workplace where he had spent four years. That environment, he said, routinely ignored personal boundaries and consumed his time without consideration. As a result, he had become particularly sensitive to warning signs in new opportunities and was actively trying to avoid repeating the same experience.


During the hiring process for a senior software development role offering a salary package of 10.5 LPA, he noticed certain unusual patterns. The technical evaluation rounds were unexpectedly simple and did not thoroughly test his abilities. Instead, interviewers seemed more concerned about logistical aspects such as his commute to the office rather than his expertise.

A key moment that raised concern involved a discussion with the operations manager. The manager indicated that work schedules were flexible and entirely dependent on project demands, implying that fixed office hours were not part of the company’s structure. This suggested that a conventional workday routine might not apply in this role.

Despite these concerns, the company moved forward and issued him an offer letter over the weekend, asking him to join immediately on the following Monday. This gave him barely any time to evaluate the terms or prepare for the transition. When he carefully reviewed the document, he noticed several omissions. The letter did not mention daily working hours or specify the number of working days in a week. Additionally, it imposed a one-month notice period even during the initial three-month probation phase.

Instead of accepting the offer without question, he chose to seek clarification. He responded to the email, including senior stakeholders in the communication, and politely requested that the document clearly outline working hours, confirm a standard five-day schedule, and reconsider the notice period given the urgency of the joining timeline.

Shortly afterward, he received a call from the HR representative, who informed him that she was not permitted to include such details in the offer document. She suggested that these matters should have already been discussed during the interview process and advised him to wait while she consulted internally.

Soon after, he was notified via email that the company had decided to withdraw the offer altogether. The explanation given was that incorporating additional terms would require internal approvals and compliance checks, which could not be completed within the limited timeframe before his scheduled start date.

Although he initially felt anxious about losing the opportunity, he later reconsidered the situation. In hindsight, he felt relieved that he had avoided potentially entering another unhealthy work environment immediately after leaving a difficult one.

The post sparked considerable discussion among readers. Many supported his decision, suggesting that withdrawing an offer over a reasonable request indicated deeper organizational issues. Others pointed out that while working days are typically defined, exact office hours are often left flexible, especially in roles where workloads may vary depending on project demands.