IBBS is a good place to work, but can be unstable financially - Project Manager IBBS Employee Review

4.0
Apr 14, 2010
Recommend
CEO approval
Business outlook

Pros

Collegial "can-do" culture Interesting work--industry pioneer Good relationships with customers Significant growth opportunities Freedom to pursue new directions with management approval

Cons

Financial stability No job security Terminations can be arbitrary Infighting amongst senior management High turnover in certain departments (e.g., Finance)

Explore other reviews about IBBS

1.0
Mar 5, 2014
Anonymous employee
Recommend
CEO approval
Business outlook

Pros

high salary, very good benefits in health- medical dental and vision, 401k, as well as vacation. Casual wear to work.

Cons

deceptive management - deceptive internally and to customers. Untrustworthy executive team. HR Team lies to incoming candidates/new hires regarding location (ie watched a candidate accept an offer based on their work location being at IBBS's new "in-town, Atlanta" office, which was a complete farse). HR does not properly file legal documentation when employees separate from the company. Upon my exit - which was voluntary - I had to file a complaint with the Department of Labor because of their failure to properly document and file the necessary documents my departure. I watched management lie to current and prospective customers, IBBS employees, and candidates/new hires. Disgusting, and most unprofessional environment I've been in. I was fortunate to find another opportunity and run - most employees who caught on to managements deception were canned. (Even those who put in two weeks notice were walked out because they pissed an executive team member off.

2
3.0
Jul 31, 2015
Recommend
CEO approval
Business outlook

Pros

I really enjoyed the work environment of a smaller company, relaxed atmosphere and the developers were separated from rest of the company's employees

Cons

Smaller Company couldn't compete with larger corporations salaries, procedures from back when company was first started have been carried through and are still common practice in one form or another.. Since the company is not flush with cash, they are unable to afford the refactoring (of both processes and code) needed to do things in a more standardized and modern fashion. So over all there remains a lot of special cases (code/software wise as well as in the network architecture and configuration, etc.

See reviews by: Helpful|Rating|Date|All