Start With The Center Of Gravity
A healthy job posting has a clear center of gravity. The title, first paragraph, duties, qualifications, and success measures all point toward the same kind of work. A communications role mostly communicates. A help-desk role mostly supports users. A lab role mostly works with lab equipment. Real jobs can be broad, but they usually have a home base.
Scope creep starts when the home base gets blurry. The title says specialist, but the duties add project management, reporting, training, vendor follow-up, documentation, emergency support, and a catch-all clause that looks suspiciously well rested. One or two adjacent duties may be normal. A whole second job family is where the posting starts rearranging the furniture.
The useful question is not whether the posting is bad. The useful question is whether the posting explains how the work is prioritized. If a job lists strategy, daily support, training, documentation, and cross-team coordination, it should also explain which duties own the calendar and which duties are occasional. If everything is first priority, the calendar has already left the meeting.
Watch The Verb Pile
Scope creep often hides in verbs. A posting that asks someone to design, develop, implement, administer, train, troubleshoot, document, evaluate, coordinate, and support may be asking for a complete department in sentence form. The nouns matter too, but the verbs tell you how many modes the person has to switch between.
Mode switching is expensive. Building something new and supporting what already exists are different mental gears. Training users and writing documentation are different from triaging tickets. Coordinating with vendors is different from owning the final outcome. When a posting stacks too many verbs without explaining boundaries, the role may become a daily game of 'which hat is on fire now?'
That does not mean you should ignore broad roles. Some people like variety. The issue is transparency. A posting can say, clearly, that the role is 50 percent support, 25 percent project work, 15 percent documentation, and 10 percent training. That kind of split turns fog into a map.
Look For The Trapdoor Clause
Other duties as assigned is common language. It does not automatically mean danger. The problem is where it appears and what came before it. If the posting already listed a reasonable role, the clause may simply cover normal flexibility. If the posting already listed five job families, the clause is not a footnote. It is a tiny door with excellent manners.
The best move is to ask for examples. 'What kinds of duties have fallen under this clause in the past?' is a calm, practical question. It invites specifics without sounding combative. If the answer is occasional event help or a short-term project, fine. If the answer is a rotating grab bag of recurring work, you have learned something useful before donating your afternoon.
Also ask who decides when the clause activates. A catch-all duty is less risky when it has a clear manager, clear frequency, and clear relationship to the role. It is riskier when every team can drop something into the basket and nobody names the lid.
Read The Calendar, Not Just The Title
A job title is branding. The duties are the calendar. Scope creep becomes visible when the duties compete for the same hours. A role can be both strategic and hands-on, but only if the posting says what happens when support tickets arrive during project deadlines. A role can coordinate with many teams, but only if decision ownership is named.
If the posting includes deadlines, shifts, events, physical requirements, travel, on-site requirements, or support coverage, those details are not side notes. They shape the week. A remote-sounding platform role with a commute rule is not the same as a fully remote role. A student tech role with lifting and delivery is not just a desk job with a laptop.
Your goal is not to catch the posting doing something wrong. Your goal is to see whether the work has edges. Edges make jobs manageable. Fog makes every task feel like it might bring luggage.
Quick Takeaways
- Compare the title to the actual duties, not the tone of the introduction.
- Count verbs that require different work modes.
- Ask which duties are core, occasional, and future-state.
- Treat catch-all clauses as questions, not automatic dealbreakers.