3y
Thank you for your feedback. We are usually happy to hear where we can improve, but in this instance there are simply too many inaccuracies to be left unanswered.
You mention that 'remote work is very limited', but then contradict yourself by saying that the contract that you signed stipulated that you indicate a remote work address. You also omit to mention that your contract stipulated specific work hours, which you chose to ignore on several occasions.
Which means you were fully aware that, although the role was 100% remote, it was a full-time, fixed-hours position. As clearly explained to you when you accepted our work offer, we require a fixed work address to reinforce the full-time fixed-hours nature of the role.
According to you, your job was ‘not goal oriented’ and too focussed on hours worked, rather than quality of work produced. Since CobbleWeb uses Agile project management methodologies, in which each project is broken down into epics (a collection of tasks that outline a particular user journey, such as the buying funnel or product search), which upon completion AND a demo have to be signed off by the client, your statement is patently untrue.
You make the accusation that you received very little feedback. Our records tell a completely different story. There were daily retrospectives with the CTO, Paul Payen. After the rest of the development team complained about a lack of concrete communication from your side, the CEO had to step in to prevent damage to our client relationships. At that stage you were addressed about your lack of productivity and sub-par work quality.
You make another unsubstantiated statement that the company has a high employee turnover. In fact, our average employee tenure is 18 months, which compares very favourably with large well-established tech firms, where it can be as little as one year. Obviously we are not resting on our laurels; and are constantly working on new ways to improve aspects such as employee support, engagement, and company fit.
You say ‘learning is not encouraged’ which is quite bizarre, since it is literally baked into our business model. However, any research has to be done in a structured way that contributes to our clients’ project outcomes. That is why any research requirements are always first discussed, signed off by the tech lead, and then outlined in Jira, our project management software.
While you are more than welcome to study anything that you fancy in your own time, it is unacceptable to neglect your allocated tasks. It is also quite presumptuous of you to overrule your tech lead, who decides when and which new software should be investigated.
In conclusion, we had to let you go to protect our business, our clients’ projects and our team cohesion. In particular, for not adhering to the terms of your work contract and not working with the rest of the team in a productive and constructive manner. We hope that you learn from this and become a more mature team player in future.
