"See if you can lend a hand."

I glanced through the glass at the engineers slumped over their desks and asked, "Where exactly are you stuck?"

Manager Lambert stood, walked to the door, and called out:

"Whitney, come brief Simmons on the problem."

Finn Whitney was in his early thirties, unshaven, with dark circles stamped under his eyes.

He looked me up and down, shoved the proposal across the table, and didn't bother hiding his irritation. "You're a girl. What do you know about programming?"

"This project runs on a cutting-edge automated control system. You sure you can handle it?"

I flipped through the proposal for a few minutes. The further I read, the more wrong it looked.

"Engineer Whitney, your control logic has a problem." I pointed to one of the modules. "This feedback loop is wired wrong. It's not a coding issue. The algorithm framework itself was built on a flawed foundation."

Finn frowned. "No way. We followed the standard methodology."

"Look here."

I took his pen and drew a few lines across the schematic.

"The feedback signal should route through this path. You've got it running in parallel, but it needs to be serial with a bypass."

"Any program built on this framework will stall at step three, because the signal never completes the loop."

Finn went still. He stared at the lines I'd drawn for a long time, and the color drained from his face.

"Son of a… she's right."

Two other engineers crowded in behind him, studied the schematic, and said nothing.

Finn looked up at me. His expression was hard to read.

That afternoon, I rebuilt the corrected framework from the ground up.

The program ran clean.

Manager Lambert beamed. "Simmons, you're something else. I knew I picked the right person."

"Keep this up. Once the project wraps, I promise you'll be well taken care of."

He sounded so sincere there was no room for doubt.

From that day on, I lived inside the Engineering Department.

In by eight every morning, out past eleven or twelve at night, weekends included.

The project timeline was razor-tight. The client called every other day pushing for updates, and the bosses pushed just as hard.

Over the next month and a half, I wrote tens of thousands of lines of code and revised the plan more times than I could count.

Whenever the client had a change request, I was the first person they contacted.

Lambert couldn't even be bothered to relay messages. He just handed them my number directly: "Talk to her. It's faster."

At first, the engineers in the department weren't exactly welcoming.

Because I was a woman, and because I didn't have a formal engineering degree.

Finn was the worst. He barely acknowledged me when I spoke to him, and dragged his feet every time I asked for files.

Once I went to him for the raw dataset and he didn't even lift his head. "Find it yourself. It's on the desk somewhere."

The desk was buried under a stack of documents half a meter tall. It took me thirty minutes to dig it out.

The others weren't much better.

In meetings, whenever I raised a point, they either ignored it or said, "You wouldn't understand. This is how we've always done it."

But I didn't have the luxury of caring about any of that.

The project wouldn't wait.

By the end of the first week, I had the first module running.

Finn saw the results, paused, and asked, "How'd you pull that off?"

I walked him through it.

He listened without a word. The next day, his attitude shifted noticeably.

He started handing over files without being asked and came to me with questions on his own.

In the third week, another module hit a bug. The engineers spent two days trying to fix it and got nowhere.

I stayed up all night tracking down the issue, changed seven lines of code, and by the next morning it finally ran clean.

After that, every one of them was polite when they saw me.

Finn took me to lunch one day and rubbed the back of his neck. "Simmons, I was a jerk to you before. Don't hold it against me."

I just said it was nothing.

Deep down, I knew they hadn't been trying to make things difficult for me on purpose.

They were simply used to coasting.

The project was worth a hundred million dollars. Company policy tied bonuses directly to the project's value.

For them, as long as the project got delivered, the money was theirs.

Who actually did the work? Irrelevant.

During that month and change, Manager Lambert treated me unreasonably well.

Every morning he'd greet me with a smile, ask if I'd eaten breakfast.

When I stayed late, he'd have Finn order takeout for me.

Once I was running a hundred-and-one-degree fever and still fixing code. When he found out, he sent his assistant over with a box of medicine.

"Susannah, take care of yourself. No project is more important than your health."

At the time, I actually thought he was a decent person.

Looking back now, those words were nothing more than insurance against me walking off the job.

The day the project wrapped, the client signed off on the final review in one pass.

Lambert cracked open a bottle of wine in his office and had everyone raise a glass.

He walked over to me holding his glass, all smiles. "Susannah, you're the real MVP of this project. Paul Lambert does not forget."

I was naive enough to believe that if I just did good work, people would treat me fairly.

Naive enough to believe all those smiles and kind words were sincere.

Naive enough to believe the world actually ran on "hard work gets rewarded."

Now I understood. I'd been nothing but a tool.

I didn't cry. I didn't make a scene.

I didn't go to Director Finch to pour my heart out, and I didn't file a complaint with HR.

Because none of that would have changed a thing.

Report a department manager?

I'd been at the company barely over a month. What leverage did I have?

I made myself one promise, silently.

Starting today, I would never be fooled again.

After I went back to the Finance Department, life got quiet.

Nobody came looking for me, and nobody assigned me any work.

My desk was tucked in a corner where people rarely passed.

Once in a while a colleague would come by to use the printer, grab their pages, and leave without so much as a glance in my direction.

Director Finch didn't call me in for a talk either.

I figured he already knew what had happened over in Engineering. He just didn't want to get involved.

After all, I was nobody. Just the lowest person on the ladder.

The work in Finance wasn't complicated.

Mostly auditing expense reports, organizing vouchers, helping pull together financial statements.

I spent three days clearing the entire two-month backlog of receipts, then re-sorted the previous year's vouchers chronologically from scratch.

Marilyn, at the desk next to mine, watched me hustling back and forth and finally said, "Susannah, slow down. The work's not going anywhere."

I smiled and kept going.

Slow down for what?

If I slowed down, my mind would circle back to all of it. Better to stay busy.

But I wasn't the one looking for trouble. Trouble came and found me.

One day at lunch I went to the cafeteria.

I'd just sat down when two women from Marketing took the seats across from me.

They didn't know who I was. They ate and talked.

"Did you hear? The Engineering project bonus was two million. Lambert pocketed several hundred thousand all by himself."

"Yeah, and the people under him got a nice cut too. Even the intern who just started walked away with fifty grand."

"Apparently the project was stuck from the start. Then some woman from Finance went over and cracked the whole thing."

"No way. Finance? A woman who knows how to code?"

"Who knows if it's even true. Probably just dumb luck. Right place, right time."

"So how much did she get?"

"Not a cent. Worked for free like an idiot."

They both laughed.

I kept my head down and kept eating.

I heard similar things a few more times after that.

In the restroom. In the hallway. Once, in the elevator.

Two people talking up ahead, me walking behind them, listening.

They'd glance back and spot me, freeze for a second, then go quiet.

I wasn't hurt, and I wasn't angry.

I'd already thought all the same things myself.

A fresh college graduate, used as someone else's workhorse, and when the dust settled she didn't even get table scraps.

That kind of story was a joke no matter where you told it.

If I'd been the bystander, I probably would've laughed too.

But let them laugh.

Sooner or later, some of those people wouldn't find it so funny.

I started studying the Finance Department's workflow in earnest.

The company's reimbursement process was painfully slow. From the moment an expense form was filled out to the moment the money actually hit someone's account, it averaged two weeks.

In between, a claim had to pass through the department supervisor, the finance audit, the finance director, and the general manager's signature.

Layer after layer. Any link in the chain could stall.

I spent a week compiling every reimbursement record from the past year into one dataset.

Sixty percent of all delays were stuck at the same bottleneck.

Invoice auditing.

Invoice auditing was entirely manual, one receipt at a time. The volume was massive and mistakes were easy to make.

Whenever a non-compliant invoice turned up, it got kicked back for resubmission, and just that round trip ate several days.

I thought: could a program handle this automatically?

Once the idea took hold, I started working on it after hours.

The company's accounting system was an older build that didn't support API integration, but it could export spreadsheets.

I studied the file format inside and out, then wrote a Python script that could automatically read each invoice number and tax code from the spreadsheet, run them against the tax bureau's public verification endpoint, and write the results back into the sheet.

The concept wasn't groundbreaking. Plenty of off-the-shelf accounting software could do the same thing. The company just hadn't purchased any.

So I built one myself. Free of charge.

Three days of coding and the core functionality was running.

I spent a few more days debugging, pushing the recognition rate from eighty percent to over ninety-five.

The remaining five percent were mostly invoices that had been photographed out of focus or partially blocked. Those still needed a human eye.

The program was ready, but I didn't rush to show it off.

Because I already knew.

In a new environment, what you actually did didn't matter. What mattered was what other people believed you did.

I kept going to work as usual, doing my tasks as usual, greeting my coworkers as usual.

Then one day, Marilyn came back lugging a stack of invoices, sweat beading at her temples.

"Overtime again. If I don't get through all of these by the end of the week, the monthly report won't close."

I looked at the stack in her arms. Two hundred receipts at least.

"Marilyn, let me help."

She glanced at me. "You've got your own work. I'll manage."

"I already finished everything on my end. Might as well make myself useful."

I took the invoices from her, sat down at my computer, and pulled up the program.

Marilyn didn't notice what I was doing. She'd already hunched over her own desk, cross-checking receipts by hand.

About fifteen minutes later, she looked up. "Susannah, you haven't gone through a single one yet?"

"Already done."

"What?"

"Two hundred and thirteen invoices. Six flagged with issues. I've marked every one."

Marilyn froze. She got up and walked over to my screen.

An Excel spreadsheet filled the display, every invoice's information laid out row by row, each status column reading either "Valid" or "Anomaly."

The six flagged entries had specific reasons noted in the remarks column.

Invoice number nonexistent. Issue date mismatch. Taxpayer ID incorrect.

Marilyn stared at the screen for a good ten seconds, then turned to me. "How did you do that?"