Chapter 23

The Internship He Did Not Get
The rejection arrived in March, a carefully worded email thanking Caelan for interviewing and explaining that the company had selected a candidate with more advanced manufacturing experience. He had wanted that internship badly. It was paid, connected to his degree, and located within commuting distance of home. He had already calculated how many hours he could work and how much of the following semester it would fund.
For a moment, disappointment slid straight into anger. He thought about the transfer, the four credits that would not follow him, the extra summer course, and the feeling of continually adjusting his ambitions downward.
At dinner he pushed rice around his plate and told Nerissa he was fine.
She studied him briefly. “That's not what your face says.”
“I didn't get the internship.”
“I'm sorry.”
“It would have helped.”
“Yes.”
He waited for the old pattern: she would brainstorm desperately, offer money she did not have, or reassure him with promises about how everything happened for a reason. She did none of those things.
The company's rejection email included a link to an optional feedback session. Caelan scheduled it, then spent the next two days worrying that he would sound defensive. The hiring manager, a practical engineer named Owen Blake, told him his technical coursework was strong, but he had spent too much of the interview describing what Hawthorne had taught him rather than demonstrating how he made decisions under constraints. “We hire people to solve trade-offs,” Owen said. “Show us your judgment, not just your résumé.”
Caelan left the call annoyed because the criticism was fair. He reviewed the model he had built for his summer course and identified a design change he had made purely because it looked elegant. The change had increased cost without improving durability. He rebuilt the model using fewer components, wrote a comparison of failure modes, and presented it to Caroline Vale at the fabrication workshop. She challenged his assumptions and asked him to defend the price difference. The conversation was more useful than praise.
He showed the revised design to Meredith, his commuter classmate, who suggested a test sequence based on real maintenance conditions rather than laboratory convenience. They spent an evening documenting the work. The report became a strong portfolio piece, but it did not arrive as a consoling prize for rejection. It emerged because he kept working when no guarantee of reward existed.
At home he considered telling Nerissa that the rejection had taught him a valuable lesson. The phrase sounded too neat. Instead he told her he still felt disappointed and that he had received useful feedback. She listened and asked whether he wanted to cook dinner together. He said yes. They chopped vegetables side by side and spoke about the workshop, the weather, and a book she had borrowed from the community center.
Later that night he checked his savings. There was enough to pay the next train pass and the course materials he needed, but not enough for an unexpected emergency. He added a small automatic transfer from each paycheck. This was the kind of planning he had once considered his mother's job. Now he understood that competence was not a state granted at graduation. It was a habit built through boring repetition.
When the next rejection arrived, he opened it, recorded the result, and moved on to another application. The disappointment still hurt. It no longer required someone else to make a sacrifice to prove his future remained possible.
“Do you want advice,” she asked, “or do you want to be disappointed for a while?”
He looked up, startled. “I think disappointed for a while.”
“All right.”
They ate in silence, and it was a good silence. After dinner she left him alone with his frustration rather than trying to purchase relief from it.
The next morning Caelan went to Professor Lenox's office and asked what skills would make his next application stronger. The professor recommended a summer fabrication course and an open-source modeling project. Caelan emailed the internship company requesting brief feedback and, to his surprise, received two actionable suggestions about communicating design trade-offs in interviews.
He applied to smaller firms. He contacted the manufacturing workshop at Bay Commonwealth about a summer assistant opening. He visited the career center and rewrote his résumé to emphasize completed projects rather than institutional prestige. There were more rejections. Each one stung. None of them was an instruction to demand a rescue from his mother.
One afternoon he met Silas in Boston for coffee. Silas had secured a summer engineering internship through Hawthorne and seemed almost embarrassed to tell him.
When Professor Lenox looked over Caelan's revised portfolio, he pointed to a paragraph describing a failed prototype. “Keep this,” he said. “A good engineer can explain how judgment changed after evidence.” Caelan had originally wanted to remove the failure and present only the successful model. Instead he revised the explanation to be clearer. He began to understand that honest work had a shape: it showed not merely where the project ended, but why the decisions along the way were justified.
Silas called that weekend to ask how the revised portfolio was going. Caelan sent over the testing report and waited for the usual sarcastic commentary. Instead Silas said the document sounded more confident because it admitted what the first design got wrong. They talked for an hour about engineering jobs, competing deadlines, and whether adulthood was mostly learning to have a plan B. Caelan laughed when Silas said it was really about having a plan C and enough money to buy groceries. The joke worked because it contained a truth neither of them needed to avoid.
“Be happy,” Caelan said.
“I am. I just don't want to rub it in.”
“You're allowed to do well even when I'm disappointed.”
Silas grinned. “That's weirdly mature.”
“Don't get used to it.”
May you like
Later, during the walk home from the station, Caelan passed a small park where children were trying to launch paper airplanes into gusty spring wind. One plane rose beautifully, then struck a tree. Its owner laughed, retrieved it, and adjusted the wings. Caelan stood watching longer than he would have admitted.
At his desk that night he opened a new project file. He called it Second Design. Not because the first plan had been worthless, but because a design's value could survive its revision.