Legal liability of a developer employed by a company
<p>The title says it: I am a full-time employee working as an ordinary developer at a company settled in Sweden. I am working on a number of different projects within the company but spend 80+% of my time on one particular project.</p>

<p>This project is an agile project where we develop closely with the customer who is participating in it. Work is done more or less by acclamation, although we have a somewhat rough plan. However, I always enforce that all work done is tracked using Youtrack so that we can agree on estimates, do moderations and that the customer can verify work that we marked as fixed and all this works well. All the work is also based separate specifications that we or they draft in the first place, then agree on and derive features and tasks from it. So far so good.</p>

<p>Now however we're at a situation where the customer is a single person and therefore has to take the roles of the product owner as well as the project manager, as the customer only booked/pays for development time (they book a budget of hours and my company can "throw work" at this and since a couple of months it's only me). The problem is that the customer only knows <em>what they want</em> <strong>not</strong> <em>how to achieve it</em>. In other words, no customer has no appropriate technical background to be in the role of the product owner.</p>

<p>So the development process works in a way that the developers (mostly me) make suggestions on how to approach new features technically and the customer agrees so that we can move forward. The customer, due to their lack of technical knowledge, virtually cannot disagree mostly. Sometimes they have their own ideas that we discuss but the work that we start is always agreed on and all arguments and concerns have been voiced; all future implications (complexity, needed time etc.) were also voiced.</p>

<p>So recently we finished integrating a huge component into the project, according to the tasks. However, this component is highly complex and does not align with their former component as they had envisioned. The customer even called it a nightmare, as it costed already much more time than planned and during our daily scrum I hinted that, should we continue the integration, it will cost much more time and increase the complexity even further.</p>

<hr>

<p>Now to get to the <strong>point of my question</strong>: Do I as a developer in my current position have any additional legal liabilities should this project fail or should the customer claim for recourse? With additional I mean other liabilities that are <strong>not</strong> covered through the company I am working for. I should note that I made the CEO already aware of this project and that it might back-fire. We also agreed that there has been at least one other red flag regarding this project.</p>

<p>What should I do?</p>

<p>Focusing exclusively on the legal aspects here, is the customer's contract with your company, or with you?  If all your interactions with the customer have been as a representative of your employer, and the customer's contract is with the employer, the employer is the one legally responsible.  </p>

<p>The most likely negative effects on you personally are poor performance reviews and lesser chance at promotion/advancement/raises within your company, but even those might not necessarily happen as long as you keep good communication with your superiors and do your best to manage a challenging situation.  If you demonstrate good leadership and management skills on a difficult project, that might be a more convincing demonstration of your capacities even if the project eventually fails.  </p>

<blockquote>
  <p>What should I do?</p>
</blockquote>

<ul>
<li>Document your interactions with the customer well, as / just after those interactions happen. </li>
<li>Do your best on the project.</li>
<li>Keep open and honest lines of communication with your superiors about what's happening. </li>
<li>Be glad you're working on this as an employee of a larger company, and not as a freelancer. </li>
</ul>

software employment liability