Aurora Solar

JavaScript/Frontend Engineer (Mid to Senior)

We are looking for a mid to senior level JavaScript/frontend engineer who will help take our cloud-based solar design software, which is used by thousands of solar companies worldwide, to the next level of functionality and interactivity. We are a fast-growing, VC-backed startup and every engineer contributes to key feature rollouts and bringing cutting-edge technology to the solar industry. If you are interested in solving challenging problems that truly matter, we would love to hear from you!

About the Job

  • Build new functionality for our industry-leading solar design platform

  • Spearhead the development of new greenfield products

  • Write high quality, well tested code

  • Highly competitive salary


  • 4+ years of experience building maintainable, clean, and well-tested user-facing code

  • Love writing Javascript or TypeScript (React, Redux, Styled Components experience a plus)

  • Great engineering skills and strong CS fundamentals.

  • Excellent collaborative and communication skills.

  • A thoughtful balance between loving to ship code fast and keeping up best practices for our repos

  • Fluent in written and spoken English

  • At least 50% overlap with Pacific Coast working hours

How To Apply

Please email an updated resume and answers to the following questions to [email protected]. Submissions without a resume or answers to the questions will be ignored.

  • What was your favorite project you’ve worked on and what did you like about it? Can you provide links?
  • What are some of your opinions on JavaScript testing? If you were brought in as a consultant for a company that had no tests, how would you sell them on JavaScript testing and what is some advice you’d offer the engineers writing the tests?
  • If you were designing your own JavaScript framework like Angular, Ember, or React: What are 3 features you would make sure to include and why?
  • If you could add one feature or a set of features to an upcoming JavaScript specification, what would it be and why? 
  • What are two of the biggest problems you've seen in frontend teams or codebases from your experience in the past? How would you address them?