Founder Field Note: Our Evergreen Role Was a Resume Aquarium

The role was “open” the way a museum is “hiring” dinosaurs

A few years ago, we had a customer success problem.

Churn was creeping up. Our onboarding docs looked like they had been assembled during a fire drill. Sales kept closing customers who needed a white-glove implementation, while our actual team had two gloves total and one of them was a spreadsheet.

So we agreed we needed a Customer Success Manager.

Then finance did what finance does when a small company is scared: it looked at the burn rate, made a face like it smelled warm yogurt, and said, “Not yet.”

No headcount. No approved start date. No salary band locked. No interviewer availability. Just a general belief that someday, after revenue behaved like an adult, we would hire.

And yet the job post went live.

Not as “future opportunity.” Not as “talent community.” Not as “we are building a pipeline because our planning process is held together by vibes and quarterly hope.”

It said:

Customer Success Manager — Remote — Full Time

Then, because we were apparently doing HR taxidermy, we added urgency language:

We’re growing fast and looking for someone to join our team.

No. We were not growing fast. We were staring at a dashboard and whispering, “Please.”

That posting collected hundreds of resumes. Good resumes. People with onboarding experience, renewal saves, stakeholder management interview stories ready to go, actual proof blocks from real customer fires they had put out without becoming LinkedIn philosophers.

And our applicant tracking system treated them like inventory.

Candidate takeaway:

• A job post can describe a real business need without representing an active funded req.
• “We need this person eventually” is not the same as “we are ready to hire this person now.”
• If the post has urgency language but no clear timeline, assume you need to verify the pulse before investing serious time.

The pipeline sounded responsible. It behaved like a swamp.

Internally, nobody said, “Let’s waste candidates’ time.”

That’s the annoying part. Most broken hiring systems are not built by villains in ergonomic chairs. They’re built by busy people making one tiny cowardly choice at a time.

The recruiter said, “Let’s keep the posting up so we have warm candidates when the req opens.”

The hiring manager said, “Sure, as long as we don’t overcommit.”

I said something founder-ish and useless, like, “Great, let’s stay close to the market.”

Congratulations to us. We had invented the evergreen role: a posting that lets a company browse humans before it has permission to buy.

The candidate screening process looked normal from the outside:

1. Resume submitted.
2. Auto-confirmation email.
3. A few applicants pushed through a resume filter bot.
4. Some got a recruiter note.
5. A smaller group got an automated hiring screen.
6. A few even got a one-way video interview.

From the candidate side, that feels like traction. From the company side, it was mostly market research with calendar invites.

We weren’t evil. We were worse: operationally vague.

We had no hiring SLA. No rule that said, “If this role is not funded, candidates do not enter interviews.” No trigger that paused the posting after thirty days. No requirement that the recruiter disclose pipeline status.

So the system kept breathing.

It inhaled resumes. It exhaled silence.

Candidate takeaway:

• “Pipeline” is recruiter-speak for “maybe later” unless paired with budget, timeline, and decision owner.
• If you get moved into an AI interview screen before speaking with a human, treat that as a signal to verify whether the role is real enough for your time.
• Track Time-to-Human in your job search dashboard. If a source produces screens but not humans, it may be a bot wall wearing a blazer.

Maya was qualified. Our process made her wait in a lobby that had no building.

One candidate — call her Maya — should have been exciting to us.

She had managed onboarding for mid-market accounts, rebuilt a customer health scoring workflow, saved a messy renewal by coordinating product, support, and sales, and could explain the difference between “customer success” and “being everyone’s emotional recycling bin.”

Her resume was not keyword confetti. It was clean evidence.

The ATS liked her. The recruiter liked her. The hiring manager liked her.

So we sent her the automated screen.

The bot asked normal-ish questions with that cold little interrogation-room energy:

Tell us about a time you handled a difficult customer.

Describe your approach to cross-functional collaboration.

How do you prioritize competing customer needs?

Maya answered well. Not perfectly, because nobody sounds fully human when talking to a blinking upload box, but well. She used examples. She gave metrics. She named tradeoffs. She did not say “I’m passionate about delight” like a cursed brochure.

Then the process stalled.

Why?

Because there was no role to move her into.

The hiring manager said, “Let’s keep her warm.”

Warm. What a hideous phrase. Candidates are not soup.

Two weeks passed. Then three. The recruiter sent one “still aligning internally” message, which is bot-speak for “the humans have not admitted what is happening.”

Eventually Maya followed up with the question we should have answered before asking her to record anything:

Is this position currently approved and funded, with an intended start date, or is this an evergreen pipeline role?

That sentence hit the room like someone turned on fluorescent lights in a nightclub.

We had to answer honestly.

It was pipeline.

Maya withdrew. Politely. Correctly. With more professionalism than the process deserved.

Candidate takeaway:

• Ask the funding question early, especially before any one-way video interview or take-home.
• Use direct language: “Is this an approved, funded role with an active hiring timeline?”
• If they dodge with “we’re always looking for great people,” translate that as “not enough signal to prioritize.”

The three flavors of evergreen posting

Not every evergreen job post is trash. Some are legitimate.

Hospitals, retail groups, high-volume support teams, seasonal employers, and large field organizations may keep ongoing postings because they hire continuously. That is not automatically a ghost job.

The problem is when companies use the same mechanism for roles that require a specific manager, budget approval, and team need — but forget to tell candidates the opening is theoretical.

Here are the three versions you’ll run into.

1. The real evergreen

This is a recurring role with constant openings.

Examples:

• Customer support representative at a large support center
• Warehouse associate for multiple locations
• Registered nurse roles across a hospital system
• Sales development roles in a high-turnover org

These can still have a clumsy candidate screening process, but the need is real. The company hires this profile repeatedly.

Green flags:

• Multiple openings or locations are listed.
• Recruiter can explain hiring classes or start dates.
• The interview process is standardized and fast.
• Human Contact Rate is decent: people actually respond.

2. The future pipeline

This is the “we expect to need someone like this” role.

It may become real. It may not. It lives in budget purgatory eating resumes with a tiny spoon.

Yellow flags:

• “We’re building our bench.”
• “Timing is flexible.”
• “We don’t have a specific start date yet.”
• The post stays up for months with no visible changes.
• Recruiter talks about “getting to know you” more than the actual team problem.

3. The fake active req

This is the swamp creature.

It looks like a real job. It may even have interviews. But the company has no current intention or ability to hire.

Red flags:

• The job has been reposted repeatedly with the same wording.
• Nobody can name the hiring manager’s urgent business problem.
• They push an automated hiring screen before answering basic role questions.
• You get vague job rejection language like “timing changed” or “we went in a different direction” while the role remains posted.
• You see job interview ghosting after they praised your background.

Candidate takeaway:

• Your goal is not to avoid every evergreen role. Your goal is to identify which kind you’re dealing with.
• Real evergreen roles have hiring machinery. Fake active reqs have fog, delay, and stale job postings.
• The more senior or specialized the role, the less acceptable it is for the company to hide behind “always hiring.”

The Evergreen Reality Check: five questions before you donate your week

You do not need to interrogate the recruiter like a tax auditor with espresso poisoning.

You do need to ask enough to separate opportunity from compost.

Use these before you accept a screen, take-home, or panel.

Question 1: “Is this role approved and funded today?”

Not “is the team growing?”

Not “is this a priority?”

Approved. Funded. Today.

A real answer sounds like:

Yes. The req is approved, compensation range is set, and we’re targeting a start date in October.

A fog answer sounds like:

We’re still aligning internally, but we’re excited to meet strong candidates.

Excitement does not pay rent. Alignment is where decisions go to wear a little sweater and die.

Question 2: “What changed that created the opening?”

You want the business trigger.

Good answers:

• “A team member was promoted and we need to backfill.”
• “We signed three enterprise customers and need onboarding coverage.”
• “We split support and success because renewals were suffering.”

Bad answers:

• “We’re always looking for great talent.”
• “The team is evolving.”
• “Leadership wants to see who’s out there.”

That last one is not a job. That is corporate window shopping.

Question 3: “Who is the decision maker, and are they interviewing now?”

If there is no decision maker, there is no decision.

You are trying to avoid being evaluated by a committee that has not agreed a human should exist in the seat.

Question 4: “What is the target decision timeline?”

Listen for dates, not vibes.

Good:

Recruiter screen this week, hiring manager next week, panel the following week, decision by the 30th.

Bad:

We move quickly for the right person.

That sentence has personally wasted enough candidate hours to qualify as infrastructure damage.

Question 5: “How many candidates are currently in process?”

They may not give an exact number. Fine.

But the shape matters.

If they say, “We’re early and speaking broadly,” that can mean you are entering the aquarium. If they say, “We have three finalists and are adding one more,” you know the risk.

Candidate takeaway:

• Ask these questions before high-effort steps, not after you have emotionally moved into the job.
• You are not being difficult. You are checking whether the employer has done the minimum adult paperwork.
• If the answers are vague, lower the priority of that role in your job search dashboard.

Score the role, not your hope

Hope is a terrible CRM.

It makes every “quick sync” feel meaningful. It turns a recruiter’s smiley face into a forecast. It convinces you that silence is complexity instead of disrespect.

So score the role like an operator.

Create a simple Evergreen Risk Score from 0 to 10:

• +2 if the posting is older than 45 days with no meaningful update.
• +2 if it has been reposted more than once.
• +2 if no one confirms it is an active funded req.
• +1 if the first step is an automated hiring screen before a human conversation.
• +1 if the recruiter cannot name the business trigger.
• +1 if the timeline is “flexible” or “moving quickly for the right person.”
• +1 if your Time-to-Human is over seven days after applying.

Then act accordingly:

• 0–2: Apply normally, but still track it.
• 3–5: Apply only if you can route to a human or the role is a strong match.
• 6–8: Treat as low-priority. Use a lighter application, no unpaid work, no emotional pre-spending.
• 9–10: Skip unless you have insider confirmation the req is real.

This is not cynicism. This is energy management.

The modern market punishes candidates who treat every posting like a sacred door. Many are not doors. Many are painted rectangles on a wall.

Candidate takeaway:

• A role with high evergreen risk does not deserve premium effort.
• Save deep customization for roles with real hiring demand, human contact, and visible urgency.
• Your application strategy should reward evidence, not job-board theater.

What to send when you still want the role

Sometimes the role is suspicious, but the company is interesting. Fine. Don’t rage-delete your future. Just stop feeding the machine blindly.

Send a short note that creates a human route and asks for reality without sounding like you’ve been radicalized by LinkedIn job posts. Even if you have. Understandable.

Try this:

Hi [Name], I’m interested in the [Role] because my background maps closely to [specific business problem or requirement]. Before I complete the next step, could you confirm whether this is an approved active req with a target start date, or an evergreen pipeline role? Happy to proceed if there’s a current hiring timeline.

If you already did the AI screen:

Hi [Name], I completed the screen and remain interested. To calibrate next steps, is the team actively selecting candidates for this opening now, or keeping a pipeline for future headcount? If active, I’d be glad to share a short role-evidence map showing how my experience fits the scorecard.

That phrase — role-evidence map — matters. It tells the human you are not just “checking in.” You are ready to make the match easy.

If you are preparing for an AI screen anyway, this is where using a tool like NoSweatKing can help: it decodes questions and helps you answer in your own voice, so if you do spend time with the bot, your proof is at least bot-readable instead of being sacrificed to transcript soup.

Candidate takeaway:

• Do not beg for updates. Ask for status and offer evidence.
• Keep the note short enough that a recruiter can answer it between meetings.
• If they will not confirm the role is active, do not escalate your effort.

The painful truth: companies use your patience as a storage layer

Evergreen postings are attractive to companies because they transfer uncertainty onto candidates.

The employer gets optionality:

• A stack of resumes if budget opens.
• Compensation intelligence.
• A sense of market availability.
• Backup candidates if someone quits.
• The warm glow of “talent pipeline” on a slide deck.

The candidate gets… what, exactly?

A confirmation email. Maybe a bot interview. Maybe a recruiter call. Maybe three weeks of checking Gmail like it owes you closure.

This is the bargain modern hiring keeps trying to normalize: companies keep their options open while candidates keep their lives on hold.

No.

You can be open to opportunity without becoming free storage for someone else’s planning failure.

Candidate takeaway:

• Treat unclear roles as leads, not commitments.
• Keep applying, networking, and interviewing until you have a real offer.
• Never let a vague process stop your momentum. Silence is not a relationship.

The founder apology, translated into candidate strategy

If I could go back, I would have forced one rule:

No unfunded role gets an active job post that looks like a funded role.

If we wanted a future pipeline, we should have said so in the first paragraph. If we wanted market research, we should have paid for it instead of laundering it through candidate hope. If we wanted to “keep people warm,” we should have remembered people are not leftovers.

Maya did the right thing. She asked the adult question. She got the truth. Then she left the aquarium.

That is the move.

Not bitterness. Not self-blame. Not refreshing the careers page like a medieval peasant waiting for rain.

Verification.

Here is your compact workflow:

1. Check the post age and repost count. Stale job postings are not automatically fake, but they start the investigation.
2. Look for a human route. A recruiter, hiring manager, employee, or credible referral increases Human Contact Rate.
3. Ask if it is an active funded req. Use those exact words.
4. Ask what created the opening. Real jobs have business triggers.
5. Score the risk. Don’t give premium effort to low-reality roles.
6. Protect your proof. Build proof blocks and a role-evidence map for serious opportunities, not every job-board mirage.
7. Keep moving. Until there is a signed offer, your pipeline belongs to you.

The broken hiring system wants you to confuse motion with progress.

A submitted application is motion. A bot screen is motion. A “we’re still aligning” email is motion wearing deodorant.

Progress is a human with authority moving you toward a decision.

Everything else goes on probation.