![thank-you-traveloka](https://res.cloudinary.com/dzhed5o95/image/upload/v1746693918/thank-you-traveloka_p64amb.png) ## The Technical Path For nearly 2 years, I've been navigating the backend engineering field at Traveloka. My technical toolkit primarily revolved around Java, but the real growth came from diving deep into cloud infrastructure, particularly AWS. > [!tip]- Hey, stop right there. Do you want to know something about AWS? > While Amazon is widely known as the world's largest e-commerce company, a surprising financial reality exists behind the scenes: AWS (Amazon Web Services) contributes a disproportionate amount to Amazon's profits compared to its revenue share. [The Motley Fool](https://www.fool.com/investing/2024/01/10/amazon-e-commerce-company-74-profit-this-instead/) > AWS accounts for just 16% of Amazon's total revenue, yet it generates a whopping 74% of the company's operating income. [The Motley Fool](https://www.fool.com/investing/2024/01/10/amazon-e-commerce-company-74-profit-this-instead/) This profit powerhouse has fundamentally transformed Amazon's business model and financial health. > The contrast becomes even more stark when examining Amazon's profitability without AWS. In 2022, Amazon's core e-commerce business (both North American and International segments) actually operated at a loss, with North America losing $2 billion and International segments losing $7.74 billion. Without AWS's massive contribution of nearly $23 billion in operating profit, Amazon would have posted operating losses of $10.6 billion that year. [FourWeekMBA](https://fourweekmba.com/amazon-revenue-breakdown/)[FourWeekMBA](https://fourweekmba.com/is-amazon-profitable-without-aws/) The office—conveniently close to home—housed an environment that was, without doubt, exceptional. I found myself surrounded by remarkably talented individuals who constantly pushed the boundaries of what's possible. Yet despite this ideal setup, one factor kept nudging me toward the exit: time. ## Time Last year marked significant milestones—a promotion to the active board at [Palayu Mandiri](https://palayumandiri.com) and passionate solution-crafting with [Kugie](https://kugie.app). But 2024 has been genuinely exhausting. Every commitment—whether family or friends—required careful coordination with my calendar. While this forced me to master time management, I eventually realized something crucial: I needed more than seven days in a week. My calendars became oversaturated, leaving zero space for personal reflection or growth. ## Professional Fields vs. Amateur Passion Two years in professional software engineering revealed something fundamental about myself: I thrive as an amateur. There's something special about approaching challenges from an underdog position rather than as an established expert. Don't misunderstand—I genuinely love my work. But what truly energizes me is experiencing the process itself, feeling the rhythm of creation and problem-solving rather than just checking deliverables off a list. ## Final Days: Seeking Wisdom During my final weeks at Traveloka, I invested countless hours seeking knowledge from those more experienced than myself. These conversations proved invaluable, particularly two sessions that fundamentally shifted my perspective. A Senior Product Manager emphasized that product development ultimately answers to customers—they're the real boss. Whether it's Grab strategically placing ads or companies monetizing customer data, success requires understanding multiple viewpoints. He stressed that product management isn't just about the product itself; it demands foundational knowledge of your current position, regardless of your background in engineering, marketing, finance, or elsewhere. When discussing career milestones, he shared his aspiration for entrepreneurship while acknowledging realistic constraints. With a family to support and research suggesting only a 10% success rate for new businesses, he's building financial security before taking that leap—something I deeply respect. Our conversation about success revealed its subjective nature. He views success not through short-term wins or questionable tactics, but through enjoying each step while making thoughtful decisions. Ultimately, product ownership requires sustainable thinking—consistently understanding your next steps while considering all aspects. I also spent time with an Engineering Manager at Traveloka, shared equally valuable insights during our conversation. His clear message: "If there's nothing left to achieve, leave." His greatest challenge? Managing people—the variables are countless. He advised choosing reliable team members without becoming overly dependent on any individual. His definition of success centered on following your roadmap and gaining the experiences you desire while maintaining personal goals. His parting advice resonated strongly: define your version of success early. ## The Next Chapter These conversations confirmed what I'd been feeling—it's time for a new direction. My next journey will take me down the product path, where I can apply my technical background while exploring new challenges in creating user-centered solutions. Professional fields taught me discipline and technical excellence. Amateur passion showed me where my heart truly lies. Now, I'm ready to bridge these worlds in product development—crafting solutions that marry technical possibility with genuine user needs. >[!quote] Charlie Chaplin >"That's all any of us are: amateurs. We don't live long enough to be anything else." [Goodreads](https://www.goodreads.com/quotes/8600537-that-s-all-any-of-us-are-amateurs-we-don-t-live) --- <div style="border:1px solid #EEE; background:transparent; padding:20px; border-radius:5px; text-align:center;"> <h3>Never Miss an Update</h3> <p>Get my latest thoughts on digital knowledge management and personal growth delivered directly to your inbox.</p> <a href="https://setasena.substack.com" style="display:inline-block; background:#3D85C6; color:white; padding:10px 20px; text-decoration:none; border-radius:4px; font-weight:bold;">Subscribe</a> </div>