From Backpacker Dreams to Microsoft PRs: How I Landed My First $40/hr Upwork Contract and a "Rising Talent" Badge

Yusuf Temel — Mon, 29 Jun 2026 12:32:53 GMT

Every developer shares the same beautiful daydream at some point: packing a backpack, traveling the world, and writing code from a beach or a cozy café while earning a living through freelance work. Total economic, time, and location independence. It’s the kind of dream that gives you butterflies.

I was one of those dreamers. Driven by that exact vision, I woke up one morning, opened an Upwork account, verified my identity, and started building my profile. But once the setup was done, reality hit me: How on earth was I going to stand out among millions of talented freelancers?

The Iron Rule of Freelancing: "Proof of Work" Over Diplomas

I quickly realized an unspoken rule of this ecosystem: clients don’t care about your traditional diploma or which corporate enterprise you used to work for. They care about one thing: Proof of Work. In a sea of anonymity, your proven track record is everything.

Fortunately, I felt ready. I didn't just list buzzwords; I filled my portfolio with real, heavy-hitting projects:

My open-source contributions to Microsoft’s Semantic Kernel and Ant Design Blazor.
A fully implemented, solo-developed Municipal HR Management System.
An AI-powered virtual fashion try-on platform named Giydir.

I wanted my profile to scream "Senior .NET & AI Integration Engineer" before a client even read my bio.

The Language Barrier and the Long Road to the Finish Line

Winning the invitation wasn't the end of the battle; it was just the beginning. What followed was weeks of intense communication, technical discussions, and negotiation.

As a self-taught developer from Turkey, English is not my native language. I’m not going to lie—this part pushed me to my absolute limits. I had to kickstart my own intensive English sprints, practicing day and night to ensure I could communicate seamlessly during project discussions. It was an exhausting, stressful, but incredibly rewarding learning curve.

Closer to the Dream Than Ever

Today, I am right on the verge of delivering this first major project.

Looking back at that morning I first opened the Upwork app, I realize that the backpack dream isn't just a fantasy anymore. It’s a pipeline currently in production. To anyone out there sitting in front of a blank profile wondering if it's worth it: focus on your Proof of Work, embrace the painful learning curves, and just push your code. The rest will follow.

Overcoming Imposter Syndrome: My Journey into Open Source

Yusuf Temel — Sat, 27 Jun 2026 07:45:19 GMT

For a long time, as a self-taught developer, I struggled with a persistent sense of inadequacy compared to my peers with formal engineering degrees. I eventually realized that this wasn’t a reflection of my actual skills, but rather a mental battle I was fighting within. I wanted to prove to myself that capability is defined by action, not just a diploma. My journey to overcome this "imposter syndrome" led me to the world of open-source development.

The First Win: Ant Design Blazor

My first contribution to Ant Design Blazor was a turning point. I identified an issue where exception stack traces were unnecessarily printed to the console in the JsInvokeAsync method. When I saw my pull request merged, I couldn't believe it. The maintainer, ElderJames, was incredibly kind and expressed genuine appreciation for my fix. That simple interaction silenced my inner critic and proved that I could contribute to professional-grade codebases.Aiming Higher: Microsoft Semantic Kernel

Encouraged by this success, I decided to aim higher. I set my sights on Microsoft’s Semantic Kernel. Transitioning from a smaller project to such a massive repository was like diving into the deep end. Everything felt complex, and at times, I felt overwhelmed.

Initially, I tried to solve an exception handling issue with a basic, custom try-catch block. I quickly realized this was a "junior" approach for a high-level project. I deleted my code, dug deeper into the repository architecture, and discovered the KernelException class. Engaging with Mark Wallace from the Microsoft team was a highlight of this experience; his feedback was incredibly constructive and professional, which motivated me to push my standards even higher.

My contribution to Semantic Kernel is currently under review. Being part of the discussion with the maintainers has been an education in itself. It’s not just about getting a PR merged; it’s about aligning with the architecture and standards of a global-scale project.What I Learned

Transitioning to the Microsoft project was a major turning point for me. Thanks to the constructive feedback I received, I learned how to develop code within a high-level project environment.