Design: Page for /employers

[davidmolina]

Feature

Similar to a product demo, an employers demo will be a landing for companies, organizations and government agencies that want to know more about hiring our military veterans, spouses and military family members.

Why is this feature being added?

This feature enables employers to quickly and seamlessly learn more about our organization and determine whether hiring one of our members makes sense. The value add is that CEOs, C-level and hiring managers don't have to wait to get in touch, they can have all the data at their fingertips at an instance and make an informed decision internally before reaching out. We want to limit the warming period as much as possible. We want employers to know the value add before reaching out.

What should your feature do?

• The landing (or popup) will ask for name, title, company, email and phone number to request more information. This data can populate back into our Airtable where the CEO and/or Chief of Staff can make contact and answer their questions and next steps.
• The automatic email response will send the recipient our short deck, and a link to a visualization graph of our membership, including (1) total number in our community (via Slack), (2) geographic location (via zip code), (3) military branch, (4) number of employed, (5) number underemployed/unemployed and actively looking for a software developer role, and (6) programming languages.
• Internally, we should be able to update this and automate as much as possible. Internally, we should have a special code to access the visualization graph (or make it open) to brief folks when we're giving a talk or in a meeting.

[kylemh]

This is a great idea. We'd likely be reaching "end goal" status at the point when we implement this feature.

[davidmolina]

@kylemh exactly. It helps leadership better sell Operation Code when we have answers to their questions about numbers, etc.

[hollomancer]

Opening this as a task for design/wireframe to Hacktoberfest.

[hollomancer]

Deprioritizing, as this requires too much backend work to act on right now.

[kylemh]

@dmarchante can you document this issue in the new repo so we don't lose it? Feel free to apply the blocked label and a comment saying that it's blocked by the need for parity