Good pay and growth opportunities.
I was brought onto a project at Intuit to support the implementation of a third-party platform that I had prior experience with. My role was positioned as the internal specialist, responsible for designing the necessary integrations to support the project’s objectives.
However, during my time on the team, it became evident that there was a significant knowledge gap regarding the platform among existing team members. I later learned that the team had previously undergone training for the platform but chose to discontinue it, citing the complexity and time commitment as prohibitive. I was hired to bridge this gap and move the project forward.
Unfortunately, the lack of foundational understanding created challenges early on. I was tasked with designing integrations that were not technically feasible given the platform's capabilities. When I raised these concerns and offered alternative solutions based on my experience, my input was not well received. Ultimately, I was let go after one month, with the reason cited being insufficient back-end experience.
While I appreciated the opportunity to contribute, the experience highlighted the importance of alignment between project goals, team capabilities, and realistic expectations. I hope future hires are given more clarity, support, and a collaborative environment that values transparent technical dialogue.
Ensure that teams are adequately trained and possess a foundational understanding of the technologies they are expected to work with, especially before bringing on external specialists.
Creating realistic expectations around technical feasibility and fostering an environment that values open dialogue and expertise can lead to better project outcomes and employee retention.
Additionally, clearer communication around role expectations and more collaborative decision-making would help reduce misunderstandings and promote long-term success.
The interviews were in three stages: * Stage 1: An initial phone contact made by the talent acquisition person. * Stage 2: A phone discussion with the hiring manager to talk about the position, evaluate past experience, and discuss requirements
1. Technical phone screen - 60 minutes with the hiring manager and one team member. 2. On-site full day, including: * Coding challenge task in Python * Presentation of the coding challenge * System design * Troubleshooting * Beha
1. Phone call by Recruiter 2. Technical Phone Screen 3. 4 Rounds of Technical interview onsite Met 4 members of the team. Each asked a few technical and coding questions. Whiteboarding occurred in 2 out of 4 rounds.
The interviews were in three stages: * Stage 1: An initial phone contact made by the talent acquisition person. * Stage 2: A phone discussion with the hiring manager to talk about the position, evaluate past experience, and discuss requirements
1. Technical phone screen - 60 minutes with the hiring manager and one team member. 2. On-site full day, including: * Coding challenge task in Python * Presentation of the coding challenge * System design * Troubleshooting * Beha
1. Phone call by Recruiter 2. Technical Phone Screen 3. 4 Rounds of Technical interview onsite Met 4 members of the team. Each asked a few technical and coding questions. Whiteboarding occurred in 2 out of 4 rounds.