Axelerant Reviews & Provider Details

The backend engineer working on this project is the most reliable one, and he is the only one who finishes up his part by the deadline. Review collected by and hosted on G2.com.

Since it's an aggressive project, we agreed to reserve 2 weeks buffer, so our contract explicitly said that the final UAT acceptance is on 5/12. Result? We finally launched it on 6/15, with 2 of our in-house engineers spending almost a month wrapping things off, and rewriting some code because it's not working as expected or up to the spec.

Here are some details that I want to highlight:

1. The expected final UAT acceptance date is 5/12, but the final hand-off day is 6/9, and the project still has parts that our in-house engineers need to spend time to fix, for example, UI details, edge cases handling, etc.

2. As a frontend-heavy project, our designer spent a lot of time on the details but one of their engineers doesn't pay too much attention to it. After our team took back the project, we need to fix some UI/UX bugs that were not being taken care of, for example, spacing, and fonts used.

3. There's one engineer who didn't show up in the scheduled meeting multiple times. He sometimes would later tell us he's sick, sometimes there's just no explanation. This was when he was delayed in his progress, so we were all eager to see what his progress was.

4. Code quality is not the best. This part I'll put as last because this is more subjective. Our engineer spends 1 month after taking over the project to make it match our standard. Maybe because it's a very aggressive project, they have to put up things that are not in the most standard way, which is an inevitable tradeoff. Review collected by and hosted on G2.com.