Software R&D Engineer Needed
Budget: $750 – $1,500 USD
I’m kicking off a new-product R&D cycle and need an engineer who loves turning blank-sheet ideas into working software. The entire effort is green-field: no legacy code, no fixed stack—just a clear mandate to research, prototype, and validate a fresh concept before we move to full-scale development.
You’ll start by exploring technical approaches, comparing frameworks, and mapping out architecture options that balance performance, scalability, and cost. From there, I expect rapid proof-of-concept builds to stress-test core features and expose unknowns early. Your findings—both successes and dead ends—should be documented clearly so we can make informed go/no-go decisions at each stage.
Deliverables I need to see:
• A concise research brief outlining explored technologies, key trade-offs, and recommended direction
• Source code for at least one functional prototype that demonstrates the product’s core value proposition
• A short roadmap that highlights next R&D steps, estimated effort, and potential risks
Please be comfortable iterating in uncertainty, explaining your rationale to non-technical stakeholders, and working autonomously while keeping me in the loop through brief, regular updates. If tackling new software ideas from the ground up sounds exciting, let’s talk.
You’ll start by exploring technical approaches, comparing frameworks, and mapping out architecture options that balance performance, scalability, and cost. From there, I expect rapid proof-of-concept builds to stress-test core features and expose unknowns early. Your findings—both successes and dead ends—should be documented clearly so we can make informed go/no-go decisions at each stage.
Deliverables I need to see:
• A concise research brief outlining explored technologies, key trade-offs, and recommended direction
• Source code for at least one functional prototype that demonstrates the product’s core value proposition
• A short roadmap that highlights next R&D steps, estimated effort, and potential risks
Please be comfortable iterating in uncertainty, explaining your rationale to non-technical stakeholders, and working autonomously while keeping me in the loop through brief, regular updates. If tackling new software ideas from the ground up sounds exciting, let’s talk.