진돌.dev
Dec 7, 2025 · 6 min read

I Left the Startup I Worked At for 3 Years and 6 Months

Jinseok Yeo

I left the company I had worked at for 3 years and 6 months. It was not a short period, and it was a place that had been with me from the start of my career until now.

This post is a retrospective documenting what I experienced and learned during that time. Rather than debating the rightness or wrongness of my choices, I want to summarize my growth and limitations as a developer, and the reasons why I chose a new beginning.

Reasons I Was Able to Stay for 3 Years and 6 Months

1. A Clear Growth Environment

When I joined, I was a junior developer just starting my career, not even fully understanding React. Fortunately, the company had an experienced CTO and lead backend and frontend developers, and through collaboration with them, I learned a great deal, from fundamental skills to a developer's mindset.

The startup environment also significantly influenced my growth. Individual growth directly impacted the team and the product, and the company encouraged this. As a result, in 2024, I was offered to lead a small team and experienced the team-building process by participating in interviews for new team members. I clearly felt that I was trusted as a member of the organization.

2. Product Development I Could Actively Participate In

As it was my first company, my affection for the product was significant. It wasn't just about implementing given requirements; my judgments and choices could influence the actual user experience and product direction.

Especially within the frontend team, I had relative freedom to propose new technologies or structural improvements. I proactively introduced libraries like React Query, React Hook Form, and Zod and disseminated them to the team. I also initially researched and built webview technology, which later formed the basis for other projects.

When I heard in a peer review, "Jinseok's code has been incredibly helpful," I realized that my work could impact the entire team. This experience became a crucial asset in growing into a developer who can make independent judgments and decisions in any environment.

3. The People I Worked With

Above all, the biggest reason was my colleagues.

I was able to work while forming deep bonds, both professionally and personally. We continued our relationships by spending time together outside of work, and I felt we were closer to friends than mere colleagues.

The fact that I will naturally drift apart from the people I saw every day is what I regret the most.

Reasons I Decided to Change Jobs

1. Changes in Company Direction and Role Structure

For me, 2024 was a period of maximum immersion. My influence on the product and team was significant, and development itself was enjoyable. However, in the latter half of the same year, the situation changed as the company's priorities shifted rapidly.

An app developed in the past began to grow rapidly overseas, and management decided to halt existing projects and focus all personnel on that product. While this was a perfectly understandable business decision, the internal preparation and consensus-building process within the organization were insufficient.

This change occurred particularly at a time when I was offered a team lead position and forming a team, which significantly shook roles and expectations. Some team members found themselves in a technology stack environment different from what was initially expected, creating a burden for both the organization and individuals.

From this point, I began to ponder what role I could play in this environment in the long term.

2. Discrepancy Due to Changes in Decision-Making Structure

Initially, team members were given a lot of autonomy and responsibility, and I had the experience of working proactively within that structure. However, after the direction changed, a greater proportion of key planning and decisions were made at higher levels, and the context was often not sufficiently shared.

As a result, there were increasing moments when it was difficult for me to understand 'why this feature is being developed' or 'what problem this task solves.' In an atmosphere where speed and execution were emphasized more than asking questions, I increasingly felt like I was becoming an executor rather than a decision-maker.

I came to realize that there was a clear gap between the way I excel and the role the organization expected of me.

Growth Over 3 Years and 6 Months

Growth Through Feedback

Early in my employment, I was a developer who 'did what was assigned.' The feedback I received in my H2 2022 review was clear.

"It would be great if you could work more proactively. Currently, it feels like you are mostly just doing what is assigned." "Please be more proactive in expressing your opinions when issues or coordination problems arise during the development process." "Look at UI/UX more critically and actively provide feedback."

I pondered how I could improve. When I considered why I couldn't offer opinions, it was because I didn't trust my own suggestions. I needed solid knowledge and experience.

From this period, I started working on side projects or studying after work. As a result, I began receiving positive reviews from H2 2023.

"It was good to see you contemplating the product's direction for better alternatives." "It was good to see you actively proposing ideas."

Unovercome Feedback

Completeness was a point of feedback I received throughout all three years.

"Even when content is in the design specification, issues are sometimes found during the testing process." "Designs are frequently omitted."

Perhaps due to my less meticulous nature, I often missed minor details. This was feedback I received in almost every review.

To improve, I tried breaking down development units into smaller pieces or introducing developer testing periods, but I still missed minor details. This happened even more frequently when coding with AI.

I began to think that if I couldn't solve it, perhaps I could compensate with other strengths. I want to grow into a developer who demonstrates strengths in rapid execution and problem-solving using AI.

Next Company

My next company is Olive Young's Global Team.

What I realized during my 3 years and 6 months at the company was that both the team and individuals can grow in an environment where I can actively voice my opinions.

In that regard, I'm a little concerned about the next company. During the HR interview, I was told that I wouldn't be able to express my opinions as freely in a large corporation as in a startup, so I thought I might fail the culture fit, but I passed.

Since I passed the culture fit, I should strive to contribute to the product as actively as I have been, as that's likely what they expect of me.

Based on my 3 years and 6 months of experience at Lookco, I will continue to grow as a product-building developer at Olive Young, striving to become a product maker rather than just a developer.

Jinseok Yeo

A frontend developer in commerce who improves both the product and how the team builds it.