"Do I need to make that distinction explicit?"
"What good would a code bootcamp do for me which I can't already do self-taught?"
"Just because that is your preferred experience, you want me to follow it? "
21–30 of 32 posts
"Do I need to make that distinction explicit?"
"What good would a code bootcamp do for me which I can't already do self-taught?"
"Just because that is your preferred experience, you want me to follow it? "
My company is fully remote. When I interview people, I don’t know how old they are, nor do I care. I look at their job history as it relates to their ability to perform the job for which they are applying. If you were applying for an associate or junior developer position, your lack of experience wouldn’t really matter. I would worry that your bouncing around reflects that you can’t be counted on to stick it out for…
I am also live in Viet Nam. i am working for a US company in Viet Nam. I am a founder of a vietnam startup. I read your information in hacker news. Could we make friend? I always want to learn knowledge from US experts.
When I applied for my first fulltime job the company in question was offering both a contract and fulltime option. I was asked, probably in addition to my history of freelancing, why I was gunning for the fulltime option. I responded by saying that I appreciated the steadiness of work (with freelance you are often looking for the next opportunity), and to help contribute to the success of a particular organisation in the long term. They seemed satisfied by this response. I think they were coming from the point of view that you could make more money by freelancing / contracting, so were just curious as to why I wanted to "downgrade" (not their words, this is just my speculation).
Based on that experience (admittedly I was 23 at the time), you may find prospective employers more open to entertaining your application than you might think due to them having a different perception of your history.
I think given Covid you could make a pretty good case for wanting to shift to a more stable career path. I also wouldn't belittle your own experience thus far as not being a "career". There are many advantages of chopping and changing between different business contexts that you now have, that someone who only ever worked in 2-3 companies would not have.
You say you have no network. I would suggest reflecting a bit more on this, as I'm certain you would at least have some amicable contacts / temporary colleagues that you've made along the way, even if you wouldn't necessarily think of them as your "network" right now. Do you have a LinkedIn profile? If not, consider making one and connecting with some of the people you've worked with in the past.
Popping up a GitHub profile with a simple project that demonstrates what you think your skills are (e.g. perhaps it's a business web application that has a well-written set of unit tests, or applies a particular design pattern in a clear and logical way) could be a good compliment to your CV that employers can use to verify your expertise. If you find yourself relating more to the student crowd, then this is the sort of tack that graduates would take to prove their ability.
* get your CCNA and become a junior network engineer.
* Join the military. You can join the US military without living in the US or being a US citizen and achieve citizenship in 3 years instead of 5. If you have a 4 year university degree you can start life as a management intern as a 25A. If not you can be a 25B or if you are more ambitious and not afraid of failure a 17C or 25D.
* Learn JavaScript. When I say learn it I mean actually learn it as in writing original applications, walking the DOM, avoiding frameworks. Most people paid to write JavaScript never actually learn it and they need tremendous help from frameworks, abstractions, tools and other things that slow them down and makes for slow/shitty products. Employers generally realize the incompetence associated with this technology but they have products they need to ship. If you actually learn the technology with confidence companies will hire you just for the potential of solving problems other developers refuse to accept.
Earlier quoted context omitted.
I am also live in Viet Nam. i am working for a US company in Viet Nam. I am a founder of a vietnam startup. I read your information in hacker news. Could we make friend? I always want to learn knowledge from US experts.
Oh cool. Send me an email at qbtqgbx46owaab4@jetable.org, and I will respond with my real address.
Earlier quoted context omitted.
As stated before, I find freelancing to be a lonely experience. Not a lot of developers to talk shop to, and rarely do clients follow-up with additional work or referrals. I finish work for clients as I get paid, and usually never hear from them again. I've interviewed at larger companies trying to expand my career into being a senior among more developers but they seem to think I don't fit the bill, yet never tell m…
That depends entirely on how you freelance. I join teams. My current project, for a major Dutch bank, started with me developing the prototype, and later interviewing a bunch of people (internal and external) to join the team that I'm still part of. At other projects, I was hired to add some external expertise to an existing team. But it's mostly long projects in teams. But before I ended up in these sort of big proj…
A contractor is typically on site, or sells his time (and presence), meaning he has one client at a time.
A freelancer to me works on projects, and will take on multiple clients at the same time.
My company is fully remote. When I interview people, I don’t know how old they are, nor do I care. I look at their job history as it relates to their ability to perform the job for which they are applying. If you were applying for an associate or junior developer position, your lack of experience wouldn’t really matter. I would worry that your bouncing around reflects that you can’t be counted on to stick it out for…
What I don't know is what is so different about the approach to getting hired as full-time employee compared to a freelancer that makes it so difficult for me to pass. In what ways should one behave differently at a full-time job interview compared to a contractor's interview.
Right now I'm on YouTube looking for winning tech interviews in order to see how I should speak and things to say. It's the closest you could be to a fly on the wall eavesdropping on an interview. Because when it comes to social cues, I learn better by observing than by intuition.
- Start a company and build product for enterprise. The amount you get paid as a company vs. as an individual is not even comparable.
- Learn to sell more, or hire someone who can, and then learn to sell. Someone who can ask for a price you would never ask without blushing, blinking, sweating. Most engineers I've seen have a problem with sales and you don't know what's valuable for clients. I was in meetings where the client ignored features we spent weeks on, and was amazed by a feature we implemented in a day. One colleague engineer who tagged along was just amazed: "From all the features, they loved that?". Sometimes the amount of engineering you spend on something and the value it has to someone are two independent variables.
- Get an attorney who'll draw your contracts and make sure your company doesn't get abused. Clauses to protect you. To make sure you get compensated for the opportunity cost of an exclusivity contract, and to make it constrained in space, time, and limited to some entities. Obviously never sign something before they read it. The contracts you're handed were probably written by people from a legal department, so it's good to run it through someone cut from the same cloth.
- Amicable relations. Always deliver. Build a reputation. Repeat customers are a thing. Recommendations are definitely a thing. This can be very profitable.
- Network. The energy it takes is considerable. To be able to positively pitch your services, build relations, follow up on enquiries, spread good vibes... Build relations, build trust... And sometimes, sometimes, you might have to do a solid to a relation in a large enterprise to get in, but when you get in, you get in. Again, this can be profitable.
- For hiring, surround yourself with people you can learn from, who can complement you. Your objective is to grow the company.
- After servicing many customers, you'll learn patterns. You can sell a product many times over.
I'm excited for you. All the best!
One issue that may be getting in the way of you getting full time work is that you come across as being defensive/testy in response to friendly comments here. Here's some examples below of comments that could have softer phrasing (like first acknowledging the commenters point, then refuting it, instead of jumping into refutation): "Do I need to make that distinction explicit?" "What good would a code bootcamp do for…
Earlier quoted context omitted.
As stated before, I find freelancing to be a lonely experience. Not a lot of developers to talk shop to, and rarely do clients follow-up with additional work or referrals. I finish work for clients as I get paid, and usually never hear from them again. I've interviewed at larger companies trying to expand my career into being a senior among more developers but they seem to think I don't fit the bill, yet never tell m…
That depends entirely on how you freelance. I join teams. My current project, for a major Dutch bank, started with me developing the prototype, and later interviewing a bunch of people (internal and external) to join the team that I'm still part of. At other projects, I was hired to add some external expertise to an existing team. But it's mostly long projects in teams. But before I ended up in these sort of big proj…