Backend Engineering Intern (paid, project-based, remote)

WhyWave is building a voice AI companion for children ages 3 to 5 that never puts a screen in front of the kid. That constraint pushes almost all of the interface work onto the parent's side: setting up the device, deciding what topics and values the companion should follow, checking in on what their kid has been asking about lately.

Current state: real engineering work is already in progress on the product itself, plus some published technical writing about it. No shipped product with real users yet. This role extends the client side, not a from-scratch build.

Paid, project-based internship. We'll talk numbers directly rather than post them. The product ships for English-speaking markets, but the team works in Russian internally, so you don't need English, and Russian speakers are preferred.

Depending on what interests you:

• the real-time service layer: streaming audio over WebSocket/WebRTC, session state, the on-device/cloud split
• the API between the voice pipeline and the parent's companion app
• latency, end to end, across the whole speech-to-speech loop
• a way to test model or pipeline changes without quietly making responses slower

Python (AsyncIO), an async service layer, WebSocket/WebRTC. That's the
stack.

Requirements: Python, AsyncIO, WebSocket/WebRTC basics.

You'd be working on a system where latency is a hard constraint, with
someone who deals with that same constraint every day, not a CRUD app with
a deadline. If it works out, staying on past the internship is a realistic
option.

If designing around what's NOT there sounds more interesting than another dashboard apply through Wellfound. It will also be great if you specify your Linkedin profile.