111–120 of 279 posts
* Remote: Yes (onsite preferred)
* Willing to relocate: Yes!
* Technologies: Java, C# Python, JavaScript, Swift, Objective-C, C++
* Résumé/CV: http://www.ntpeters.com/Nathan_Peterson_Resume.pdf
* Email: ntpeters@mtu.edu
Willing to relocate: No
Technologies: python, C#, JS, aws ecosystem, C++, matlab, C, go, LabView, sql, distributed systems, redis (descending order of experience)
whoami: Please send me code test or a real issue you're having. I'll send my resume in exchange (if relevant).
Thanks!
theaddressis11235813213455@gmail.com
Remote: Yes
Willing to relocate: No
Technologies: Specializing in business and engineering of mobile and web products for 17 years. Ruby + Ruby on Rails (10 years), Go (golang), C, Swift, JavaScript, HTML. Please see CV linked below for full skill-set.
Résumé/CV: http://www.lukeheuer.com/
Email: luke@heuerlabs.com
Junior iOS dev + designer looking for any great opportunities, have experience with MapKit, CoreLocation, Sketch, usage of many different API's. Please take a look at my resume for a better list!
Hope to hear back from some of you.
Remote: Yes
Willing to relocate: Yes
Technologies: Python, Django, Django REST Framework, Flask, Tornado, ElasticSearch, MongoDB, Redis, Celery, RabbitMQ, Consul, Selenium, Scrappy, Grab, BeautifulSoup, Fabric, Vagrant, Docker, Nginx, Gunicorn, JavaScript/NodeJS, AngularJS 1.x
Résumé/CV: https://www.linkedin.com/in/dmitryfedotkin
Email: fedotkin.dmitry@gmail.com
Earlier quoted context omitted.
when I see programmers who know so many languages, I feel like I have no chance and I dont bother to apply, but thankfully I have a lot of ideas of my own.I hope you will accept a worthy offer, because not many employers can understand beside languages how long it takes to learn all the other technologies.
I've done paid work in C#, C, C++, Objective-C, Python, Java, Javascript, x86 Assembly, a variety of flavors of SQL, Silverlight, Actionscript, Go, Node... Probably other things off the top of my head. The thing is, I'm only really good at C# and C++. Most of the above languages use similar paradigms and just have some different syntax. The skill I actually want when I hire people is willingness to work on something…
Sure, many of them are the same C/C++ family, both a lot of them aren't, and I tried not to repeat the ones that were isomorphic to something else.
To that end, I learned Haskell well enough to be able to "think functionally" and applied that to what I already knew about JavaScript, Python, etc. But I didn't go out of my way to learn Scala, even though I want to.
I learned MySQL and MongoDB because I needed them to complete projects, but didn't make the leap to PostgreSQL or Couch because I could just pick them up later, if it ever even came up.
I think the point is, know how to do a lot of things, but don't get locked down into doing it only one way.
Location: (soon to be) Sacramento, CA
Remote: Yes.
Willing to relocate: No, but willing to travel to the SF Bay Area up to once a week, with occasional week-long trips.
Technologies: Python, C, C++, MATLAB, Git / toy projects using Flask, Django / rusty experience in Java, OpenGL (C++)
Github: https://github.com/aganders3
Résumé/CV: Provided by request via email.
Email: aganders3@gmail.comLocation: San Diego, CA Remote: Willing. Willing to relocate: Yes, to Seattle area. Technologies: C/C++ (Boost + STL), Java, Haskell, PHP, JavaScript (Node + several frameworks), MATLAB, Python, Lua, MySQL, MongoDB, UNIX/Linux Currently learning: Qt, Laravel PHP. Resume: https://www.linkedin.com/in/mattwalther https://github.com/mashiox/ Email: matt@mashio.net I am a recent graduate from San Diego State University wi…
when I see programmers who know so many languages, I feel like I have no chance and I dont bother to apply, but thankfully I have a lot of ideas of my own.I hope you will accept a worthy offer, because not many employers can understand beside languages how long it takes to learn all the other technologies.
I don't think I really know a language until I've spent a couple of years in it, and written something significant in it (rather than just doing maintenance and tweaks in an existing code base).
This works in your favor: You read that resume and perceive someone who looks like a coding star. As someone who reads a lot of s/w engineering resumes, I see someone who's potentially making strong claims that they can't back up. Or worse, someone who thinks they're better than they are. At that point you read the rest of the resume for evidence to back up the claims; if someone claims expertise in a horde of languages and they've only actually worked in a few, that's interesting data.
I used to put LISP and a bunch of different variants of Pascal and assembly languages on my resume, until I realized that nobody really cared.
Just claim what you know well. Don't worry about looking good.
[deleted]