Decent company, not the greatest job out there - Call Center Representative bei IDIQ: Mitarbeiterbewertung

3.0
21. Dez. 2021
Empfehlen
CEO-Befürwortung
Geschäftsprognose

Pros

- Job stability - Benefits after 30 days

Kontras

- Long work days dealing with rude, aggressive people - Customer service job, however, you are required to have a minimum save rate (sales) - Micro managing - Not much room for improvement, unless you suck up to everyone who's in management - They don't take care of current employees, they just replace them every few months

Mehr Bewertungen zu IDIQ entdecken

5.0
18. Nov. 2025
Empfehlen
CEO-Befürwortung
Geschäftsprognose

Pros

You get exposure to both manual and automation testing (Selenium, Cypress, Playwright). Great place to develop full-stack QA skills: UI, API, backend data validation.

Kontras

Some older parts of the platform require extra manual verification. Technical debt sometimes makes automation harder.

4.0
14. Apr. 2025
Empfehlen
CEO-Befürwortung
Geschäftsprognose

Pros

Exposure to Diverse Technologies: Ryan gained experience with a wide range of technologies early in his career, including C#, VB.NET, .NET Framework, JavaScript, jQuery, and SQL Server[cite: 68]. This broad exposure likely provided a solid foundation and allowed him to explore different areas of software development. Full-Stack Experience: His role as a Junior Full Stack Developer indicates he was involved in both front-end and back-end development from the beginning[cite: 68]. This holistic experience is valuable for understanding the entire software development lifecycle. Database Skills Development: He gained experience working with SQL Server, including writing queries and stored procedures[cite: 68]. Database skills are fundamental for many software development roles. Early Career Growth: Starting as a Junior Full Stack Developer suggests an opportunity for growth and learning within the company.

Kontras

Junior Level Responsibilities: As a junior developer, Ryan likely had more limited responsibilities and less autonomy compared to senior roles. Decision-making power and influence on architectural choices would likely have been lower. Potential for Less Specialization: While broad exposure is a pro, it might have meant less opportunity to deeply specialize in a particular technology or domain at this early stage. Mentorship Quality (Unknown): The resume doesn't provide information about the quality of mentorship or guidance received as a junior developer. The level of support can significantly impact early career growth. Complexity of Projects (Unknown): The "various projects" could have ranged in complexity. As a junior, he might have been assigned to less critical or less technically challenging tasks initially. Salary and Benefits (Not Mentioned): The resume doesn't provide any information about compensation or benefits, which are important factors in evaluating an employer. Junior roles often have lower salaries.

Bewertungen anzeigen nach: Hilfreich|Sterne|Datum|Alle