Highnote is looking for a skilled web software engineer to help us build a truly unique communication tool for audio creators and their teams.
📣 We’re currently only hiring either a:
- Senior Software Engineer with a salary of $145k
- Lead Software Engineer with a salary of $165k
For details on level-specific salaries and responsibilities, read more here. We’re currently only hiring for either a Senior or Lead Engineer.
- You’ll earn $105k -$165k / year (see Engineering Levels above) and ~1% equity
- You’ll be the 2nd engineer on a seed stage team of 5 (Jordan Bradley, Chris Muccioli, Paulina Vo, and Christine Cha)
- You’ll report to Christine Cha
- You’ll receive full benefits on a remote team embracing the future of work
Highnote is building the simplest and most effective way for audio creators — musicians, podcasters, voiceover artists — and their teams to collaboratively make comments, exchange ideas, and collect listener feedback on their audio. We’re venture-backed by the same investors behind productivity tools like Airtable and Superhuman.
Check us out here →
Highnote is a modern, real time web application running on a lean serverless stack.
- React, Webpack
- Firebase (Firestore, Cloud Functions, Storage) + Node.js
Our Benefits and More
Remote first, 4-day workweek, full health benefits, unlimited PTO (for real), and more.
Learn more about working at Highnote →
For details on level-specific salaries and responsibilities, read more here.
- You care deeply about your impact on those around you and the broader community. You try your best to treat people with kindness, patience, and empathy.
- You take a lot of pride in your work and your impact on the team. This, combined with excellent time and project management skills, makes you a reliable and productive contributor to the team.
- You have professional experience navigating challenging situations, various personalities, and diverse work styles and enjoy the dynamic, constantly changing environment of an early-stage company.
- When faced with ambiguity or challenges, you proactively ask questions and come up with solutions. You have methodical approaches to debugging issues, digging into documentation, and learning new concepts.
- Leadership & Accountability
- Associate-level candidates manage their own time productively and complete their assigned tasks with guidance from senior team members.
- Mid-level candidates can break down a small project into executable tasks and implement it from start to completion with some technical guidance.
- Senior-level candidates can also break down larger, more ambiguous projects. They make well-informed decisions on software architecture and continuously improve the overall team’s code quality and efficiency.
- Lead-level candidates also manage long-term technical roadmaps and build robust, complex products from the ground up. They use their expertise to shape the overall technical vision and engineering team culture.
- Bonus: You have personal or professional experience with audio creation (playing in a band, being a voice-over actor, working with musicians, etc.)
- Relevant Experience
- Associate-level candidates should have experience building full-stack web applications.
- Mid-level candidates should have at least one year of professional experience building complex, modern, and performant web applications.
- Senior- and Lead-level candidates should have multiple years of professional experience being core contributors to applications that serve thousands of active users.
- Language Mastery
- Mid-level candidates can write these languages fluently and get comfortable in larger, complex codebases with some help from other teammates.
- Senior- and higher-level candidates can dive into legacy codebases, third-party source code, and decipher complex systems of logic without help from other teammates.
- You can build and debug complex React applications (like ours!), but frameworks are just part of your larger toolkit. You make well-informed decisions on when and how to use frameworks and other third-party tools, and when to roll your own solutions.
- You have a keen eye for design and are able to build pixel-perfect implementations of complex interfaces. You are an excellent wrangler of the CSS & HTML and are able to keep things accessible, beautiful, and performant.
- You have a solid understanding of how servers and clients interact, and inform your architectural decisions with full-stack considerations. You are comfortable making well-informed decisions about our server-side code, data models, and API design.
- You have extensive knowledge in a particular technical area, ex. WebAudio, WebGL, progressive web applications, render performance, accessibility
- You have additional backend and/or devops skills
- You have additional product and/or visual design skills
- You have previous experience managing and/or growing an engineering team
Teamwork and Communication
- You are an effective communicator, whether it’s via Slack, Zoom, or in person. You can articulate your thoughts and opinions with sensitivity and empathy for others.
- You are an engaged code reviewer and technical collaborator. You help other teammates improve their contributions through detailed and relevant feedback while maintaining a culture without blame or fear of making mistakes.
- You think about and understand your work deeply. Because of this, you can explain things clearly in different ways to all different audiences (especially non-technical ones) without losing detail or context.
- You deliver your work reliably. You give well-informed estimates on your active or upcoming projects, and manage expectations accordingly when these estimates change.
- As part of the product team, you always consider future business, user, and internal needs when making decisions. You collaborate with other departments to build solutions that reflect the whole company’s priorities, not just engineering.
In joining an early stage team, you’ll have unprecedented control over your trajectory, and can play a big role in how we define career development at Highnote for team members to come. To read our current thinking on different engineering team roles, learn more here →
A Sample Week at Highnote
Here’s an example of what a typical week might look like for this role:
- Every day, Monday - Thursday
- Engineering Team Chat (30min) - Casual engineering meeting to discuss any questions, challenges, or other ideas around technical or just team-related topics.
- Full Team Standup (30min) - All team members give a quick status update on what they’re working on, with any open questions or blockers. Sometimes we’ll do a mini deep dive on specific topics that come up.
- Start building out active feature project.
- Quick spontaneous huddle in the afternoon to pair program on a gnarly issue.
- Product Team Chat (1hr) - Meet with Chris, Jordan, and Christine to talk through any feature work in progress. We give lots of room for open questions, discussions, and suggestions. Some things might be in discovery stage, some might already be on staging, ready for QA!
- Continue working on feature project
- Feature work ready for initial review! Put it in PR and send to manual QA.
- Start work on a smaller improvement item, like refactoring a shared module or polishing up some UI interaction states
- Address PR and QA feedback on the feature project, as well as some other improvements we may have missed the first time around.
- Sprint Planning (1hr) - The whole team meets to align on our high-level initiatives and plans for upcoming week. This is a place to ask prioritization questions and give an update to the whole team about work in progress.
- Friday - Sunday
- Off. We operate on a four-day work week at Highnote, so your weekend is Friday through Sunday! You might see one of us pop online for a bit to work on something because we’re too excited about it to wait for Monday, but it’s not typical or expected.