How to decide whether a job is worth applying to

Most job searches lose their time in the same place: the pile of postings that are neither clearly right nor clearly wrong. You read one, feel uncertain, save it, and return to it three times before applying anyway at midnight. The cost is not the application. It is the hours of unresolved deciding around it.

A decision framework fixes this, and it does not need to be complicated. Four questions, asked in order, answer almost every case in under ten minutes.

1. Would you accept this job if it were offered on Friday?

Not the version of the job you are imagining — the one described in the posting, at the pay written on it, in the location and work model stated. If the honest answer is no, the rest of the questions do not matter. Close the tab. If the answer is 'only if the salary moved', treat the top of the posted band as the real offer and answer again.

2. Can you evidence the required list?

Required and preferred are different promises. Required means the employer does not expect to hire without it. Preferred means it improves your case. Go through the required list and, for each item, name the specific role, project or period where you did that thing. Not 'I could do that' — where you did it.

If you can evidence all of the required items, you are a strong applicant. If you can evidence most and the gaps are learnable, you are a legitimate applicant and should say something about the gap rather than hoping nobody notices. If you cannot evidence the majority, this is a stretch application, and stretch applications are worth making rarely and deliberately, not in batches.

3. Do you understand what the work actually is?

Some postings describe a job. Others describe a department. If, after reading, you could not explain to a friend what this person does on a Tuesday, that is a signal about the role and often about the process behind it. You can still apply — but ask about it in the first conversation, and expect a specific answer.

4. Is there anything here you would want to ask about before starting?

Write those questions down now, while you are reading carefully. They are the best interview questions you will have, and they will be gone by the time you get an interview if you do not capture them.

What this looks like on Rice & Bean

Every posting on Rice & Bean states its pay range, its work model, and its requirements split into required and preferred. Applications cost a Bean, which is a small, deliberate friction: it exists so that applying is a decision rather than a reflex. The framework above is simply the decision the Bean is asking you to make.

A decision you can explain out loud is a decision you can defend in an interview. That is the whole point of slowing down at this step.

When the answer is no

Say no properly. Do not save it, do not maybe it. A search with ten live applications you believe in is calmer, easier to follow up on, and easier to talk about than a search with sixty you have half-forgotten. Save the effort for the postings that survived all four questions.