If Your Manager Asked You to Do Something Unethical, Say What You Checked First

“What would you do if your manager asked you to do something unethical?” tests you under pressure. “I’d refuse and go to HR” skips every hard part. Most requests an engineer gets are gray, so start there. First, check the request against a written rule. That tells you whether it’s wrong or just uncomfortable. Second, raise it with your manager directly and soon. Name the rule and offer another way to reach their goal. Third, if they still push, bring in the person who owns that rule. Do it with your manager, not behind their back. Then accept that owner’s decision. Answer with a real case if you have one. The follow-ups ask for details only a real case has. The running example below is an Android engineer. His manager asked him to start an attribution SDK before users had given consent. The last section covers what to say when nobody has ever asked you to cross a line.

Your manager asked you to do something unethical? Most answers skip the gray cases

Indeed’s guide to ethical interview questions was updated in June 2026. It lists a version of this question about a manager asking you to act against your ethics. Its advice is to give real examples of how you handled a situation. That advice matters more here than for most questions. Everyone promises to do the right thing. Few people can show how they did it.

The obvious answer treats the request as plainly wrong. Fraud, faked test results and lying to a customer are easy calls. Nobody needs an interview to find out whether you’d commit fraud. The interviewer wants to see what you do when the request is defensible. Maybe the deadline is real and the manager is not a villain. Maybe you aren’t sure you’re right.

Mary Gentile built a business-ethics curriculum around that gap. It is called Giving Voice to Values. The University of Virginia’s Darden School of Business, where she teaches, describes it on its initiative page. The page carries no date. Its summary of her book says the issue “isn’t distinguishing what is right or wrong.” It is “knowing how to act on your values despite opposing pressure.” The same page says people who use the method often rehearse scenarios and script the conversation in advance. So your answer should show the conversation you had with your manager, word for word where you can.

Check the request against a written rule before you call it unethical

Kofi is an Android engineer with five years of experience. He works on a language-learning app sold by subscription. He is interviewing for a senior role at a health-tech company. We invented him for this post.

A paid campaign was launching on a Monday. The growth team said its install numbers were short. Their attribution SDK only started after the consent screen. That screen was the third step of onboarding. Kofi’s manager, Ines, asked him to start the SDK in the app’s startup code instead. It would only be for campaign week, she said. Then he could switch it back.

Kofi felt uneasy. But unease alone gave him nothing specific to say. So before he answered, he checked two things. First, he ran a debug build and watched the network calls on first launch. The SDK sent the advertising ID and device details before any screen appeared. Second, he read the rules that applied.

Google Play’s User Data policy is one of them. The policy page shows no date. It says an in-app disclosure is needed when data collection may fall outside what users reasonably expect. Consent needs “affirmative user action,” such as a tap. It also says consent must be given “before your app can begin to collect or access” that data. The SDK being third-party code didn’t help. The policy says the developer remains responsible for compliance in that case too. His own company’s privacy policy also promised that marketing data needed consent.

Now Kofi had something specific to say. The change would break a published rule and his company’s own promise. Your answer needs the same step. Name what you checked and what it said. If the check had come back clean, the right answer would change. He’d voice his discomfort, then build it.

Raise it with your manager first, with the rule and a way to hit the date

Kofi messaged Ines the same afternoon. Then he asked for ten minutes on a call. He said three things.

He started with what the change would actually do. The SDK would send device identifiers before users saw the consent screen. Next came the rule, with the link. Last, he offered a way to serve her goal. Her real problem was missing installs. Their funnel showed 18% of new users closed the app before reaching step three. Those users never saw the consent screen. So he proposed moving consent to the first onboarding screen. That would take about two days, so it could ship before Monday.

Each part covers a gap in the other. A refusal with no alternative sounds like you care about being right more than about the team. An alternative with no rule sounds like a preference. Both together show judgment and a wish to help your manager succeed.

Bring in whoever owns the rule, with your manager, not around them

Ines pushed back. It was only one week. Nobody would notice, she said. Interviewers probe this moment hardest. Kofi didn’t argue a second time. He also didn’t go quietly to her boss.

He said he wasn’t comfortable shipping it. He asked her to put the question to Marcus with him, that day. Marcus led privacy for the company. If Marcus said it was fine, Kofi would build it. Ines agreed and joined the call. Marcus said no and approved the consent-first change.

That shape is easy for an interviewer to trust. Kofi escalated to the person who owned the rule, not to the most senior person he knew. He kept his manager in the room. He also said in advance that he’d accept the owner’s ruling. That last part shows you aren’t using ethics to win a technical argument. Our post on disagreeing with your manager covers ordinary disagreements, where you lose and commit.

Accepting the owner’s ruling has a limit. Some requests stay wrong whatever a privacy lead says. Faking data for an auditor is one. Then you refuse and use your company’s formal reporting channel. Say that in one sentence if the interviewer asks. Don’t make it the center of your answer unless it really happened.

Kofi’s story also needs a result that includes the cost. The campaign launched on time. Attribution coverage rose from about 55% of installs to about 66%. That was still well short of what growth wanted. A month later, Ines asked Kofi to add a check to the team’s SDK review list. Every new SDK now gets a look at what it sends before consent.

Kofi’s answer, from the request to the checklist

Kofi, Ines, Marcus and the language app are fictional. So are the 18% and the coverage figures. The Play policy lines he relies on are real. Keep his order and use your own case.

Something close to that happened to me last year. We had a paid campaign launching on a Monday. Growth was missing installs, because our attribution SDK only started after the consent screen. My manager, Ines, asked me to start it at app launch for that week.

Before I answered, I checked what the SDK sent. It sent the advertising ID and device details before any screen appeared. Google Play’s User Data policy requires consent before that kind of collection. Our own privacy policy promised the same.

I raised it with Ines that afternoon and showed her the policy. I also offered another fix. About 18% of new users quit before reaching the consent screen. So I suggested moving it to the first screen. That was two days of work.

She still wanted the quick version. So I asked her to check it with our privacy lead together. I offered to build whatever he approved. He turned down the early start and approved moving consent. We launched on time. Coverage went from about 55% to 66%, still short of what growth wanted. Afterwards Ines asked me to add a pre-consent check to our SDK review list.

The order is built for the follow-ups. “How did you know it was wrong?” points to the second paragraph. “Did you go over her head?” points to the fourth. Sometimes the request is fine in principle and only the timing is wrong. Our post on saying no to someone who outranks you covers that version.

If nobody has asked you to cross a line, use the time you caught one

Plenty of engineers have never had a manager ask for anything like this. Don’t invent a story. The follow-ups on this question get specific fast. Who owned the rule? What did they decide? A made-up case falls apart by the second question.

Say plainly that it hasn’t happened to you. Then give the nearest real case. That is usually a problem you noticed that nobody asked about. Kofi’s backup case came from a code review two years earlier. A teammate’s change logged the user’s email address with every network error. Those logs went to their crash reporting service. It kept them for 90 days. Kofi flagged it in review and linked the company’s logging guideline. The teammate agreed and removed the field. Kofi then added a lint check that flags email fields in log calls. That story uses the same three moves at a smaller scale. He checked a written rule, then raised it with the person involved. Last, he fixed it so the next person wouldn’t need to.

Leave a Comment