Page 1 of 1

PHP Developer Opportunity - Yahoo!Inc. Sunnyvale,Full-Time.

Posted: Wed May 18, 2005 4:25 pm
by gengoid
Senior Front-end Engineer for Yahoo! 360

Are you prepared to build the next innovative web service that Yahoo has to offer? The Yahoo! 360 team is looking for a strong, passionate, self-motivated Senior Front-end Engineer to join the Yahoo! 360 Engineering team. You'll work collaboratively with software engineers, interaction designers, visual designers, user experience researchers, marketers, and product managers.

The ideal candidate will have a strong command of PHP, procedural and object-oriented design, dynamic content retrieval, performance optimization techniques, unit testing techniques, debugging techniques, state management, HTTP, and Apache. He or she would feel comfortable working within a Unix environment, has used CVS, and is familiar with bug tracking tools. A Computer Science degree or related work experience is also required. Knowledge of client-side code (HTML, CSS, JavaScript, DHTML), cross-browser compatibility issues is highly desirable.

The ideal candidate also enjoys collaborative work environments and applying his/her technical skill to solve user experience issues. Strong verbal and written skills enable this candidate to work effectively with others and help drive features to completion.

Must have qualifications include:
* A strong command of PHP.
* Familiar with procedural and object-oriented design principles.
* A Computer Science degree or related work experience.

This job is currently available for U.S

Posted: Tue May 24, 2005 12:50 pm
by ody
I can not help but wonder what:

Code: Select all

<span style='color:blue' title='ignorance is bliss'>you</span>.S</span>
is all about...

Posted: Tue May 24, 2005 2:37 pm
by John Cartwright
our word filters...

he did not spell "you" correctly.

Example, "you" in aolbonics become u

Posted: Wed May 25, 2005 6:54 am
by Chris Corbyn
He meant US but with the dots in there it reads the first letter U as aolbonics and phpBB has a bug which makes our filter parse the HTML back into the post :? . I'll correct the post....

[Note: Use of &#xx; e.g. &#85; prints the Ascii cahr as expected (ascii 85 == U )]