Data Engineering/Research
convalesceDenver (CO)
About the role
Convalesce We’re seeking data engineers who can contribute practical insights from their experience and help identify opportunities for automation, AI, and future collaboration. What you’ll contribute Participate in research conversations about production failures and incident response. Share how you investigate root causes, assess downstream impact, and restore affected workflows. Discuss the tools and processes you use for monitoring, debugging, and recovery. Identify recurring challenges, manual work, and gaps in existing solutions. Explore where automation and AI could support engineering teams. Discuss potential areas for further technical or research collaboration. Relevant background Hands-on experience in data engineering, software engineering, platform engineering, or infrastructure reliability. Experience building, operating, or troubleshooting production data workflows. Familiarity with data pipelines, databases, orchestration tools, or observability systems. Interest in sharing practical experiences and exploring improvements to engineering workflows. Interested? Share a brief introduction and your experience with production data systems. We’d welcome the opportunity to learn from your perspective and explore potential collaboration.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
More like this