<p>Hey,</p>
<p>Since a few weeks I've been passively looking for opportunities to work on cool golang projects remotely, and to be honest I might not be looking in the right places because I don't really find much exciting offers.</p>
<p>From what I saw, go jobs are becoming more and more frequent but it's still really hard to find them on most platforms, and full-time remote work is still not accepted in many places.</p>
<p>Am I just setting the bar too high? Should I look for jobs in other languages as well, despite the fact that I really fell in love with Go? I unfortunately won't have a choice to be working remotely.</p>
<hr/>**评论：**<br/><br/>Sythe2o0: <pre><p>I was able to get a (full time, remote) job in Go in 5 weeks of applying for almost exclusively remote Go jobs (after 4 weeks, I started applying for remote jobs in other languages). I may be an outlier, I don't know your experience / education. I used the #gophers slack and whoishiring.io to filter for jobs, if that helps you.</p></pre>tdewolff: <pre><p>Exact same thing for me, I used Slack and got a full-time remote job in four weeks. Going to local Go meet-ups might prove valuable too, and the recent Who's Hiring posts here on Reddit can be useful too.</p></pre>elagergren: <pre><p>Third data point, but I was found from my GitHub repos (among other things, IIRC).</p></pre>jackmott2: <pre><p>Restricting a search to 1 language + remote + exciting is going to be hard yes, no matter what the 1 language is.</p>
<p>I would advise against the 1 language search. You may find go really exciting now but one day you will realize language isn't really that big of a deal! Better to work on an exciting <em>thing</em> or for good money/environment than a particular language.</p></pre>LogicX: <pre><p>Have you checked the golang slack jobs channel?</p></pre>Ullaakut: <pre><p>Didn't know it existed, going to check that asap! Thanks! :)</p></pre>mdaffin: <pre><blockquote>
<p>Am I just setting the bar too high?</p>
</blockquote>
<p>If you cannot find anything then yes you are.</p>
<p>Remember, go is still a new language - rapidly growing in popularity but still new. There are quite a lot of developers wanting to code in it and not many positions for it. Most companies that are coding in go will likely also have things written in other languages as well. It is only the newest of startups that will be almost pure go.</p>
<p>That said a lot of companies are moving towards it so you might have better luck finding a job for a company that uses other languages but that might be open to moving to go - or at the very least allowing you do to start some new projects in go. Looking for companies that are already use multiple languages might help.</p>
<p>You can always get a job working with another language for now while continuing to look for that dream job you want but dream jobs that meet all of your goals will be hard.</p></pre>Ullaakut: <pre><p>That totally makes sense. The only thing is that I think I'd rather wait for something that really fits rather than to work on something I don't truly enjoy. Knowing myself I don't think I would do a good job if I'm not into it unfortunately.</p>
<p>Very good advice though, thank you :)</p></pre>mdaffin: <pre><blockquote>
<p>rather than to work on something I don't truly enjoy.</p>
</blockquote>
<p>Welcome to life as an employee. It is rare to get your ideal job what you really want is to aim for a job that puts you in a better position then you currently are. If you can afford to wait for this then great, but it can take some time with a high bar set.</p></pre>rubiksCode: <pre><p>couldnt agree more</p></pre>emilevauge: <pre><p>We are based in EU, we love GO, we build Traefik ;)
<a href="https://containo.us/jobs/developer">https://containo.us/jobs/developer</a></p></pre>thegsg: <pre><p>That was fun! Props to who came up with the challenge </p></pre>nathforge: <pre><p><code>/home/emile/dev/go/src/github.com/containous/jobs/cmd/mysticeti/mysticeti.go</code></p>
<p>Think it might be the parent poster :)</p></pre>ngauthier: <pre><p>I don't think it's unreasonable, and I think it will be a growing list. Have you seen this list? Many of these places use Go:</p>
<p><a href="https://github.com/remoteintech/remote-jobs">https://github.com/remoteintech/remote-jobs</a></p></pre>ngauthier: <pre><p>Also I recommend subscribing to Golang Weekly and checking out their Jobs section each week. You can also just browse the archives:</p>
<p><a href="https://golangweekly.com/">https://golangweekly.com/</a></p></pre>cjbprime: <pre><p>Depends where you live. Sure, in SF.</p></pre>Ullaakut: <pre><p>I'm in Europe. It's true that it would most likely be easier in the US.</p></pre>EatPrayWhat: <pre><p>Berlin has a bunch of Go companies. Who is hiring on HN and golangjobs are your friends.</p></pre>earthboundkid: <pre><p>Depends on where in the US. If your city doesn't have a big tech scene, you may be trapped doing .Net or having to work remotely.</p></pre>tallnerd: <pre><p>A lot of companies give reasonable freedom to work with multiple languages. Some allow you to transfer to a team which is using this or that language. In my experience, language is less important than the company culture. If you're writing Go in a toxic environment, you're probably not going to be enjoying yourself.</p></pre>bostich: <pre><p>I searched for a pure Go job in Europe and found one.</p>
<p>We are hiring by the way: <a href="https://smallpdf.com/careers" rel="nofollow">Smallpdf Careers</a></p></pre>jerf: <pre><p>Part of it may depend on what you mean by "exclusive". I've been doing more and more of my work in Go (I'm in a position to be a very large decider in what new projects get done in), but I still can't <em>exclusively</em> work in Go. Partially because of existing projects that I can't justify a language change for, partially because there are things for which Go isn't the best choice.</p>
<p>Also, I'd say, Go's nice and all, or of course I wouldn't be here and trying to pick up the questions that get posted here on <a href="/r/golang" rel="nofollow">/r/golang</a>, but it's not the <em>only</em> nice language to work in. In 2018, I'd be reluctant to take on a large dynamically-typed code base, and I personally loathe Java and can't stand working in it, and C should pretty much be put out of its misery and C++ needs to stop accreting every feature the standards committee can think of, but you know, C#'s pretty nice too, for instance. There's some other nice languages, even if I did just literally proclaim my hatred of #1, #2, and #3. And even some things written in dynamically-typed scripting languages can be tolerable if they are well-done.</p></pre>pinpinbo: <pre><p>Come to SV, there are a bunch here</p></pre>pwaring: <pre><p>I think adding 'remote' will make it much harder. Even as a freelancer (PHP but I don't think the language makes any difference) I find a lot of people are uncomfortable with the idea of hiring a remote worker and want you on-site at least some of the time.</p></pre>3rdkulturekyd: <pre><p>Hey - here at WorksHub we're thinking about setting up a 'GolangWorks' platform in the coming months as we've found the Go community super vibrant and buoyant! It would be great to know whether this is something that would be pretty well-received...?
You can get an idea of how it could look here - <a href="https://www.works-hub.com/?utm_source=reddit&utm_campaign=Walkies&utm_content=Gen%20FP" rel="nofollow">WorksHub</a></p></pre>Greymarch: <pre><p>Depends on how much money you have saved, and how long you can last with the money you have saved. If finances are tight, then you shouldnt be looking exclusively for GoLang jobs.</p></pre>Thaxll: <pre><p>A bit off topic but a language is a just a tool, the end goal is to deliver something you should focus on that end goal not what to use to achieve it. Good dev don't really care about tech x,y,z.</p></pre>Ullaakut: <pre><p>Well, I simply believe that Go is a tool that I enjoy working with, there's no shame in having a favorite tool is there? :) When I said I was looking exclusively for Go jobs, I don't mean that I won't touch any other language.</p>
<p>I just really like how Go allows me to focus on what matters and not on maintaining a build toolchain, struggling with deployments because of compilers, etc.</p></pre>Fwippy: <pre><p>If you work at a larger company, you shouldn't have to worry about build toolchain or compilers, no matter what language you use. Somebody else will have already solved that for you.</p></pre>eikenberry: <pre><blockquote>
<p>Good dev don't really care about tech x,y,z.</p>
</blockquote>
<p>I don't believe this is true. Software development is an art and our 'tech' is our medium. Artists often show an affinity for certain mediums over others. Not ever good dev is a Michelangelo, some are Van Goghs or Donatellos. </p></pre>vestonice: <pre><blockquote>
<p>Good dev don't really care about tech x,y,z.</p>
</blockquote>
<p>That couldn't be more wrong. Good developers are going to want to choose the best tool for the job, which will vary depending on what it is you are trying to accomplish. Some programming languages (e.g. PHP) are bad choices all the time.</p></pre>Thaxll: <pre><p>I think you misinterpret what I was saying or I didn't communicated it properly, yes they're going to use the best tool for the job opposed to I want to code in x,y,z because it's fancy. I was referring to people that want to only use that language or that tool which is the wrong way to approach a problem. Saying that PHP is the wrong choice all the time is wrong for instance.</p></pre>vestonice: <pre><blockquote>
<p>I think you misinterpret what I was saying or I didn't communicated it properly, yes they're going to use the best tool for the job opposed to I want to code in x,y,z because it's fancy.</p>
</blockquote>
<p>What do you think drives someone's desire to work on something in a new language? It increases their experience and gives them new perspective to think about problems, which is again the hallmark of a good developer.</p>
<blockquote>
<p>I was referring to people that want to only use that language or that tool which is the wrong way to approach a problem.</p>
</blockquote>
<p>I agree with you that stubbornly refusing to use any but a particular tool is not good.</p>
<blockquote>
<p>Saying that PHP is the wrong choice all the time is wrong for instance.</p>
</blockquote>
<p>Have you ever written any PHP? It's a broken language with few good features and a ton of landmines. Nobody with an ounce of sense would select PHP for new development work.</p>
<p>Just as you can use PHP to write software, you can use a car with shitty brakes to go places. Because you can make it work does not mean you should. And because you can make it work does not make it less stupid.</p></pre>Fwippy: <pre><p>Only a Sith deals in absolutes.</p></pre>vestonice: <pre><p>I'm not sure if you're being sarcastic or not, but if not:</p>
<p>You haven't really made a case for why PHP is any good and should be considered for serious endeavors over other, more capable languages in the same sphere. It is widely understood to be a poorly designed mess of a language. That mirrors my own experience with it. But don't take my word for it - see the well-known blog post "PHP: a fractal of bad design": <a href="https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/" rel="nofollow">https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/</a></p>
<p>If I also told you that brainfuck or whitespace was an awful language that should not be used for serious projects under any circumstances, would you also reply that only a Sith deals in absolutes?</p></pre>Fwippy: <pre><p>Oh, I'm someone else, not the person you were talking with. I was just making a funny.</p>
<p>I agree that PHP has a lot of bad design decisions. I haven't worked much with it, and for that I'm glad. But PHP is good for some things, e.g. beginners who just want "HTML + a bit of logic." </p>
<p>I probably won't recommend that somebody use PHP. But I, like the parent, take issue with the assertion that PHP is <em>always</em> a bad choice.</p></pre>vestonice: <pre><p>The issue I take with suggesting PHP for beginners is that it will show them exactly how to do it wrong.</p>
<p>If you have no other experience and you see in PHP that, for example, "1" (a string) and 1 (an integer) are interchangeable, you might think that is a sane thing.</p>
<p>It's not. You end up with brittle code that breaks in subtle and surprising ways.</p>
<p>Can you mitigate these problems? Yes you can, if you are informed enough to do so.</p>
<p>But you could also just make it easy on yourself and use a language that isn't littered with landmines.</p></pre>Fwippy: <pre><p>Sure, it may not be the best choice. But you can't say it's always a terrible choice.</p>
<p>Whenever you find yourself making "always" or "never" statements that contradict what other people believe, it's usually because you have less understanding than others, not more.</p></pre>vestonice: <pre><p>Can you even come up with a realistic scenario where choosing PHP for any sort of new project makes sense? Because I can't. Your "HTML plus a bit of code" example did not do it for me, because you can do that with a ton of other languages that are better designed.</p>
<blockquote>
<p>Whenever you find yourself making "always" or "never" statements that contradict what other people believe, it's usually because you have less understanding than others, not more.</p>
</blockquote>
<p>This makes me think you have never used PHP or you do not understand the ramifications of a broken type system. Did you read the article that I linked previously? It does a fine job explaining why it's a poor choice.</p>
<p>In fact, I was just putzing around with a PHP online code sandbox just to see how much stupidity there still was. I was confused by literally the first thing I tried to do (echo a falsy value) which is illustrated in the example below:</p>
<pre><code><?php
echo(true); // This produces 1
echo(false); // This doesn't produce anything, that's not confusing at all! /s
</code></pre>
<p>Any developer worth their salt would be very concerned about such basic functionality acting in such a confusing way.</p></pre>twisted1919: <pre><p>I will never understand why so much hate against PHP...
When was last time when you have used PHP seriously so that you can say it's always the wrong tool? It doesn't even make sense.
Are you one of those who used PHP 10 years ago and think it hasn't changed since then? </p></pre>vestonice: <pre><blockquote>
<p>I will never understand why so much hate against PHP... </p>
</blockquote>
<p>Have you ever read <a href="https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/" rel="nofollow">https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/</a> or <a href="https://blog.codinghorror.com/the-php-singularity/" rel="nofollow">https://blog.codinghorror.com/the-php-singularity/</a>?</p>
<blockquote>
<p>When was last time when you have used PHP seriously so that you can say it's always the wrong tool?</p>
</blockquote>
<p>When was the last time you used any language that had an equality operator that you are actively supposed to avoid using because it provides broken comparison? PHP 7 documentation still has a big warning box on <a href="http://php.net/manual/en/function.strpos.php" rel="nofollow">the strpos documentation page</a> telling you that you need to be extra careful to use <code>===</code>.</p>
<blockquote>
<p>It doesn't even make sense.</p>
</blockquote>
<p>What exactly does not make sense about calling something like it is? You'd probably think it stupid for someone to drive a nail with a rock when they have a perfectly good hammer, right?</p>
<blockquote>
<p>Are you one of those who used PHP 10 years ago and think it hasn't changed since then? </p>
</blockquote>
<p>I am one of those people (aka "competent developers") who knows that the single most glaring flaw in PHP is its loose typing. And guess what? PHP 7 is still loosely typed:</p>
<pre><code>0 == "" // this is true
</code></pre>
<p>How about the fact that the standard library is garbage? We still have functions like <a href="http://php.net/manual/en/function.ldap-connect.php" rel="nofollow">ldap_connect</a> which, despite its name, also clearly has a note on its documentation that it <em>doesn't actually connect to anything</em>.</p>
<p>So please enlighten me - what has changed exactly? Because as far as I have seen, it is still littered with problems.</p>
<p>Also, I have to say I'm surprised to be hearing this sort of disagreement in the Go subreddit since it is actually a well designed language.</p></pre>
