[Deepgram x DEV Hackathon Submission Post Placeholder Title]
Tags: hackwithdg, javascript, python, programming
Published: 2022-04-06 23:55:23

<!-- Please delete anything appearing between angle brackets and create your own title before publishing your submission post.  -->

<!-- [Instructions]: # (To submit to the Deepgram Hackathon on DEV, please select the template that corresponds with the challenge you are submitting to and delete the content for the other submission type. You are encouraged to submit as many times as you would like, but please create a separate submission template for each project.) -->

<!-- ✨Pro Tip: You can link all of your submissions together by adding `series: {your series name here}` to each post in the header section – right between “tags” and “description. ✨ -->

— 

<!-- [Template 1: Build Challenge]: # (Select this submission template if you have built an application using Deepgram for this hackathon.) -->


### Overview of My Submission
[Note]: # (Please make sure the project links to the appropriate GitHub repository, and includes the [Apache-2 permissive license](https://www.apache.org/licenses/LICENSE-2.0)  and README.)


### Submission Category: 

<!-- [Note]: # (Accessibility Advocates, Analytics Ambassadors, Gram Gamers, Wacky Wildcards) -->


### Link to Code on GitHub

<!-- [Note]: # (Our markdown editor supports pretty embeds. Try this syntax: `{% github link_to_your_repo %}` to share a GitHub repository) -->
<!-- [Note]: # (Your repository must include a README) -->
<!-- [Note]: # (You must use and list a permissive license for your code: MIT, Apache-2) -->


### Additional Resources / Info

<!-- [Note:] # Screenshots/demo videos are encouraged! -->


—

<!-- [Template 2: Innovative Ideas Challenge]: # (Select this submission template if you are creating a written submission for this contest that does not include a coding element.) →

<!-- [Note]: #If you want some tips for getting started with writing to help you with this submission, check out: https://developers.deepgram.com/blog/2022/03/technical-writing-a-beginners-guide/  -- >

### Introduction

<!-- [Note]: # (Tell us why you decided to participate in the Innovative Ideas category of the Deepgram Hackathon on DEV. Have you ever encountered Deepgram before or had any prior understanding of speech recognition technology before participating? Anything else you’d like to share with us upfront that’s relevant to your submission can go here) -->

### My Deepgram Use-Case

<!-- [Note]: # (Share your story. We want to hear all about it! What's your big idea? What inspired your submission to the Innovative Ideas category of the Deepgram Hackathon on Dev? How do you think Deepgram could help with their speech-to-text technology? Anything else you’d like to share with us upfront that’s relevant to your submission can go here.) -->

### Dive into Details
<!-- [Note]: # (Break down your idea. What is the problem or challenge you'd like to see solved with Deepgram? Who would benefit from this innovation--is there a specific industry, region, or group of people? How will it help them? Are there Deepgram features that would be important in this use case? Hint: Take a look at Deepgram’s documentation to inform what you share: https://developers.deepgram.com/documentation). Top Tip: Is there research that led you down this path, things you learned about Speech-to-Text technology, speech recognition AI, your writing/research process, etc? Talk about that here.)  -->


### Conclusion
<!-- [Note]: # (Any thoughts or takeaways about what you've learned from participating in Deepgram Hackathon “Innovative Ideas” challenge can go here! If you're planning on writing a series of posts for the Hackathon, consider teasing your next post.) -->

—

<!-- [Note]: # (Be sure to include the DEV usernames of your collaborators, if any. Prizes for winning projects with multiple collaborators will be sent to the person who posts this submission and they will distribute the prize evenly. DEV will not split prizes as per our rules. We are unable to make any exceptions.) -->

<!-- [Reminder]: # (Submissions are due on April 11, 2022 @ 11:59 PM UTC) -->