Azure Cloud R&D Specialist for Long-Term WFH Position
Budget: $2 – $8 USD
Title: Azure Cloud Research & POC Specialist (Long-term, Work From Home)
I'm a cloud consultant running multiple client projects, and I need a self-directed technical right hand to research solutions and build proofs of concept that I then take to delivery. This is varied R&D and problem-solving, not ticket-closing.
The single most important thing: you can take a vague problem and run with it on your own. I'll give you the goal and the context, not step-by-step instructions, and I need to trust it'll get done well without me checking in every hour. If you need constant direction, this isn't the role. If you love figuring out how things work and proving them out, you'll thrive here.
What you'll do:
Research how to solve specific Azure problems and write up clear findings
Build working proofs of concept in a sandbox (configs, scripts, sample dashboards)
Write step-by-step runbooks I can follow to deploy
Document everything cleanly, so I can pick it up without asking you questions
What I'm looking for:
Genuine self-direction. You research, decide, and deliver without hand-holding, and you know when to flag a blocker instead of spinning your wheels.
Solid Azure fundamentals, and the resourcefulness to teach yourself what you don't already know
General data literacy: comfortable with SQL, basic data modeling, how data pipelines (ETL/ELT) work, and how BI and reporting fit together. One of my gigs is data-heavy, so this matters even if your strength is elsewhere.
Strong technical writing. Your runbook should let someone else execute it cold.
Scripting in PowerShell and/or Python
Real working knowledge in ONE of these, plus eagerness to learn the other: (A) Power BI + Databricks + Python, or (B) Entra ID + Intune + Conditional Access
Bonus: Hands-on Databricks (Spark, notebooks, lakehouse), Azure certs (AZ-104, DP-203, SC-300, and similar), a GitHub or portfolio.
To apply: Start your message with the word "SANDBOX" so I know you read this. Then send me two things: (1) a specific example of a time you were handed an unfamiliar problem with little guidance and figured it out and delivered, and (2) any sample work, GitHub, certs, or a screenshot of something you've built.
I'm a cloud consultant running multiple client projects, and I need a self-directed technical right hand to research solutions and build proofs of concept that I then take to delivery. This is varied R&D and problem-solving, not ticket-closing.
The single most important thing: you can take a vague problem and run with it on your own. I'll give you the goal and the context, not step-by-step instructions, and I need to trust it'll get done well without me checking in every hour. If you need constant direction, this isn't the role. If you love figuring out how things work and proving them out, you'll thrive here.
What you'll do:
Research how to solve specific Azure problems and write up clear findings
Build working proofs of concept in a sandbox (configs, scripts, sample dashboards)
Write step-by-step runbooks I can follow to deploy
Document everything cleanly, so I can pick it up without asking you questions
What I'm looking for:
Genuine self-direction. You research, decide, and deliver without hand-holding, and you know when to flag a blocker instead of spinning your wheels.
Solid Azure fundamentals, and the resourcefulness to teach yourself what you don't already know
General data literacy: comfortable with SQL, basic data modeling, how data pipelines (ETL/ELT) work, and how BI and reporting fit together. One of my gigs is data-heavy, so this matters even if your strength is elsewhere.
Strong technical writing. Your runbook should let someone else execute it cold.
Scripting in PowerShell and/or Python
Real working knowledge in ONE of these, plus eagerness to learn the other: (A) Power BI + Databricks + Python, or (B) Entra ID + Intune + Conditional Access
Bonus: Hands-on Databricks (Spark, notebooks, lakehouse), Azure certs (AZ-104, DP-203, SC-300, and similar), a GitHub or portfolio.
To apply: Start your message with the word "SANDBOX" so I know you read this. Then send me two things: (1) a specific example of a time you were handed an unfamiliar problem with little guidance and figured it out and delivered, and (2) any sample work, GitHub, certs, or a screenshot of something you've built.