✅ Project Must Be Within Experience Block
-
RChilli only extracts project details when they are mentioned under or within the Experience section of the resume.
-
The project timeline must fall within the employment period. If a project’s dates do not align with the stated job duration, it will not be parsed.
✅ Keyword Requirement
-
To successfully identify and extract projects, the resume must explicitly include keywords like:
-
"Project Name:" -
"Project Details:" -
"Team Size:" -
"Role in Project:"
-
Without these structured labels, the parser may skip the information.
📄 JSON Output Format for Projects
When parsed correctly, each project is nested inside the corresponding experience block under the Projects array:
🔎 Additional Parsing Behavior
📌 Project Without Experience Block
-
If a resume only contains project data without any linked employer or job profile, project information will not be captured.
-
A valid Employer + JobPeriod combination is necessary to anchor the project information.
📌 Multiple Projects Support
-
RChilli supports parsing multiple projects per employer. Each is parsed into a separate object in the
Projectsarray, provided the formatting is consistent and clear.
📌 Fallback Behavior
-
In edge cases (like when projects are listed independently with clear job roles and timelines), RChilli may treat them as experience entries, especially if no distinct Experience block is present.
✅ Best Practices for Accurate Project Parsing
| Formatting Tips | Why It Matters |
|---|---|
| Mention “Project Name:” explicitly | Helps parser detect start of a project |
| Include team size, role, and skills used | Adds depth to parsed output |
| Align project date with experience date | Ensures parser links the project correctly |
| Avoid putting all projects in a standalone block without employer context | Projects will be ignored if unanchored |
If you are still not getting the right results, please reach us at support@rchilli.com.
Comments
0 comments
Please sign in to leave a comment.