Join us on the AngularJS team at Google

[Brad Green]

Hey,

I'm the engineering manager for AngularJS and I'm looking for a few good engineers to join the team here in Mountain View, CA. This is a full-time position at Google.  You'd work on Angular's core features, its tools, and its partnerships with both development teams here at Google and external developers around the world.

Key Qualifications

• Proven ability to challenge the status quo in software engineering
• Strong affinity for collaboration with other developers
• History of solving issues in development productivity
• Commitment to code hygiene, readable code, tests and testability
• Optimistic, easy-going, and fun to be with
• Experience with client-side web technologies

You can find a more expansive, though generic, job description at http://www.google.com/about/jobs/locations/mountain-view/engineering/swe/software-engineer-mountain-view.html.  

To apply:

1. Create a description of why you believe you're a good fit for the list of Key Qualifications
   
2. Send it along with your resume via the "Apply Now" button on the page from the link above

I'm looking forward to hearing from you.

- Brad

[Luc Heinrich]

On 2 oct. 2012, at 19:31, Brad Green <br...@bradly.com> wrote:

> I'm the engineering manager for AngularJS and I'm looking for a few good engineers to join the team here in Mountain View, CA.

(doing the Jedi hand waving mind trick thing)

No Brad, you are looking for engineers in Paris, not Mountain View. Paris.

;)

--
Luc Heinrich - l...@honk-honk.com

[Brad Green]

One additional thing, please MAKE CERTAIN to say that you're interested in working with the AngularJS team in your cover letter.

[gdan...@gmail.com]

Hi,

That's great you are expanding your team! 

From my perspective, I'am developer who writes typical business apps, AngularJS is the only project which tries to push browser further in my domain. I know there are new JS APIs for 3d gfx, video, etc. However they don't help to create complex forms for a CRM app. 

I've just started my first client side JS project and chosen AngularJS over other frameworks. The bindings and ordinary html as templates from 1.0 version are really awesome. However I've noticed that some simple things (for server frameworks) are still hard to do in AngularJS. Average developers (IQ < 150) need more guidance and ready to use patters. For example how should I redirect a user to login page, how should I create one-to-many relationship between models and save new child records. 

I hope that in next releases you'll spend some time on less sexy problems I mentioned above. The power of Ruby on Rails comes from the fact it was extracted from real applications, typical business applications which have 50-200 db tables.

Typical, boring, business applications count for 90% of software produced all over the world. Therefore I hope AngularJS project will gain more visibility inside Google. 

Greg 

[Eddie Huang]

Hands down THE most enjoyable framework I've ever worked with, hope you find the people you're looking for, you definitely need more people :)

On Tuesday, October 2, 2012 10:31:32 AM UTC-7, Brad Green wrote:

[Sutikshan Dubey]

Can't stop myself from echoing Greg's message here.

We are also part of those 90% population who usually build Business application and first thing we need to implement are:-

- Authentication

- Authorization as per custom Roles.

- infrstructure required to build typical Master-Detail screens

- Editable Datagrid directive (something basic to start with).

We observed few people are working on these sample application to help whole community, just thought of bringing all these to your attention.

Soon after we get over with our sprints I will try to open source, whatever little we did in above areas.

[Eddie Huang]

There have been talks briefly at my current place of work (MobileIron), on open sourcing the suites of framework code I and my team wrote that includes a basic server side table directive. No promises though, as I don't know if management will give the actual go-ahead...

In the mean time, editable datagrid is actually not too hard to implement if you won't display more than 100 rows at a time. Everything on that list are also relatively easy ;)

[Jeremy Sager]

I don't agree with this post at all.

Authentication and authorization belong on the server side of the application; if you put your security solution in JavaScript please give me the address to your site and I'll crack through it in ten minutes.

A datagrid directive belongs in a project like http://angular-ui.github.com/

I'm not really sure what you mean by the infrastructure required to build typical Master-Detail screens. I feel like that's already there, maybe you can elaborate?

[Sutikshan Dubey]

I agree with you Jeremy. 

What I meant was, Implementing common stuff should be easier... May be better docs and blogs about implementing common stuff would help us.

Authentication/Authorization does happen at server side. Stuff most of the time we all would be doing at client side are, soon after start of any project are:-

1. Keeping "Encrypted" auth token stored at cookie/web-storage, if user has opted for "remember me" tick box, or session-storage.

2. Pop-up logon screen if user requested some unauthorized URL. (I know someone posted a nice solution in github and shared the link in this forum).

Please correct me if above two points are not recommended to do at client side. and if yes, what are the alternatives we have to remember authenticated user.

[Michael Bielski]

Wow... talk about thread-jacking. The man posted a job opening and turned to the user group in hopes of finding someone interested in joining the team, not an open invitation to tell him what is wrong with the product. Stay on topic people.

[gdan...@gmail.com]

We help to keep the job opening on the top of the list.

[Michael Bielski]

That's as may be, but I am not sure the end justifies the means.