1) about the temporary contract
While the technical challenges were highly stimulating, the primary limitation was the structural insecurity inherent in the three-year temporary contract framework. My commitment to the organization was profound: I devoted three full years to the role and, based on the expectation of transitioning to a direct employee, I declined two external job offers during that period. This decision demonstrated my loyalty and belief in the company’s future with my talent. However, the anticipated direct employment did not materialize at the end of the contract, resulting in a significant professional disappointment. The biggest drawback was, therefore, enduring a prolonged period of contractual uncertainty and the final result of not being converted to a direct employee, which reinforced the need for long-term internal security in my next position.
2) about the operational environment
The operational environment presented an excellent opportunity to demonstrate high self-initiative and discipline. Working as a dedicated developer within a non-developer-centric department required me to function as a technical leader and ambassador for data solutions.
Early on, I leveraged strong communication skills and proactive engagement to educate colleagues on the possibilities of automation, effectively bridging the knowledge gap and driving adoption from the ground up. This unique structure meant I quickly became the primary technical owner, demanding rapid and decisive responses to project needs and domain-specific challenges (e.g., Quality requirements). The primary structural limitation was the absence of a dedicated software development and data analysis track within the department, as well as the lack of direct peers and management with a dedicated data-driven vision. This decentralized environment required tremendous resilience and forced me to create my own learning path for specialized corporate tools, thereby cultivating exceptional resourcefulness and a deep sense of project ownership.
