> How should I structure my resume? I have no past projects other than the work I've put for my past 2 employers?
This part is pretty easy. Include the companies you work for, and the dates. Describe the project and the (relevant) skills you used. For title, put Software Developer, Contract. You can put junior on the one where you had an official title, and leave out a level on the one where you didn't have a specific level noted.
Given your resume is short, include an education section listing your Bachelors degree, and courses included: and list some you think are relevant.
Getting hired is hard, especially if you're working remotely. Try to use and build your network. That person who hired you twice, might be able to hire you again, or know someone who can use your skills; send them an email. If you've got contact info from anyone you were working with, send them something like
Hi X, I enjoyed working with you at Y, so sad it failed, what are you working on now, do you have any openings, or know anyone who is looking for a developer like me?
I know someone who's been doing this for 10+ years. Everytime he joined a startup he thought it'd be long term, then it all ends. He told me if he knew his life would be volatile like this he would've saved his money instead of splurge it all. I hope you find a more stable remote startup job, but don't be surprised if this unpredictability continues for years. Save your money.
I don't think any of us can answer these questions for you. It sounds like you've done enough real development to consider yourself integrated into the field, so there's hope I think. If I were in your shoes the main thing I'd be considering is how you want to spend the rest of your career. Do you genuinely enjoy software development? If so then get your thinking cap on and figure out how to make it work. If you don't like it that much then this might be a good time to jump ship.
Remote roles are also difficult to land for junior developers because there is an assumption that those working remotely are going to be independent (it's harder to support someone when you can't sit at the keyboard with them). So that might be one of the reasons you aren't finding remote roles, and one could argue that at this stage of your career you maybe shouldn't be looking for one.
Also bear in mind that in the U.S. market we're in a situation now where even incredibly skilled developers are having trouble finding work. I worked with a guy about a decade ago who mentored me and taught me a lot, he was one of those savant programmers who'd been doing it his whole life. He got laid off last year and has been out of work since. So it's also the market, not just you.
All of this being said I think there is a place in the IT industry for people like you to find work in companies who have a harder time getting bodies into seats, unattractive companies with boring tech stacks and cultures. That might not sound appealing to you, but it's been my experience that companies like this tend to come with less stress and a slower pace. Basically you need to look at it from the cost/benefit perspective of the employer. If they have a hard time hiring and paying an excessive salary, they're more likely to hire inexperienced people. Whereas if you're gunning for high paid remote roles you're just too far down experience line.
Once you build up your experience and skill-level, that's when you can aim for remote roles.
There is a lot of YC activity in the Middle East, I think some startup in some other Arab country could hire you remotely.
There are also startups in Southeast Asia that might be options.
> I was the only developer on the frontend team for this new startup, I was responsible of taking a full Figma design from scratch and implement it with React, I have to be honest I had to use a component library to get the job done, because the deadline was very close and everything was fast paced, there was no room for code refactoring, code quality, TBF I didn't even write tests!
I can't tell if this is a joke or not lol--almost nobody writes frontend tests at early-stage startups. And aren't you supposed to be using component libraries nowadays?
> How should I structure my resume? I have no past projects other than the work I've put for my past 2 employers?
This part is pretty easy. Include the companies you work for, and the dates. Describe the project and the (relevant) skills you used. For title, put Software Developer, Contract. You can put junior on the one where you had an official title, and leave out a level on the one where you didn't have a specific level noted.
Given your resume is short, include an education section listing your Bachelors degree, and courses included: and list some you think are relevant.
Getting hired is hard, especially if you're working remotely. Try to use and build your network. That person who hired you twice, might be able to hire you again, or know someone who can use your skills; send them an email. If you've got contact info from anyone you were working with, send them something like
Hi X, I enjoyed working with you at Y, so sad it failed, what are you working on now, do you have any openings, or know anyone who is looking for a developer like me?
I know someone who's been doing this for 10+ years. Everytime he joined a startup he thought it'd be long term, then it all ends. He told me if he knew his life would be volatile like this he would've saved his money instead of splurge it all. I hope you find a more stable remote startup job, but don't be surprised if this unpredictability continues for years. Save your money.
Sorry I can't help, but have you took a look in the "who is hiring?" / "Who wants to be hired?" threads? https://news.ycombinator.com/submitted?id=whoishiring
Perhaps there is something useful and you can post your data in the correct thread.
I don't think any of us can answer these questions for you. It sounds like you've done enough real development to consider yourself integrated into the field, so there's hope I think. If I were in your shoes the main thing I'd be considering is how you want to spend the rest of your career. Do you genuinely enjoy software development? If so then get your thinking cap on and figure out how to make it work. If you don't like it that much then this might be a good time to jump ship.
Remote roles are also difficult to land for junior developers because there is an assumption that those working remotely are going to be independent (it's harder to support someone when you can't sit at the keyboard with them). So that might be one of the reasons you aren't finding remote roles, and one could argue that at this stage of your career you maybe shouldn't be looking for one.
Also bear in mind that in the U.S. market we're in a situation now where even incredibly skilled developers are having trouble finding work. I worked with a guy about a decade ago who mentored me and taught me a lot, he was one of those savant programmers who'd been doing it his whole life. He got laid off last year and has been out of work since. So it's also the market, not just you.
All of this being said I think there is a place in the IT industry for people like you to find work in companies who have a harder time getting bodies into seats, unattractive companies with boring tech stacks and cultures. That might not sound appealing to you, but it's been my experience that companies like this tend to come with less stress and a slower pace. Basically you need to look at it from the cost/benefit perspective of the employer. If they have a hard time hiring and paying an excessive salary, they're more likely to hire inexperienced people. Whereas if you're gunning for high paid remote roles you're just too far down experience line.
Once you build up your experience and skill-level, that's when you can aim for remote roles.
There is a lot of YC activity in the Middle East, I think some startup in some other Arab country could hire you remotely.
There are also startups in Southeast Asia that might be options.
> I was the only developer on the frontend team for this new startup, I was responsible of taking a full Figma design from scratch and implement it with React, I have to be honest I had to use a component library to get the job done, because the deadline was very close and everything was fast paced, there was no room for code refactoring, code quality, TBF I didn't even write tests!
I can't tell if this is a joke or not lol--almost nobody writes frontend tests at early-stage startups. And aren't you supposed to be using component libraries nowadays?