Changing...Fast. - Market Development Representative SAP Concur Employee Review

2.0
20 Sept 2016
Recommend
CEO approval
Business outlook

Pros

Great co-workers, nice office, fair PTO, and opportunity to make decent commission for an entry level job. Other departments have great culture.

Cons

The Market Development department is going down the drain. In the last five months, under new management and a "transformation" the department has gone from a strategic, partner driven and creative marketing role to a cold calling center. Before this transformation you had a monthly goal and you were able to strategize with the sales team on creative ways to drive new business. Everything from email campaigns, events, and marketing tactics that required creativity and strategy. Now you are required to sit on an automatic dialer for a minimum of 2.5 hours which will increase to 5 hours by the end of the year. That is a promise. You are required to have over 500+ dial attempts and at least 15 conversations every day and this too will increase to over 30 soon. Everything is recorded and you are constantly being critiqued and picked apart. They are also mandating the use of pre-written emails from marketing so there will be no creativity there either. Market development has become a robotic, insanely boring department. If you are hoping for a role where you simply show up, sit on a dialing system and cold call all day long than this will be a good fit for you. But I stress there is zero creativity, extreme micro-management and employee morale is at an all time low.

Explore other reviews about SAP Concur

5.0
28 Apr 2026
Recommend
CEO approval
Business outlook

Pros

Work life balance is great

Cons

Forgot about growth unless switch teams which is very difficult

1.0
26 May 2026
Recommend
CEO approval
Business outlook

Pros

Compensation & Benefits: The benefits package, including health insurance and the unlimited sick leave policy, is solid and competitive. Peer Group: There is a subset of highly intelligent, hardworking individual contributors who genuinely care about the product and engineering excellence. Slow Pace (until it isn't): For those looking for a slower-paced environment, the workload is manageable and expectations are low, making it a comfortable place to coast in the short term. The exception is when everyone realizes there is a deadline and someone has to pull some heroics to make up for mismanagement. If you are not this hero, then you can continue to relax.

Cons

Operational Offloading: The recurring annual layoffs and reorganizations have severely damaged team structures. Eliminating specialized QA teams and PMs has not streamlined the organization; instead, it has dumped non-engineering overhead (like running manual test suites and project management) directly onto software engineers, distracting them from core development. Stagnant Tech Stack & AI Paralysis: The technical direction is hampered by conservative decision-making and a slow-to-paranoid adoption rate of newer technologies. A heavy reliance on legacy systems, combined with extreme hesitation around modern industry tools and AI, has left the product architecture lagging behind industry standards. Internal Team Toxicity: While individual experiences vary, middle management is usually quite toxic but frequently lacks objective accountability. Active, high-performing engineers who advocate for structural or process improvements are often targeted. Performance evaluations, compensation allocations (such as bonuses), and leadership opportunities (like Team Lead tracks) are sometimes leveraged punitively to reward quiet compliance over actual technical merit. Useless Skip-Level Paths: The escalation path is structurally broken. Skip-level managers and directors consistently default to protecting the middle-management hierarchy to avoid conflict, completely ignoring valid documentation of retaliation and favoritism. Inter-Team Friction & Duplication: Product verticals operate in silos, creating massive friction. Feature teams regularly bypass platform architectural standards or duplicate core services (even attempting to split off competing apps) just to circumvent platform dependencies. This political maneuvering results in disjointed, fragmented end-user experiences. Parent Company Resistance (Concur vs. SAP): There is an internal narrative that Concur must remain "special" and separate from SAP. Local leadership frequently resists standardizing SAP-wide operational policies, such as unified design languages, centralized security/privacy frameworks, and modern, structured agile practices, hindering true product maturity, even when engineers are begging for anything to improve conditions. Attrition: With all the above issues, there are no good, motivated engineers left. The ones who were brave enough to speak up or act to improve things were either chased away by the toxic people and environment or beaten down into apathetic obedience.

See reviews by: Helpful|Rating|Date|All