codebase
- open roles
- 5
- added, 30 days
- 1
- removed, 30 days
- 0
- remote
- 0%
- state their pay
- 0%
Postings added vs. removed, last 30 days
- Added 1
- Removed 0
- Net +1
Added uses the date codebase gave, or the day we first saw a role after the first crawl. Removed is the day a role's last listing disappeared from its source.
What they hire for
Matched on job titles; one role can count in two fields.
Teams with openings
As the employer labels them on its careers site.
Where the roles are
Busiest locations
- Pune, Baner, IN 5
How and when
Work mode
- Not stated 100%
Contract
- Full time 100%
How fresh
- 1–4 weeks 20%
- 1–3 months 60%
- Over 3 months 20%
What they pay
0% of open roles state pay (0 of 5).
Too few roles state pay to show a range.
Lower quartile, median and upper quartile of each advertised range's midpoint. Never converted.
Where we find them
- Breezy HRATS5
Each role links straight back to where codebase posted it. Duplicates across boards count once.
Figures refreshed just now. Listing an employer does not imply a partnership or endorsement.