WHO WE’RE LOOKING FOR

We’re looking for builders, tinkerers, and thinkers who aren’t afraid to get their hands dirty.

If you’ve written code, built a product, launched a feature, led a community experiment, or solved a messy tech problem, we want your story on stage.

This isn’t about theory or pitch decks. It’s about showing how technology is moving Africa forward, one project, product, or bold idea at a time.

SESSION FORMATS

1. Tech Talks (30 minutes)

Dive into the story behind what you built, the challenge, the process, the decisions, the results.

Perfect for developers and teams who want to share practical lessons, patterns, or frameworks from real-world experience.

2. Workshops (60 minutes)

Hands-on learning sessions where attendees can follow along and build something tangible, code, model, workflow, or concept.

This is your space to teach by doing.

3. Interactive Demos (45 minutes)

Show your project in action. Walk the audience through how it works, let them test it, and explain the thinking behind it.

TECHNICAL FOCUS

Primary Focus Areas

• Google technologies: GCP, Firebase, Flutter, TensorFlow, Angular, Vertex AI, Gemini
• Core domains: Artificial Intelligence, Cloud Computing, Cybersecurity, Blockchain

Secondary Focus Areas

• Web technologies, open-source projects, developer productivity tools
• UI/UX, human-centered design, and scalable software practices

If your topic sits between these areas, even better. We value interdisciplinary ideas and original perspectives.

SUBMISSION GUIDELINES

Your proposal is your story.

Make it clear, grounded, and worth attending. We’re not looking for buzzwords or fancy slides, we’re looking for sessions that make developers stop scrolling and say: “I need to be in that room.”

DO’S

1. Keep it on-theme. Align your talk or workshop with Catalyzing Africa’s Digital Transformation through Emerging Technologies.
2. Make it useful. Share practical insights, real-world case studies, and technical lessons you’ve learned firsthand.
3. Be specific. Define your audience level — Introductory, Intermediate, or Expert.
4. Be clear about outcomes. Tell us what participants will learn, build, or walk away with.
5. Encourage interaction. Live coding, demos, Q&A, keep the audience part of the experience.
6. Add local relevance. Examples or stories rooted in African contexts stand out.
7. Respect your slot.Tech Talks → 30 min, Workshops → 60 min, Interactive Demos → 45 min

DON’TS

1. Don’t turn your talk into a product pitch or promotional session.
2. Don’t exceed your session time.
3. Don’t submit duplicate or nearly identical proposals.
4. Avoid content that’s offensive, discriminatory, or non-inclusive.
5. Don’t recycle talks word-for-word from other DevFests , bring something new, even if it’s an updated angle.

WHAT MAKES A STRONG SUBMISSION

A solid submission is clear, specific, and gives both the selection team and attendees a reason to care.

Title

Your title is the first impression. Make it count. It should be sharp, descriptive, and reflect what your session truly delivers. Creative titles are welcome, but clarity beats cleverness every time.

Your goal: make the reader stop and think, “That’s exactly what I want to learn.”

Description

1. Concise

Your abstract should describe what the session actually covers, not sell it. Two short paragraphs are enough if they communicate substance. Start with the technical focus or problem space you’re addressing: what technology, use case, or insight are you exploring? Then outline how you’ll approach it, what tools, demos, frameworks, or data you’ll use. Be clear if it’s hands-on, exploratory, or conceptual. Finish with what attendees can expect to learn or build. Reviewers should be able to read your abstract once and immediately understand what will happen in the session and why it matters.

2. Complete

Be clear about who your audience is. “If you’re an Android developer exploring how to integrate GenAI tools into your app, this session is for you.” That single sentence helps both the committee and attendees decide if it’s the right fit.

Outline the main points or demos you’ll cover. Give a sense of flow or structure, introduction, core idea, implementation, results, lessons.

Finally, define what participants will take away: “You’ll leave with a working prototype” or “You’ll understand how to design secure Firebase architectures.”

Avoid vague language and avoid confidential material. Submissions should be shareable and transparent.

3. Coherent

Make sure your proposal reads clearly from start to finish. Disorganized or confusing abstracts rarely make it through review. Proofread. Simplify. Get to the point. A clear, readable submission reflects a well-prepared session.

4. Use the Present Tense

Write as if your session already exists.

“This session explores real-world uses of Vertex AI in education” is better than “This session will explore…”

It feels confident and immediate.

Bio

Your bio gives context on who you are and why your perspective matters. Keep it short, two or three sentences covering your background, area of expertise, and what you’re currently working on.

If you’re part of a developer community, startup, or research project, mention that briefly. Links to professional or project profiles (LinkedIn, GitHub, portfolio) are optional but useful.

Avoid personal details or long career stories. Keep it relevant and professional, this bio will appear on event materials and the website.

Notes and Comments

This field gives the review team useful background that doesn’t fit in your abstract. Use it wisely.

You can include:

• Context on how the session fits the event theme.
• Links to previous recordings, slides, or demos.
• Information about where the session has been presented before and what feedback it received.
• Any unique perspective, project, or local context that strengthens your proposal.

If you’re referencing past talks or feedback, anonymize or shorten links to avoid personal identifiers.

This section is seen only by the selection committee, not attendees, use it to help reviewers see the value behind your submission.

NOTE ON COVERAGE OF EXPENSES

Conference Access

All speakers receive a complimentary full conference ticket for DevFest Mt. Kenya 2025.

This ticket grants access to all sessions, workshops, networking spaces, and side events.

Co-speakers listed on approved sessions are also eligible for free admission, provided they have contributed meaningfully to the preparation and delivery of the talk.

Travel and Accommodation

DevFest Mt. Kenya is a community-led, non-profit event. We do not provide travel or accommodation support for speakers. However, the organizing team can assist with: Providing a formal invitation or VISA support letter if required.

Recommending trusted accommodation options and travel logistics for speakers attending from outside Nyeri or Kenya.

Expenses and Reimbursements

There are no reimbursements for travel, accommodation, or other personal expenses. Speakers are encouraged to confirm their participation only after ensuring they can cover their own costs.

Speaker Support

If you have specific accessibility needs or logistical concerns related to participation, please reach out to the organizing team at the provided speaker support contact. We’ll do our best to assist within our capacity.