Run unless you really need a job or experience - Client Accounts Receivable TreviPay Employee Review

*Amazing People *Great Culture *Solid Benefits * Gym and Cafeteria on site *Top Leaders *Hybrid Working Arrangements *Tons of Internal Movement and Opportunities *This is just the tip of iceberg - Apply Today to Learn More!

*The only Con is that you're not working here with me!

The company works on interesting fintech problems and engineers get exposure to a large distributed system with many microservices. Some engineers on the team were approachable and helpful when available. There are technically interesting challenges related to scaling and maintaining a platform that has evolved over time.

HR onboarding to learn overall company business model is good; however, technical onboarding for new engineers after arriving to assigned department was significantly more difficult than expected. Documentation for development environment setup and internal services was frequently outdated or incomplete. New engineers often had to rely on trial-and-error and tribal knowledge just to get a working local environment and understand service interactions. The platform architecture appears to have evolved organically over time without consistent service boundaries. Several services share models and dependencies across applications, which makes it difficult for new engineers to understand ownership and safely introduce changes. This increases ramp-up time and makes debugging or implementing features slower than necessary. Engineering leadership acknowledged that the system had accumulated technical debt, but there did not appear to be a clear strategy or dedicated engineering time allocated to address those architectural issues. Engineers were expected to deliver features quickly while working within a tightly coupled system, creating conflicting priorities for engineers trying to balance delivery with system stability. Engineering priorities often shifted between discussions about improving architecture and the immediate pressure to deliver features, but there did not appear to be a clear framework from leadership for how those tradeoffs should be managed. As a result, engineers were often left navigating those competing priorities on their own. Task estimation practices appeared to discourage honest engineering estimates. In my experience, engineers often felt pressure to commit to aggressive timelines even when the technical complexity suggested more time was needed. This can lead to unrealistic planning expectations and make it difficult for engineers to provide accurate delivery forecasts. Expectations for engineers during onboarding were not clearly defined. Feedback during the first few months appeared informal and inconsistent, making it difficult for new hires to understand whether their approach and priorities aligned with engineering leadership expectations until very late in the process. More concerning was the lack of accountability in how performance concerns were handled. Decisions about employment appeared to occur without a structured improvement process or clear written feedback, which can make the experience feel abrupt and difficult to learn from as an engineer. For an organization that emphasizes collaboration and respect in engineering culture, those values should also be reflected in transparent performance management and providing engineers a fair opportunity to understand and address concerns before major decisions are made.