The side-by-side editor
After importing a job, you will see the editor with two panels:
- Left panel: Edit form with all job fields
- Right panel: Live preview showing how developers will see it
Every change you make on the left updates the preview on the right instantly.
Editor sections
Job details
Basic information about the role:
- Title: Job title as it will appear to developers
- Level: Seniority (Junior, Mid, Senior, Staff, etc.)
- Department: Team or function (optional)
Tech stack
Technologies required for the role:
- Add languages, frameworks, and tools
- Mark skills as required vs. nice-to-have
- Be specific (e.g., "React" not just "Frontend")
Location
Where the work happens:
- Location type: Remote, Hybrid, or On-site
- Office location: City and country if applicable
- Timezone requirements: If remote has timezone constraints
Compensation
Pay and benefits:
- Salary range: Min and max base salary
- Currency: USD, EUR, GBP, etc.
- Equity: Stock options or RSUs if applicable
- Other benefits: Highlights worth mentioning
Important: Including compensation significantly increases developer engagement. We strongly recommend being transparent about pay.
Experience
What the role requires:
- Years of experience: Minimum required
- Required skills: Must-have qualifications
- Nice-to-have: Preferred but not required
Description
The full job description:
- Role responsibilities
- Team and company context
- Growth opportunities
- Anything else developers should know
Use clear, concise language. Avoid jargon and buzzwords.
The completeness bar
At the top of the editor, you will see a completeness bar showing:
- Green checkmarks: Completed required fields
- Orange indicators: Missing required fields
- Percentage complete: Overall completion status
You must complete all required fields before submitting for review.
Required fields
- Job title
- Tech stack (at least one technology)
- Location type
- Compensation range
- Job description
Recommended fields
- Experience level
- Department
- Specific benefits
- Company context
Editing tips
Be specific
- "3+ years of Python experience" not "programming experience"
- "Remote (US timezones)" not just "Remote"
- "$150,000-$180,000" not "Competitive salary"
Be honest
- Do not exaggerate requirements
- List true must-haves, not wish lists
- Be transparent about challenges and growth areas
Be developer-friendly
- Lead with what is interesting about the role
- Highlight the tech stack prominently
- Include team size and structure
- Mention development practices (agile, code review, etc.)
Preview your job
The right panel shows exactly how developers will see your job:
- Check formatting and layout
- Verify all information displays correctly
- Look for typos or errors
- Ensure it is compelling and clear
Save and continue
Your progress is saved automatically as you edit. You can:
- Leave and return later to continue editing
- Preview without submitting
- Make unlimited edits before submission
When ready, click Submit for Review to move to screening questions.
Troubleshooting
Changes not saving?
- Check your internet connection
- Refresh the page and try again
- Contact support if the issue persists
Preview looks wrong?
- Clear browser cache
- Try a different browser
- Report rendering issues to support