This as-told-to essay is based on a conversation with Siobhan MacDermott, a 56-year-old tech founder based in Menlo Park, California. It's been edited for length and clarity.

I've never been underqualified for any job that I've applied to.

I was vice chair at Bank of America and principal at EY. I held senior roles in cybersecurity at AVG and McAfee. I've sat in boardrooms with Fortune 500 CEOs, advised governments, and built practices from scratch.

Then, in early 2024, when I was 54, I had to relocate from New York City to California for family reasons, leaving the management consulting job I'd held as a partner at The Consello Group. I didn't anticipate what could happen when someone tries to re-enter the institutional world in their 50s — particularly as a woman in a career space that doesn't fit neatly into a job description.

The most surprising barrier has been the gap between what I've actually done and what the market knows how to categorize. I'm worried because I'm not sure where the economy is heading, but I'm an absolute eternal optimist.

I'm not going to accept anything other than staying hopeful.

I felt like my job application was going into the ether

It's been frustrating to watch organizations that desperately need exactly what I've built not hire me.

When I started my job search, I reached out to my network to try to figure out what I could do, who'd vouch for me, and where open positions were. A lot of senior roles were being downsized, but I had a lot of people who initially wanted to help me find something.

The strategies that were a complete waste of time were LinkedIn Easy Apply, recruiter calls that went nowhere, and any process that involved a 45-minute competency-based interview with someone who'd never heard of the big companies I've worked for.

I spent the better portion of every day for over a year applying and looking for jobs. I obsessively searched on LinkedIn for new positions, applying over and over again on the site, company websites, emails, and more, but getting nowhere.

I sent out countless résumés and barely got any responses. These are jobs that I know I'm qualified or overqualified to do, but sometimes I didn't even get the courtesy of the automated "thank you for applying" response.

It was like my application went into the ether. I'd try to find the head of HR for these companies on LinkedIn and reach out to them because I wanted the feedback.

I started trying to think of interesting ways to get attention

The strategy that worked the best during my job search was bypassing HR entirely and using direct outreach to CEOs and board members.

I'd send them letters not even related to a job, but more of an observation of their company to get their attention. I tried to be crafty, saying, "Based on my external assessment of your company, here are some things that I think you should be doing as you think through your next quarter."

Reaching out to CEOs got me in the door, but then they'd send me down to somebody who was pretty junior who'd say, "You're overqualified for this job." They'd courtesy interview me because they'd been told to, but it didn't go beyond that.

Sometimes a CEO would send me to HR, and HR would look at my skill set and say, "It doesn't quite match."

That happened quite a few times.

I adjusted my LinkedIn profile to get a better response, and that helped

I changed my gender to male and back to female a bunch of times to see if it made a difference — I didn't change my pronouns, just my actual gender. I felt like I had more responses on LinkedIn being thought to be male than female.

I also think being in Silicon Valley, you age out a lot faster than you do in other parts of the US, and it's definitely a highly male- dominated space. I had those two things working against me from the get-go.

So I removed the first six years of my career from my work experience on LinkedIn, and I took the dates off of my degrees so that people couldn't tell my age. This made me seem seven to 10 years younger, potentially. Once I took those dates off, I felt like I got more engagement on the site.

My job search in Silicon Valley went nowhere, so I decided to pivot and launch my own venture

I started my company out of necessity, and also out of intellectual boredom. I felt like my brain was starting to rot.

It happened about a year into job searching, when I started feeling financial pressure and frustration. I didn't want my full-time job to be looking for a job. My search wasn't looking like it was going anywhere in the foreseeable future, especially out in Silicon Valley. If you're a computer scientist or an engineer, there are jobs available, but I couldn't find a lot out here not in that space.

I started thinking, what am I good at? What do I know? What are all the pieces that I could put together? What problem can I identify that needs to be solved? That came together pretty quickly, and I launched two companies — Khaos Holdings, a strategic risk-intelligence company, and TeenAegis, a child-safety intelligence business, in January.

We're raising capital, and if the capital comes in, that will be the end of my job search. If the capital doesn't come in, then I'll keep searching — but I've decided that whatever I do will be adjacent to the problem I'm trying to solve now.

One good thing came out of the 2 years since my last job

Being out of work for two years shifted my retirement timeline eight to 10 years from digging into savings. However, since my job search started, I've really homed in on what I want to do with the rest of my career.

The journey I went on was a little bit of a midlife crisis. I asked myself, "What's my purpose in life?" as opposed to "What job do I want to have?" and then identified what skill set could bring me to that.

What led me to where I am was really thinking through questions like: What are all the issues that matter to me? What legacy do I want to leave? How do I want to think about my future for the next 10 or 15 years? How do I want to show up every day?

In the beginning, I was going to apply to anything that I could qualify for that would get me some money. Now I'm not going to do that because I don't think that's going to actually be fulfilling or make me happy. My sense of stability has required a deliberate reframe — from "security comes from a salary" to "security comes from what I've built and what I know."

I'm determined to make this work, but I also realize it may not

The hardest thing is maintaining a positive attitude day after day. If my company doesn't work out, then it's not like I can stop trying.

Taking mental health breaks is important because it's overwhelming, lonely, and hard. You lose your sense of self-worth when you're in this position; people look at you like, "Oh, you're the person who's still looking for a job." So it's hard to continue to put yourself out there.

Still, I do believe there's light at the end of the tunnel. It's just the question of how long the tunnel is.

Do you have a story to share about navigating your career in your 50s? If so, please reach out to the editor, Manseen Logan, at mlogan@businessinsider.com.

• PHP, the open-source computer programming language, had two major vulnerabilities exposed.
• Yonaton Keller woke on Wednesday to panicked messages about the two PHP vulnerabilities.
• He shares three steps you can take to protect your website.

This as-told-to essay is based on a conversation with Yonaton Keller, a 46-year-old product manager at Zafran Security, based in Tel Aviv. His words have been edited for length and clarity.

When I woke up at 6:30 a.m. on Wednesday, I had multiple messages from around 4:45 a.m. alerting me that two vulnerabilities in the PHP programming language had been disclosed.

I immediately understood that this was a very serious situation.

Websites run different versions of PHP, and it's estimated that around 70% of websites worldwide use it. This isn't the first time PHP vulnerabilities have been found, but these ones require essentially no authentication on the attacker's part.

It's a very tricky situation. If it were a year and a half ago, nobody would have really responded to this so urgently. But this might be one of the first major incidents of its kind in this AI era, and the cycle of how attackers operate and how we typically respond is broken.

AI enhances detection and response times, but it also means that any limited-technical person could exploit these vulnerabilities within minutes.

My team was very concerned and had to act fast

I'm based in Israel, so when it was 6:30 a.m., my time, it was the middle of the night in the US. This time gap worked in our team's favor, as we had time to figure out what was going on before our customers woke up.

PHP is an open-source computer programming language used to create websites and web applications. It's such a widely used programming language that we immediately understood that every one of our customers, which includes major corporations and businesses, would likely be affected by this.

With bugs or critical flaws in the infrastructure, like the two that were found in PHP, exploitation is actually quite easy, especially if you use AI agents. That was the first thing we understood: even completely unskilled attackers can use these vulnerabilities to take down sites.

The PHP Foundation said it would disclose the details of the vulnerabilities and release a fix for newer versions of the language around 5 p.m. Israel time. But some details had already been informally disclosed on an online forum. The post was deleted minutes afterward, but screenshots spread around the internet quite quickly in unofficial forums.

So, my team and I dropped everything else and spent all day on Wednesday gathering informal information to see whether we could mitigate the risk of exploitation before an official fix was released.

How to tell if you're at risk

The first step people can take to figure out if they're impacted is to look at their websites and web applications, and try to understand where PHP is involved. You can also assume that most, if not all, of them will use PHP in some way, unless you have very basic HTML-based pages.

The second step would be to look at what vulnerability scanners online are telling you. Tenable, Qualys, and Rapid7 are usually the big three for releasing detection rules and actually detecting the vulnerability. In this case, these vulnerabilities have caused such widespread panic worldwide that they were quick to respond. This is also a way to understand the exact vulnerabilities in your internet-facing assets.

After taking these steps, immediately look online to upgrade your website to the current PHP version. It's quite easy to upgrade that, and it's free. There are some technical steps to do after the fix, so you might need a tech guy to implement them. If you don't update your PHP version, the impact on your business and website can be very, very serious.

Some people are also fully taking their sites offline, and I think that can be the right call if you have evidence that you are being targeted. However, 70% of the internet can't and shouldn't be taken offline just because those sites have some vulnerabilities. It's an emergency step to take if you have evidence of potential exploitation, but it can't be a step taken by everyone.

This was not just about attackers disrupting your website or web application; it was about them taking control of your server, stealing sensitive documents, moving inside your network, and then carrying out malicious operations, such as deploying ransomware or other actions they intended.

The situation has calmed down, but my cybersecurity team is still very concerned

Things have calmed down a bit since Wednesday, but we're still very, very concerned. Patching 70% of worldwide websites doesn't take a minute or two.

Hours after the fix was disclosed by the PHP Foundation, there were already tons of exploitation attempts popping up online. Attackers are getting quicker. I think that in this AI era, when in a matter of minutes, many attackers can attack, you don't have the time you used to.

The whole traditional process of scoping the attack surface, establishing a remediation plan, then calling a guy who's going to be responsible for this remediation plan, et cetera, is broken.

For a long period of time, organizations were investing a lot in what we call post-compromise scenarios. I think the AI era of cybersecurity will involve a lot more security investments in the pre-compromise realm, so defenses can be pre-built and ready for attacks in situations like this.