ALPACAS

Q: Please introduce yourself briefly.

Geunwoo: Hello, I’m Geunwoo Noh. I’m a backend software engineer at AlpacaX, now in my third year. I mainly work on developing our Golang-based agent and designing and implementing backend APIs. My primary focus is on access gateway and system monitoring features. Since the AlpacaX server continuously collects real-time resource data, my work often involves large-scale data processing, incident response, and API performance optimization.

Junho: Hi, I’m Junho Ahn, a backend software engineer in my second year at AlpacaX. With a background in information security, I joined the team to apply that expertise. I currently handle authentication across our services. Since AlpacaX is built on a microservices architecture (MSA), this includes not just user authentication but also inter-service authentication. My role is about minimizing vulnerabilities while enhancing the user experience.

Jisung: Hello, I’m Jisung Chae, a backend intern at AlpacaX. I’ve been here for nine months, primarily working on features related to usage. Recently, I’ve been involved in the development of payment systems. A significant portion of my work consists of resolving inconsistency issues within an MSA environment and ensuring eventual consistency across the system.

In addition to our longtime Alpacas, we also spoke with Hyunwoo and Sangyeong, recent interns who have joined the team and are now working on a range of tasks, from infrastructure setup to implementing security features.

Q: How does the backend team decide on development directions?

Junho: At AlpacaX, developers are also the first users. We follow the “Eat Your Own Dog Food” philosophy. By using our own product, we naturally discover insights like, “This part feels clunky” or “it would be better if we added this feature.” For example, if we find the authentication flow too complex, we make the MFA setup straightforward based on our experience. The fact that we are both builders and users is what makes our backend team unique.

Geunwoo: As Junho said, we gain insights from using the product ourselves and also through user testing sessions that the entire AlpacaX team participates in. We observe real user flows, listen to pain points, and then discuss improvements together across backend, frontend, and business development teams. Cross-team collaboration is a big part of how we shape our development.

Q: What parts of the team culture or systems do you appreciate the most?

Geunwoo: Our feedback and code review culture is very open. Regardless of role—whether intern, junior, or senior—everyone can share their opinions openly. This often sparks new insights and diverse perspectives. It’s not just about pointing out errors; we actively discuss better structures or approaches. This openness makes collaboration smooth and helps us all grow together as developers.

Q: As interns, what have you enjoyed the most so far?

Sangyeong: I appreciated the generous settling-in period. The whole team avoided putting pressure when I joined the first time, which helped me adapt quickly. Additionally, all onboarding materials, workflows, and details are well-documented, allowing me to learn at my own pace and independently.

Hyunwoo: Same for me. I enjoy jotting things down and visualizing workflows, so creating my own notes and flowcharts for the code, as well as discussing them with the team in a non-pressure environment, helped a lot. Plus, guidance from teammates like Geunwoo was invaluable.

Q: Have you ever faced mistakes or challenging situations?

Jisung: Definitely. But the team helped me turn those mistakes into learning opportunities. Once, a faulty implementation caused background tasks to fail. Instead of simply fixing it quickly, the team encouraged me to debug it myself. Through that, I learned so much more and became more confident in solving issues independently.

Q: What’s great about working at a startup like AlpacaX?

Junho: The speed and flexibility of a small team are huge advantages. We don’t deal with lengthy approval chains—ideas can be discussed and implemented promptly. Seeing my suggestions or code reflected in the product so quickly is both fun and rewarding. Additionally, I have the opportunity to experience the full cycle—from planning to deployment to monitoring—which accelerates my growth.

Sangyeong: I agree. Even as an intern, I was entrusted with opportunities you rarely get elsewhere. At AlpacaX, ability and initiative matter more than title or tenure. Of course, responsibilities come with ownership, but that’s precisely what makes the experience fulfilling.

Q: What’s the biggest challenge and reward of your work?

Junho: The biggest challenge and reward is starting everything from scratch. Joining a startup right after graduate school meant facing new problems every day, from methodologies to real-world troubleshooting. While it involves many trials and errors, it also teaches me to identify core issues and create innovative solutions. Seeing those solutions deployed and working is incredibly motivating.

Jisung: When I first joined, everything felt like a challenge—from collaboration to implementation. But as I solved problems one by one, I gained confidence: “Next time, I can solve it faster and more accurately.” That sense of growth is the greatest reward I’ve felt at AlpacaX.

Q: What motivated you to join AlpacaX, and how did you prepare?

Jisung: In university, most of the focus was on theory, so I felt practical experience was the real differentiator. I wanted to gain that, and a startup seemed the best place to learn a lot quickly. AlpacaX, which develops its own security solutions, was especially appealing, so I decided to join.

Hyunwoo: I felt the same. I wanted real-world experience and the excitement of working in a startup. With my interest in networks and security, I pursued relevant certifications and personal projects, which prepared me well for joining AlpacaX.

Q: What kind of person would thrive at AlpacaX’s backend team?

Geunwoo: Many of our features are led directly by developers. Therefore, individuals with strong ownership and initiative fit well here. Since roles aren’t always clearly defined from the start, autonomy and immersion are essential for defining problems and creating solutions. Actively participating in code reviews and feedback is equally important.

Jisung: I agree with Geunwoo. Each developer often takes responsibility for leading features, which means you need to be proactive and accountable. While it can be challenging, it’s also where you grow the most. Anyone who embraces ownership and engages actively with the team will thrive here at AlpacaX.

We write code and build systems.

At the same time, we ask questions and search for better ways.

We’re not only building great products—we’re also shaping a better culture and work environment.