CourseStorm

Sales

• Lead with heart: Foster a collaborative, positive team environment where people feel supported, challenged, and motivated to grow.
• Coach and develop the sales team. Own regular 1:1s with two Account Executives and one Business Development Representative; review calls and provide practical coaching to improve skills and performance.
• Act as a hands-on sales leader. Partner with AEs to guide strategy and support successful closes, and work with the CEO on high-stakes opportunities.
• Run daily sales operations. Lead the daily sales meeting, ensure follow-up and accountability, and maintain rhythm and motivation across the team.
• Create and organize outbound activity. Work with our marketing team to build and maintain calling lists and develop outreach sequences to maximize pipeline creation.
• Collaborate closely with Marketing. Work directly with our marketing leader to align on messaging, create campaigns, and grow the pipeline.
• Build repeatable processes. Set up playbooks, call-scoring frameworks, coaching cadences, activity standards, and other systems to scale a high-performing B2SMB sales org.
• Track KPIs and activity. Own sales team activity tracking, forecasting inputs, and regular reporting. Be responsible for driving performance toward the company’s annual sales goal.

Director of Sales

Full-stack Engineer

• Learn what the role of Software Engineer entails at a fast-growing startup
• Gain experience with technologies including: PHP, MySQL, Laravel, React, Javascript, GitHub, AWS, automated testing, RESTful APIs, Linux, etc
• Work in a team to deliver an actual feature to production for our customers

Software Engineering Intern

• At CourseStorm, we’re hiring an Engineer, not a coder.
• Writing code is no longer the hard part. AI can code faster than any human ever will, and pretending otherwise is a waste of your precious time. Coding is not a scarce skill. Good judgment is. Clear thinking is. Knowing what not to build is. And at CourseStorm we lean into that hard. Your job here is not to prove you can grind out implementations — it’s to design and review architecture, make tradeoffs, and use AI to turn those decisions into reliable, delightful software.
• What you’ll actually doOn this Engineering team of 5, everyone works across the entire stack, because a small team with real ownership requires it:
• - Design backend logic and APIs
• - Configure and maintain servers, background jobs, and databases
• - Build and refine front-end experiences that real people love to use daily
• - Deploy, monitor, debug, and clean up
• - Use AI constantly — to generate code, explore approaches, refactor aggressively, and delete more than you add
• There are no lanes to stay in and no handoffs to hide behind. If something feels confusing to a customer, that’s an engineering problem. If a system is brittle or overbuilt, that’s an engineering problem. If AI-generated code is messy, that’s also an engineering problem—and fixing it usually means stepping back and simplifying the design, not adding more.
• Our engineering principles
• - Start with an oversimplification and work your way toward complexity based only on hard evidence
• - Default to precedent, lean on the built-in learning and consistency that provides
• - Collaborate early and often when designing new solutions when you recognize that precedent has fallen short
• - Limit your technological footprint and invest deeply in the areas where we provide unique value
• - Iterate your way there and develop an allergy to "projects with a capital P"
• - Be explicit vs. implicit and your future self will thank you
• - There are no silver bullets, only lots and lots of lead bullets. The only silver bullet is iteration.
• We care far more about your ability to reason clearly, ask good questions, work as a team, and improve systems over time than about your familiarity with a specific framework or tool.
• Who tends to thrive here
• - Engineers who like working collaboratively within a small, tight-knit team
• - People who enjoy working across infrastructure, backend, and UI
• - Folks who are comfortable saying “this is too complicated” and working with others to fix it
• - Engineers who are excited to build leverage through AI instead of fearing it
• - People who want to continually learn and grow
• - Those who are responsive and invested in teammates' successes
• Who probably won’t
• - Specialists
• - People who equate craftsmanship with writing lots of bespoke code
• - Anyone uncomfortable with responsibility or ambiguity
• - Folks who need lots of planning to feel safe
• - Engineers who prefer to work alone