Preparedness: Is the speaker prepared to deliver a good talk? Do they have a clear thesis or goal?
Avoid fitting too many ideas into the presentation. Keep it simple: about 2-3 paragraphs is what we are looking for in the pitch
Has the speaker demonstrated experience in the topic? (Providing links to GitHub repos, or explaining the content)
Avoid fluff or empty language We prefer direct, technical language to sales pitches or hypothetical situations. Examples of fluff:
Relevance: Is the talk a good fit for WiSE? Does it align with our mission to “Empower Diverse Women in Tech Careers”
In addition to speaking about code, topics such as UX, Product, testing, security, leadership, and career development are excellent fits for our community
We aim our content at an audience of women with an average of 2 years of industry experience
While you are free to mention your affiliation or work, please avoid content that is overly promotional
Give something to your audience. While we love to hear success stories of women doing amazing work, avoid self-aggrandizing language or too much autobiographical content. You’ll reach more of your audience with a “coach” mindset rather than a “hero” attitude. Learn more here:
Diversity / novelty
Does the speaker bring a fresh perspective to our event?
Is the speaker sharing something modern? Is there a unique perspective? E.g. a talk on a decade-old toolset might not be as useful unless there’s some specific tie-in to current practices.
Is there a good balance of speakers across the various talks? We may adjust speakers across different events to ensure we share perspectives from different companies or affiliations.
We get a lot of submissions on imposter syndrome, and there is a risk here of a self-fulfilling prophecy on a topic that is well-covered in books and articles. For a contemporary approach, consider:
<aside> 🤝
All submissions must follow our Code of Conduct
</aside>
Cross-functional Teams
An effective cross-functional team can introduce fresh ideas and methods of collaboration to develop more unique and powerful solutions. It's easy to fall into the habit of doing things one way and declaring it to be the "right way." A cross-functional team challenges conventional thinking and can offer fresh ideas and methods to a team, resulting in a better product for customers.
Because of the lack of views they bring to the table, organizations that operate in silos suffer with problem solving. Cross-functional teams push established ways of thinking, resulting in better decision-making processes. We may overcome groupthink and unconscious prejudices by bringing together people with diverse opinions and areas of expertise.
Team members may also believe that deadlines are less strict, and they can work more independently—or at their own pace—in a cross-functional setting. While some of this is a part of the process, it's still crucial to approach cross-functional initiatives methodically to avoid future delays and setbacks.
Every project should have a regular feedback loop to ensure that everyone is accountable for completing their portions of the task on schedule. Utilizing a work management application to plan activities and deliverables, establishing benchmarks, and being able to guarantee work is completed on time and under budget throughout the project life cycle can help.
<aside> 💕 What we liked about this submission: Provides a useful perspective on collaboration, an important skill in Engineering teams. The description gives us a clear introduction to the subject matter and why it’s important. Note that not all submissions have to be this long. This one kept a central focus, which is important for the short format of Lightning talks
</aside>
Cloud I will talk about cloud
<aside> 🚫 Too vague. We can’t see specifics of what the speaker wants to present so we can ensure it’s a good fit for our audience
</aside>
How to make passive income on [eCommerce site] Lessons from a seven-figure seller
<aside> 🚫 Off-topic, and demonstrates signs of multi-level marketing or scam tactics.
</aside>
Why girls should study STEM STEM (science, technology, engineering, and mathematics) subjects are essential for developing the skills and knowledge that are in high demand in the 21st century. However, many girls face barriers and stereotypes that discourage them from pursuing STEM education and careers. Girls should study STEM in school because they can discover their passions, unleash their potential, and achieve their goals in these fields. By studying STEM in school, girls can also challenge the gender norms, inspire other girls, and make a positive difference in the world.
<aside> 🚫 While this is a worthy topic, it is not a fit for WWCode, which focuses on adult women in technology careers.
</aside>
Getting Started as a QA Engineer Some tips and information on how to get started with a career as a QA Engineer. Here’s a link to a past blogpost I wrote on the subject: [link]
<aside> 💞 Quality Assurance and Engineering are vital topics for our members. Additionally, the applicant demonstrates her expertise by providing an example of her writing. The format is focused and inspiring.
</aside>