5

I came up with a much longer version of this but here is the skinny:

As a new employee, I was tasked to create an application. I did all my core work on time but the underlying database architecture was not up to the job and causing major delays.

To have something to show, I created a proof of concept using a different database architecture, which worked fine, but management was adamant I use their solution and unhappy the project was slipping.

I created a second demo using the "correct" architecture, which everybody promptly hated because it was very slow and sometimes failed due to a vendor bug.

I was then written up and given six months to "turn things around". To help with the database architecture, the company assigned a team of data engineers to fix the problem. They are still at it four months later while the project languishes. Vendor still hasn't fixed the bug.

I have been working on other things in the meantime and haven't missed any deadlines, but I was told I have two months to "improve", although the definition of improvement is totally nonspecific, consisting of "better collaboration", "better understanding" and "better enthusiasm".

My gut tells me they need to throw somebody under the bus to appease management and a relatively new employee probably fits the bill. I also get the impression that if somebody says you need to improve but can't really say exactly what it is you need to improve, you are probably already done for. Should I bail now while I still have a job or wait and see if maybe this will all blow over?

closed as off-topic by Philip Kendall, gnat, Mister Positive, Michael Grubey, Draken Jun 29 '17 at 6:22

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Philip Kendall, gnat, Mister Positive, Michael Grubey, Draken
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 5
    Why would you wait? Do you actually want to work at a company that has treated you this way? – nardnob Jun 28 '17 at 21:00
  • 5
    Do you understand what you did wrong yet and why it was a very bad mistake? You cannot ever willy nilly replace a backend database without a great deal of discussion and official permission even for a demo. You did double the work. Instead you should have documented the issues and suggested ways to refactor it to get to where you needed to be. Likely other applications were dependent on this data in this database and to just decide not to use it because you were having trouble making it work was a huge mistake and one that would have gotten you fired pretty much anywhere I ever worked. – HLGEM Jun 28 '17 at 21:36
  • 2
    "underlying database architecture was not up to the job" What the heck? Every "underlying database architecture", ever, in the history of computing, has been crap. Note that the two alternates you tried were also total crap. It's amazing they let you waste time fooling around on those experiments. For goodness sake, just do it using the backend given. – Fattie Jun 28 '17 at 21:38
  • 4
    @Fattie Really, every "underlying database architecture", ever, in the history of computing had been crap. Your comments are crap. – paparazzo Jun 28 '17 at 21:49
  • 1
    Hi @kmccarty dude. The first hour you were given this task, why didn't you just state "Oh, the database doesn't have ad-hoc query capability - what should I do?" Why didn't you do that? Trying to grasp the situation here. – Fattie Jun 28 '17 at 23:17
6

This is typical of a sick company.

Update your resume, get out. They don't want a working solution, they don't want to listen to reason, they've got a dog and they know it. They want someone to blame, and you are it.

Basically, you need to keep things running as best as you can while you job hunt. You are the proverbial sacrificial lamb.

  • Just an update, the company replaced some of the original architecture team but seem to have "forgiven" me for not making this work. Nine months later my kludge is still the only working option, but they hired a team of four data engineers to work on a solution and I expect they will figure it out eventually, but I am taking your advice and heading outta here. – kmccarty Aug 2 '17 at 14:03
9

Definitely bail. Job hunting is slow and having a steady income relieves much of the stress. Not to mention you have more bargaining power when negotiating salaries, since you can legitimately say you do not need the job you're applying for.

Turning the question around on you.. Why would you stay? Do you want to work at a company that put a new hire in this situation? Do you trust them with your future? I think the answer in this case is obvious, unless you have further input?

Not the answer you're looking for? Browse other questions tagged or ask your own question.