Aurora is hiring a Non-tech (Pool) in CANDIDATES' POOL — Remote. The overview below is synthesized from the employer posting on jobs.lever.co: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
In case you are interested in applying to Aurora but do not see any relevant listed job postings on Work at Aurora at the moment you can apply here. Your application will be saved and you will be contacted in case there are any upcoming opportunities matching your profile.
In case you are interested in applying to Aurora but do not see any relevant listed job postings on Work at Aurora at the moment you can apply here. Your application will be saved and you will be contacted in case there are any upcoming opportunities matching your profile.
Join our dedicated team of blockchain industry professionals.
Please apply today — we’re standing by for your resume!
In applying at this job, I confirm and acknowledge that I read and understood the Privacy Notice published at https://auroralabs.dev/privacy.
Build a standout application
For the Non-tech (Pool) at Aurora, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.