[Foundation-l] Guidelines for the use of iframes?

[Erik Moeller]

HR recently switched to an externally hosted applicant tracking system
called Jobvite. It's sadly proprietary, but very feature-rich and used
by many tech companies, including e.g. Mozilla. Basically the previous
process was for candidates to be dumped in a shared inbox, where
recruiters and hiring managers would have to keep track of them with
the aid of tracking spreadsheets and lots of emails. An ATS automates
a lot of the tracking and workflows, and helps ensure that people
don't get dropped. It also sends hiring managers reminders to submit
all the required hiring documentation, etc. So in general it's a good
thing, although we sometimes curse at aspects of its UI.

The rationale for the iframe is to automate the job listings on the
WMF site and surface the various Jobvite features.

Yes, that means that the user's browser will contact hire.jobvite.com
when loading the page (although all its resources will be loaded in
the context of the iframe). AFAICT the main issue here is to clarify
in the footer that job applications and job descriptions are run
through an external service called Jobvite and subject to the Jobvite
privacy policy, to avoid any confusion.

Whether the iframe is a good idea still remains to be seen. Jobvite
makes it unnecessarily hard to link to JDs directly (because their
ideology is that everyone should come through some social media
funnel, I think), and the navigation is heavily JS dependent right
now. So we might want to switch back to a hybrid format. The job pages
are also still actively being re-designed, and the setup might change
significantly in coming weeks.

Erik
-- 
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation

Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate