Skip to main content
Waffle works with any job description—from a one-sentence role description to a multi-page spec. However, the quality and relevance of your scorecard improve significantly when you provide detailed, well-structured input.

Automatic job description fetch

If you don’t have a JD handy, you can type a short role name like “Senior Product Manager” or “Staff Backend Engineer” into the chat. Waffle detects short inputs and automatically fetches a real job description from the web for that role. The fetched JD is used as the basis for your scorecard. When you paste a longer description (300+ characters containing typical JD keywords like “responsibilities,” “qualifications,” or “requirements”), Waffle recognizes it as a complete JD and skips the web fetch.

What to Include

The more context you give Waffle about the role, the better it can tailor competencies, questions, and scoring rubrics. Here’s what makes the biggest difference:

Role Title and Level

Be specific about seniority and specialization. Instead of “Engineer,” use “Senior Software Engineer” or “Staff Backend Engineer.” This helps Waffle calibrate the competency weights and question difficulty appropriately.

Key Responsibilities

List 5-10 bullet points describing the day-to-day work. What will this person actually be doing? Responsibilities help Waffle identify which competencies matter most and generate targeted interview questions. Example:
  • Design and implement RESTful APIs for customer-facing features
  • Lead code reviews and mentor junior engineers
  • Collaborate with product managers on technical feasibility

Required Skills and Qualifications

Include both technical skills (programming languages, tools, frameworks) and soft skills (communication, leadership, problem-solving). Waffle uses this to balance technical competencies with behavioral ones.

Team Context

Mention team size, reporting structure, and cross-functional partners. Does this person manage others? Work solo or on a large team? Collaborate heavily with non-technical stakeholders? This context shapes the competencies Waffle prioritizes. Example:
  • Reports to VP of Engineering
  • Leads a team of 3 engineers
  • Works closely with Product and Design teams

Company Culture and Values

If your company emphasizes certain values (e.g., innovation, collaboration, customer obsession), mention them. Waffle will generate culture-fit competencies to help you assess alignment beyond technical skills.

Formatting Tips

100+ words recommended for best results. Short descriptions work, but detailed JDs produce more nuanced scorecards.
Plain text works best. No need for HTML or special formatting—just paste the text directly into the chat.
Include both technical and soft skill requirements. Waffle balances hard skills (coding, data analysis) with soft skills (communication, leadership) to create well-rounded scorecards.
Mention interview format if known. If you’re planning a panel interview, case study, or technical whiteboarding session, include that. Waffle can adjust question types accordingly.

Examples of Good Input

Here’s a brief example of a well-structured job description input:
Role: Senior Product Designer

We're hiring a Senior Product Designer to lead the redesign of our mobile app.
You'll own the end-to-end design process from research to prototyping to delivery,
working closely with our product and engineering teams.

Responsibilities:
- Conduct user research and translate insights into design solutions
- Create high-fidelity prototypes and design systems
- Lead design critiques and collaborate with engineers on implementation
- Mentor junior designers and advocate for user-centered design

Requirements:
- 5+ years of product design experience, preferably in mobile
- Expert in Figma and prototyping tools
- Strong portfolio demonstrating user research and interaction design
- Excellent communication and stakeholder management skills

Team: You'll report to the Head of Design and work closely with a product manager
and 4 engineers. We're a remote-first team that values collaboration and iteration.
This input gives Waffle enough context to generate competencies like “User Research & Insight Translation,” “Visual Design & Prototyping,” “Cross-Functional Collaboration,” and “Mentorship & Design Advocacy.”
You can also describe the role conversationally. Try: “I need to hire a senior product designer who will lead our mobile app redesign and mentor junior designers.”
Avoid including candidate personal information (names, SSNs, medical data) in job descriptions. Waffle is designed for role requirements, not candidate evaluation data. Keep your inputs focused on the job, not the individual applicants.
Last modified on April 15, 2026