Sobre este puesto de Product Engineer en Make Rain
Rainmaker builds systems to make it rain. Our autonomous drone fleets and weather modification platform operate worldwide, expanding freshwater supplies, protecting agriculture, and proving that cloud seeding works at scale.
We need a product engineer to build software across Rainmaker.
Context
Rainmaker is about 120 people, and the software team is small. Our work combines autonomous aircraft, atmospheric science, field operations, data analysis, and customer delivery. Product engineers work across those areas and take meaningful ownership of what Rainmaker builds.
The role
Rainmaker's software supports campaign planning, field operations, weather analysis, aircraft operations, and customer delivery. You will build across that system, including internal tools, our operational platform, data products, and customer-facing software.
You will work directly with operators, scientists, engineers, and business teams. You will find important problems, decide what software should do, and own the solution from the first prototype through production.
This is a hands-on, full-stack role on a small software team. The work is not tied to one product or department. You will go where better software can have the most impact.
What you'll do
Build internal tools that replace manual workflows and help teams coordinate
Develop the operational platform used to plan, monitor, and review campaigns
Make weather, geospatial, flight, and campaign data useful to the people making decisions
Build customer-facing products when the problem calls for them
Work with users to understand problems, test ideas, and improve what you ship
Own products through deployment, maintenance, and continued development
Improve the shared components and technical patterns behind Rainmaker's software
What we're looking for
You have owned software from an ambiguous problem through a maintained production product
You are strong with React and TypeScript and can work across a backend using Python or Node, databases, and cloud infrastructure
You have good product judgment and can create useful interfaces without a complete specification or finished design
You have built software for complex, technical, or data-intensive workflows
You work well with users and can distinguish the underlying problem from the first requested feature
You communicate technical ideas clearly to people with different backgrounds
