Hello again,
After my account was permanently suspended, I spent about four weeks thinking very seriously about what to do next. I had two conflicting realities in front of me: on one hand, I had years of real Upwork experience as a full‑stack engineer; on the other hand, my original account and public track record on the platform were gone. I knew I still wanted to work remotely with international clients, but I had to find a different structure.
That’s when I started talking more seriously with a friend of mine from Texas. He’s a security engineer by background, with solid knowledge in backend development, cloud infrastructure, and general software engineering principles. We realized that our skill sets were complementary: I’m most effective when I’m deep in the code and delivering features, while he’s naturally strong in communication, organization, and risk management.
We decided to build a small, focused operation together. Before we touched a single project, we clarified our roles and responsibilities in writing. His role would be closer to project manager and product manager: handling client communication, managing expectations, organizing tasks, and representing our “team” on calls. My role would be full‑stack engineer: designing and implementing the actual solution, writing the code, fixing bugs, and making sure the final product met the agreed requirements.
We used my years of Upwork experience to target the right types of jobs. I knew what “good” clients and long-term opportunities looked like, and I knew how to read between the lines of job posts. I focused on finding bigger, more serious projects where full-stack and infrastructure skills actually matter. When a promising client reached out or responded, I helped shape the technical approach: proposing realistic solutions, frameworks, timelines, and roadmaps that matched their business needs.
On the client‑facing side, my friend led almost all of the communication. He explained the solution clearly, walked through the architecture, discussed trade-offs, and managed expectations around scope and deadlines. I often joined the calls, but most of the time I stayed quiet, listened carefully, and took notes. My goal on those calls was to deeply understand the scope, edge cases, and hidden complexity-not to dominate the conversation.
After each call, we debriefed together. We confirmed the roadmap, broke the work into milestones, and aligned on the budget and timeline that had been discussed with the client. Once that was clear, I shifted into execution mode. I treated the work the same way I always had on Upwork: clean code, readable structure, maintainable architecture, and regular progress updates.
I reported my progress to my friend in a structured way: what was done, what was in progress, what was blocked, and what decisions were needed. He translated those updates into client-friendly language, sent regular reports, and scheduled calls when necessary. The client always had one consistent point of contact, which made their experience smoother and more professional.
Over time, this workflow started to pay off. We attracted more serious clients, delivered solid results, and kept many of them for the long term. The structure was simple but powerful: one person focused on deep technical work, the other focused on communication, expectations, and relationships. It felt very similar to how a small development company operates: a product/project lead on one side, a full‑stack engineer on the other.
If you’re in a situation where your path has been interrupted-whether by a platform issue, a career change, or something else-know that there are still ways to move forward. Partnering with someone you trust, being clear about roles, and leaning into your strengths can be a realistic way to rebuild. This experience reminded me that even when accounts and badges disappear, the combination of strong engineering skills and solid communication can still create real opportunities.
Thanks for reading. I hope this story gives you ideas for how you and your own team can structure your work, especially if you’re rebuilding after a setback.
Top comments (0)