Make Rain
Product Engineer, Sales
About this role
Rainmaker is seeking a Product Engineer to develop software that enhances customer interactions and drives sales. This role involves creating innovative visualizations and tools that represent the company's weather modification technology, directly influencing contract closures.
What you'll do
- Design and build customer-facing results portals and dashboards
- Create interactive GIS tooling for proposals and RFPs
- Develop a demo environment for sales presentations
- Establish a component library and visual identity for software
- Implement instrumentation to analyze prospect engagement
- Collaborate closely with leadership and customers
What they're looking for
- Frontend development (React, TypeScript)
- Backend proficiency (Python or Node)
- Experience with data visualization tools (D3, Mapbox, etc.)
- Strong understanding of design principles
- Ability to navigate ambiguous problem spaces
- Translating technical concepts for non-technical audiences
- Familiarity with geospatial tools
Benefits
- Impact on product direction and design
- Direct access to company leadership
- Opportunity to work with cutting-edge technology
- Influence on the customer experience
- Chance to work in a niche industry
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Make Rain
Make Rain develops weather modification technology through innovative aerosol and liquid dispersion systems designed to enhance precipitation and address water scarcity. The company is hiring software engineers, mechanical/aerospace researchers, and product engineers to build both the core dispersion technology and customer-facing software solutions.
View all jobs at Make RainLikely interview questions
- Walk us through a data visualization or geospatial project you've shipped end-to-end. What was the technical stack, and how did you balance engineering decisions with design and user experience?
- Tell us about a time you've had to explain complex technical or scientific concepts to non-technical stakeholders. How did you know what resonated?