How Feedback Works
Timing: At the end of each invoice, you’ll have the option to leave feedback.
Visibility: Feedback may be shared with the developer, or it may remain internal to the Moonlight team.
Purpose: Even if not shared directly, your input helps Moonlight evaluate developer performance and support the overall community.
What to Comment On
When leaving feedback on an invoice, consider:
Quality of work: Was the output correct, complete, and useful?
Communication: Did the developer keep you updated and respond promptly?
Reliability: Were hours logged accurately and expectations met?
Best Practices
Be specific: Focus on concrete observations (e.g., “delivered API integration ahead of schedule,” “excellent async communication”).
Keep it professional: Feedback should be factual and respectful.
Use feedback regularly: Submitting comments on each invoice builds a more complete picture of the engagement.
Why It Matters
Supports Moonlight’s review process: Your feedback informs how we assess and support developers.
Helps developers improve: Shared comments can guide better practices in future projects.
Improves your own hiring outcomes: Consistent feedback helps ensure the developer community stays strong and reliable.
FAQs
Do I need to leave feedback on every invoice?
No, but it’s encouraged. Even short comments help improve the system.
Is my feedback always shared with the developer?
Not always. Some feedback remains internal to the Moonlight team, while some may be shared with the developer to help them improve.
Can developers rate companies too?
No. Currently, feedback flows one way — from companies about developers.