dgetty/rule-jobposting icon
public
Published on 4/9/2025
dgetty/rule-jobposting

Rule for a job post developer assititant.

Rules

Job Title & Metadata Guidelines

  • Use a clear, standardized title (e.g., "Senior Data Scientist", "Junior Python Developer"). Include relevant keywords for SEO.
  • Add meta-tags: Department, location(s), employment type (full-time/part-time/remote), and application deadline if applicable.

Opening Statement Guidelines

  • Write a brief paragraph introducing the companys mission, values, or culture. Highlight why someone would want to join this organization.
  • Example: “Join [Company Name], where innovation meets impact! We are seeking a dynamic [Job Title] to drive [specific outcome].”

Key Responsibilities Guidelines

  • List 5-8 bullet points of core job duties. Use action verbs (e.g., “design,” “analyze,” “collaborate”) and avoid excessive technical jargon unless critical to the role.
  • Prioritize daily tasks, deliverables, or projects specific to the position.

Qualifications & Requirements Guidelines

  • plit into subsections: Must-Have Skills (mandatory) and Preferred Experience/Qualities (optional).
  • Include technical skills, certifications, education level, years of experience, and tools/platforms (e.g., Python, AWS, SQL).
  • Mention soft skills (e.g., teamwork, problem-solving) if relevant.
  • Avoid overly restrictive criteria unless absolutely necessary; focus on growth potential.

What We Offer Guidelines

  • List benefits: competitive salary, health care, PTO, retirement plans, professional development opportunities, flexible work options, or company perks.
  • Highlight unique selling points (e.g., remote-friendly policy, equity options, industry recognition).

Application Process & Requirements Guidelines

  • Specify how to apply: online portal URL, email submission guidelines, required documents (resume, portfolio links, cover letter), and deadline.
  • Instruct applicants to include a subject line with the job title for sorting.

Tone & Style Guidelines

  • Use professional yet engaging language; avoid passive voice and overly formal phrasing.
  • Keep paragraphs concise (3-4 lines max) for readability. Use bullet points/sections with bold headings.
  • Avoid biased or exclusionary terms (e.g., “ninja,” “rockstar”) unless the company’s culture explicitly uses such slang.

Compliance & Legal Guidelines

  • Include standard disclaimers: “This role is contingent upon successful background checks and verification of eligibility to work.”
  • Ensure compliance with local labor laws (e.g., ADA, EEOC requirements).

Do Not Include Guidelines

  • Hyperbolic language (e.g., “best in the world”).
  • Biased or discriminatory phrasing.
  • Overly technical jargon without context.
  • Unverified salary figures (unless explicitly provided).