Bugcrowd | San Francisco | Full-Time | Onsite

Are you a Rails engineer but don't know what XSS, SQLi or mass assignment is? SHAME!

Just kidding! Come work for Bugcrowd, build some cool stuff and get your security on.

What we do: Our revolutionary approach to cybersecurity brings together the world’s largest crowd of independent security researchers to the most innovative companies. We bring thousands of good hackers to the fight, helping companies even the odds and find bugs before the bad guys do. Don't be a hack, come learn to hack!

We're a 50-ish person company based in San Francisco, down on the Embarcadero. We have an awesome team and a great office! We do cool stuff like host engineering team offsites, attend conferences (including Defcon), speak at meetups and just overall have a swell time.

We also do a lot of company-wide activities, most recently bowling in the mission. My goal is to get us all over to Australia but there are no promises (but I'm working on it)

Looking to fill the following positions:

* Senior software engineers (extensive Rails experience, security experience a major plus)

* Engineers with a strong DevOps background (containers, terraform, vault, AWS)

* Data scientists (machine learning: random forest, deep learning, Python)

* Designers (because we like to discover through design!!)

Email: damien@bugcrowd.com

My opinion is that any company building an API should run at least one bug bounty on it before releasing it to the public.

1. Yes 2. I'm here at SX and saw the interview. Chris Sogohian and Ben Wizner were very focused in their questioning and Edward seemed keen to ensure his main points were conveyed. There really wasn't an opportunity to cover current Russian political actions.

It was a very interesting interview. Combined with the Aaron Schwartz documentary and a cross to Assange it's been quite an intense couple of days!

What's the range on the Bluetooth? Prob not enough to get notifications at one of those annoying parties where you have to place your phone in a bowl at the door so you aren't distracted during "people time". I can see it would be useful to surreptitiously receive new Tinder match notifications while on a Tinder date though.

Mine will quite happily work from the other side of my house or if I'm outside gardening or something, so 15m or so. Far enough so that I can out my phone in its dock and do stuff pretty much anywhere on my block and still get notifications.

I like thinking about this concept, so I purchased On Computer Simulated Universes by Mark Solomon hoping to gain a little more insight. It's a great book and got me thinking along the lines of why we, or an ancestor universe, may want to simulate a universe. Is it for fun, learning, or o test a wide range of simulations with different parameters in order to try and avoid a disaster in the simulator's universe (such as destruction of their own habitat)?

I really like telling people that I think our universe was seeded with the idea of religion to see where we go with it. So all of the supernatural occurrences (stories, visitations, burning bushes etc.), whether you believe them or not, are simply part of our simulation program.

I started with Ember about a year ago and the getting started docs were pretty terrible. It took a lot of experimentation and frustration before I was comfortable developing with it. Eventually I became familiar with the framework and the API docs are quite in-depth, not really great for a beginner though. After about four Ember projects I can now prototype a large app (using something like Bootstrap) in a day or so, so I feel that pain at the start was worth it. Back at the time though I was tearing my hair out, especially over router changes. The changes improved things by an order of magnitude though. I trust the Ember team, I'm happy now, the start could have been easier.

My experience pretty much parallels yours. These frameworks are at the cutting edge. Only a handful of big apps have been made with Ember or Angular, and so the core teams are constantly bumping up against weaknesses in their designs which can only be addressed by making changes that break apps.

From reading the Ember discussion lists I get the strong sense that the core team is willing to make difficult breaks, but that they really try to only do it when it's absolutely necessary for the long-term robustness of the platform. A lot of thought seems to go into which problems are getting solved now, which are put off til later, and which interfaces get torn out and rewritten.

I just spent several weeks upgrading my app from the earlier Ember RCs to Ember 1.0 and the latest Ember-data, and while quite painful, I feel good about it because I don't think the core team made those changes lightly. My sense is they are looking out for us.

I'm currently working on a big Angular app that is about to move into production (although it's not to be something that's widely used in public) - we have found that Angular causes everything to be structured in a nicely organized fashion overall. This app is not structured perfectly by any means either, due to bad design on some of our pre-existing code base.

From what I understand, big Ember projects have turned out well for Ember devs - I can confidently say that I feel the same way about big Angular apps. I have built several big ones, including an online assessment platform (frontend by myself) and an online assessment platform/management system (with a team of ~10, 3 of us on frontend).

From my experience, the Angular team has thought things out on a high level, which I greatly appreciate. They are big consumers of their own product, as Angular is used quite a bit with Google's own sites - here is an example of an Angular app, with Angular being used to implement parallax scrolling (and probably more): http://www.google.com/nexus/7/

First make sure the fire sprinkler system is operational..

Reminds me of this http://en.wikipedia.org/wiki/Derweze

Or this, near Cirali in Turkey. Quite interesting to visit:

http://en.wikipedia.org/wiki/Chimaera_(geography)

Kids need some or all of the following things when growing up:

- a creek or open stormwater drain to play in, be careful during rain - a field big enough to experiment with golf in without killing someone - a covert campground as a base to launch fire cracker attacks on the local youth group - somewhere to do wheelies without being hit by a car - abandoned stuff to explore, the older and dirtier the better - a haunted looking house to be scared of (containing an elderly person who occasionally appears at the window) - a beach, island or isthmus, to play Robinson Crusoe on - some dirt to create a marble obstacle course in - a hoop and stick to make running more useful - a local cop who will make you do chores for trying to steal dinner from the local prawn farm - cane fields to get lost in - loose rules to a handful of sports - a tall tree with branches overhanging a river to tie a rope swing to - some kind of farm nearby where one can meet a horse, cow, goat or sheep

I'd also like to suggest a trampoline, but I'm keeping it out of the list because you have to buy it. It is imperative though for the early stages of learning to do somersaults in mid-air.

Thinking of all of these things from my childhood makes me somewhat lament the fact that I now live in a tiny apartment in Sydney and hardly ever leave the city.

+1 to this. I moved to Manchester a couple of years after uni to help the startup I was working for expand into the UK market. I spent the first year either at my day job or in my room wondering how to make friends. One day I walked past a tiny Aussie bar that had recently opened in Chorlton and impulsively walked in and asked for a job. The world opened up to me while working behind that bar. I became friends with so many wonderful people I never would have met if I hadn't taken that single step. At first I was petrified talking to customers but gradually the fear wore off and I was all of a sudden wheeling people out of that place in wheelie bins and organising lock ins with half the clientele.

Actually, the more I think about it, the more I realise that bar job was the difference between having the time of my life and wasting my entire two years worth of social life. Maybe it was the Manchester vibe but people just seemed to want a bartender in their life.