Dealer Tire Reviews

Pros

Home work life balance Incentives for achieving company goals/ exceeding Positive atmosphere and culture Play to win attitude Makes me feel like I’m apart of something great Opportunity for advancement Huge support team so you are never alone

Cons

Haven’t come across one yet!

Pros

Lots of Hours to work

Cons

Everything is always your responsibility

Pros

Great Benefits & PTO time. Excellent perks that come with the job.

Cons

long hours to complete daily tasks. corporate leadership

Pros

great with people, positive attitude

Cons

They're not enough hours in A-day to get the job done

Pros

* A pretty decent IT infrastructure. You'll mostly have the tools, access, bandwidth, and equipment to do your job. * Full work-from-home, with very flexible schedule, and a 40 hour work week. Work/life is not an issue here. * The company overall is pretty stable. No major mergers or acquisitions, corporate shakeups, etc. At least none that will impact your job. * Pay and benefits are pretty competitive

Cons

The main job in application development is: take this existing software, add a little functionality, and try to improve it a bit while you’re in there. So why is so much time on process? For every three developers there’s a scrum master, manager, someone else’s manager, a business analyst/product owner, and a schedule that includes all these people in a dozen different meetings every sprint, to challenge every design decision down to the tiniest implementation detail. A director might also come to critique the code. That’s just for the coding part of your job. Deploying your little feature will involve navigating a deploy process that’s weighed down by multiple levels of technical and bureaucratic complexity. All of this is interlaced with more meetings to examine the whole process itself. Is scrum working for us (spoiler alert: yes)? Do we need a couple more meetings or a couple less, or instead should we make the meetings themselves longer or shorter? No detail, no musing or question or error during deployment, is too small to discuss in depth, with every single team member, all the time. “How might we?” Is the innocent question. Which is great— the Blue Angels do this after every show. But, a) you’re a professional so you’re already trying to improve things a bit as you code, and b) you’re still just a team of three developers who spend more time meeting than coding, and c) the Blue angels have a two year tour. Drastic COVD layoffs both in IT and across the company, along with inept micro-managers who are somehow both omnipresent and unaware, have bled most of the senior talent out of IT (programmers, business analysts, and devops alike). So the complex, and sometimes interesting, job of maintaining and improving the giant nest of legacy code, will be aided by mostly new-ish peers who are talented but unfamiliar with the legacy code base, a handful of old-timers who are also friendly but spread thin, and a team of micromanagers who will turn your simple question into a complex one. Like many IT shops in maintenance mode, this one enjoys a code base that mostly works just fine. So everyone’s a little gun-shy to make too many changes to it, and the business as a whole is change-averse. At the same time, the CTO and VP feel the need to show how innovative IT is, because running a utility is boring on an executive CV. Whatever exciting new “initiatives” you hear about in your interview will never actually materialize. They’re just answers dreamed up in a “how might we?” meeting.