Big Data TechCon is for technical practitioners – the data scientists, developers and analysts who actually make Big Data work at their companies or for their clients. Job titles may vary, but the attendees of Big Data TechCon will be relying on you to help get them up to speed – or increase their expertise – that will empower them to give their companies a competitive advantage.
What do these professionals all have in common? They'll be attending Big Data TechCon in the San Francisco Bay Area from Oct. 27– Oct. 29, 2014, to learn HOW-TO master Big Data.
Big Data TechCon kicks off on Monday morning with deep-dive full-day tutorials (7 hours in length) and half-day tutorials (3 1/2 hours in length). Tuesday and Wednesday will feature dozens of 75 and 150-minute technical classes.
When you propose a tutorial or a class, be clear about the objective. Details matter. Expect to teach to your session description. For example, if you say that your session is advanced, it must be advanced. If you say your session is hands-on, it must be hands-on. If you say that your session covers three specific frameworks, you must cover all three frameworks. We also only accept sessions that are 100% tool and vendor agnostic. Do not send a sales or marketing pitch.
In your session proposal, please tell us:
• The proposed title of your session. We reserve the right to change it to our style.
• A session description of at least 150 words, and we prefer 300 words. The more detail, you provide, the better for everyone. We reserve the right to change it to our style.
• If you will be showing code, please let us know: We highlight that in the course catalog.
• If your session is a lecture format, or if it's a hands-on with attendees following along on their laptops.
• If you commit to providing your presentation and/or handouts at least a week before Big Data TechCon.
• Tell us if your session is Overview, Intermediate or Advanced. If you are unsure, please see our guide for session levels below.
• Explain what prerequisite skills or knowledge should be expected. Be specific!
• The speaker submission should be submitted to Big Data TechCon by the speaker himself/herself. Please also include the following information in the speaker proposal. Incomplete submissions may not be accepted.
• Your bio, 125–150 words, with a summary of your teaching expertise. We reserve the right to change it to our style.
• Your name, mailing and e-mail addresses, telephone and cell phone numbers.
• Your hi-res digital headshot, see http://www.bzmedia.com/photo.htm.
• Twitter and blog addresses (if you have them).
Please note, acceptance of your class proposal will be based not only on your topic's timeliness and relevance, but also on your personal credentials as Big Data expert and experience as an instructor. Be sure to communicate clearly what your class will be about, who will benefit from taking it, any prerequisite knowledge, and what the student will learn. A muddled, confused submission is likely to get rejected.
The ideal instructor is someone with real-world experience building Big Data solutions. You should have proven experience teaching practical solutions to real-world challenges, presenting new skills, and offering students an information-packed learning experience. If that describes you, please submit a session proposal electronically as a text e-mail or as a Word document to Katie Serignese, Conference Program Manager.
Conference Program Manager
Schedule and Deadlines
Monday, October 27, 2014: Tutorials
Tuesday, October 28: Technical Classes
Wednesday, October 29: Technical Classes
Attendees rarely complain that a session has too much detail – but they will be disappointed if your content is fluffy. Don't forget: This is a technical conference, and the attendees are season data management, development or analysis professionals. In all sessions, attendees want to know the details. For all development-oriented sessions, attendees expect to see code.
Overview: No previous knowledge of the class's subject is required, and the session will be a high-level introduction of the topic. (Note: We accept very few overview-level classes.)
Intermediate: These broad technology sessions emphasize capabilities and how things work. As appropriate, the instructor will show examples or code. (Note: We accept very few intermediate classes. We suggest you take the session to a deeper level and make the class advanced.)
Advanced: These sessions teach attendees how to implement a solution. As appropriate, the instructor will include detailed samples or code. (We plan for at least two-thirds of sessions to be at the advanced level.)