OpenSpace.ai | https://openspace.ai | Electron Software Engineer, Java/Kotlin BE Engineer | San Francisco | Remote | Full Time
At OpenSpace, we’re using cutting-edge technology — think the perception and navigation AI systems used in self-driving cars — to allow people out in the real world to efficiently capture their work, analyze it, and get things done. We’re building virtual time machines for every construction job site.
I am currently looking for:
1) An experienced Electron engineer to own our existing desktop sync app (plug in a 360-camera and we automagically upload what we need). This currently works but it needs some love and someone to own adding new features and applying Electron best practices.
2) An experienced BE/Kotlin backend product engineer. We use Spring, AWS, Postgres.
If you're interested please reach out to me (the hiring manager): jack@openspace.ai please put "HN whoishiring" somewhere in the subject line.
I've been looking for something like this for a while and it is quite nice so far. I was able to wire it into a side project very quickly and remove a lot of boilerplate.
MacroTower helps companies figure out their Marketing ROI. We pull data from our customers' Accounting, Marketing, and Sales software to automatically build all the important "macro" reports (CAC, LTV, and more).
We're hiring our first full-time engineer. You must know (or be comfortable learning) Python, Go, and Javascript (React/Redux).
MacroTower helps companies figure out their Marketing ROI. We pull data from our customers' Accounting, Marketing, and Sales software to automatically build all the important "macro" reports (CAC, LTV, and more).
We're hiring our first full-time engineer. You must know (or be comfortable learning) Python, Go, and Javascript (React/Redux).
Wow, thanks for writing that blog post! You highlight pretty much all the reasons why I made dumb-jump. Please don't hesitate to make issues on github if/when you run into issues/ideas.
Sorry to hear it didn't work for you. Would you consider opening an issue on github outlining what you were trying to do? Then you can be more than just hopeful that it will improve.
