Entry Level Remote Devops Jobs in Austin, TX (NOW HIRING)

About Curative
Curative is building the future of health insurance with a first-of-its-kind employer-based plan designed to remove financial barriers and make care truly accessible: one monthly premium with $0 copays and $0 deductibles*. Backed by our recent $150M in Series B funding and valuation at $1.275B, Curative is scaling rapidly and investing in AI-powered service, deeper member engagement, and a smart network designed for today's workforce.
Our north star guides everything we do: healthcare only works when people can actually use it. That belief drives every decision we make: from how we design our plan, support our members, to how we collaborate as a team.
If you want to do meaningful work with a team that moves fast, experiments boldly, and cares deeply, Curative is the place to do it. We're growing fast and looking for teammates who want to help transform health insurance for the better.
Summary
We are hiring a forward deployed software engineer to be the technical owner of our growth platform: the software that turns a stranger on curative.com into a bound group. That is one funnel, and you own all of it: the public marketing site and the CMS the marketing team publishes from, the forms and tracking that capture a lead, and the underwriting and quoting system that turns an employer's RFP into
a priced proposal and a closed deal. You will sit at the intersection of engineering, marketing, and sales. You will be embedded with the
people who use the software, not insulated from them. You will join the marketing team's planning sessions, hear which campaign is stalling and which page won't do what they need, and ship the fix the same week. You will do the same with the sales and underwriting teams on the other end of the funnel. And you will be the person watching the numbers: traffic, conversion by source and page, form completion, quote turnaround, win rate. Not vanity metrics, but the ones that say whether the funnel is actually getting wider. A big part of the job is building AI agents and automation that take work off people's plates: agents that read inbound RFPs and turn them into structured records, that draft and route content, that automate the manual campaign and sales-ops processes people run by hand today. You will be the single technical point of responsibility for these services. You will partner with marketing, sales, and product stakeholders to turn their workflows into shipped software, set the architectural direction, own production, and represent the platform in cross-team discussions.
How we build
At Curative, AI writes most of the code. Engineers direct it. We use agentic AI coding tools as the primary development surface. A senior engineer here routinely runs multiple agents in parallel: one implementing a feature, one resolving review comments, one chasing down a flaky test. The engineer's job is to set context, make the decisions the AI can't make, and keep the bar high on what ships. This is not a role for someone who wants to hand-roll every line. It is also not a role for someone who will accept whatever the AI produces. We are looking for the engineer in between: strong enough fundamentals to catch a wrong answer in a few seconds, disciplined enough to review every diff, and ambitious enough to drive several times the output of a traditional IC. On a surface where one half is the company's public front door and the other half decides what we charge an employer, that discipline matters more than usual. Strong systems and architecture thinking is important, as is product taste. This is a fully remote position.
What you'll own

• The top of the funnel. curative.com: a Next.js site on Vercel, statically generated from Strapi. Speed,
  SEO, accessibility, and uptime are yours.
• The bottom of the funnel. Our underwriting and group lifecycle platform, taking an inbound RFP through pricing to a closed deal. It is replacing Salesforce and MuleSoft.
• Ad targeting. Support marketing's paid campaigns: the audience data, tracking, and conversion signal the ad platforms run on, and whether what comes back can be trusted.
• AI leverage. The tooling, prompts, skills, and evals that let one engineer run a surface this size.
• Agents that do the work. We already run agents on the Claude API inside the underwriting platform.
• Extend them, and build new ones for RFP intake and the manual sales-ops grind.
• Conversion and experimentation. What we track, whether to trust it, what is running, and what it actually proved.
• Lead capture. Forms, validation, bot defense, routing, attribution. A lost or misattributed lead is a real dollar cost.
• Production. Infrastructure, deploys across Vercel and Kubernetes, observability, on-call, cost.
• Funnel metrics. Conversion by source, lead-to-RFP rate, time-to-quote, win and loss by segment and broker.
• Integrations. The connections to marketing and sales tooling this platform reads from and writes to.
• Stakeholders and roadmap. You are the engineer in the room with marketers, sales reps, and underwriters. You co-own the plan, push back when a request won't solve the real problem, and argue for what nobody has asked for yet.
• The domain. Within 90 days you understand the funnel well enough that every prompt you write is loaded with the right context.

What we're looking for
Foundational skills (non-negotiable)
You need these because you are the last line of defense on what the AI produces. The bar is not "can write it from scratch in an interview." The bar is "can read a 400-line AI-generated diff and spot the subtle bug in 90 seconds." On this surface, that bug is often a broken canonical tag, a tracking call that fires twice, or a rate that comes out quietly wrong.

• 5+ years shipping production software. Enough reps that you recognize bad code before you can articulate why.
• Real fluency in Python and TypeScript. Not "I can read it," but fluent. You will direct work in both every day: Next.js and React at the top of the funnel, FastAPI and SQLAlchemy at the bottom. You should be equally unbothered by a typed codebase and by an older JavaScript one.
• You have owned a real public-facing website. Server-side rendering and static generation, CDN and cache behavior, Core Web Vitals, SEO fundamentals, redirects done right, accessibility. You know why a marketing site is a different engineering problem than an internal app, and you have the scars to prove it.
• Strong SQL and relational database fundamentals. You can read a query plan, spot an N+1, know when a migration is unsafe at scale, and reason carefully about the joins and aggregations that decide what a number ends up being.
• Analytics and experimentation literacy. You have instrumented a funnel, trusted the data enough to make a call with it, and been burned by bad instrumentation at least once. You understand what an A/B test can and cannot tell you, and you don't ship a result off a week of noise.
• A correctness mindset. You have built systems where the output has to add up, and you instinctively reach for the checks, invariants, and audit trails that prove a number is right rather than just plausible. You are comfortable with the idea that "close enough" is not close enough.
• Systems thinking. Can sketch a service's architecture on a whiteboard, identify the failure modes, and reason about blast radius, including the kind that is visible to the public within seconds.
• Production cloud experience (AWS, GCP, or equivalent). You have been on-call for something real.
• Comfort working directly with non-technical stakeholders. You can run a 30-minute working session with a marketer or a sales rep, extract the real requirements, and leave them feeling heard, not bulldozed. You are as comfortable talking about campaign performance as about schema design.
• Product and design taste. You will ship things customers see. You should care how they look and read, and be able to hold a real conversation with a designer or brand lead.
• An interest in growth as a discipline. You don't need a marketing background, but you should be genuinely interested in the problem: how demand gets created, where it leaks, and the satisfaction of making a funnel measurably better.
• Sharp written communication. You will spend more time writing prompts, specs, and PR descriptions than writing code.

Note: Prior healthcare, insurance, or marketing-technology experience is not required. We care far more about your track record owning a customer-facing product surface and the systems behind it, in a role where the business could see the results. Any industry counts. What we do look for is real interest in the growth side of the problem.
AI-first working style (also non-negotiable)

• You already use Claude Code, Cursor, Codex, or equivalent as your primary development tool - not as a side autocomplete.
• You have opinions about how to structure prompts, when to split work into subagents, and how to keep AI output from drifting.
• You review every AI-generated diff. You do not merge on vibes.
• You treat the AI as a junior engineer with infinite throughput: high leverage, zero judgment, needs supervision.
• You enjoy building tooling that makes AI more effective on your codebase - skills, evals, fixtures, integrations.
• You see AI leverage as what makes it possible for one engineer to own a full product surface and stay close to users - not as a reason to stay heads-down in a terminal.

Strongly preferred

• A portfolio of AI-assisted work - skills you wrote, agents you built, automations you shipped.
• Experience being the single owner of a non-trivial service in production.
• Experience with a headless CMS, and specifically with supporting a non-engineering team that owns its own content model and ships on its own schedule.
• Growth or marketing engineering experience: landing pages, lifecycle and campaign tooling, paid acquisition and ad-platform data, attribution, CRM and marketing-automation integration, SEO or content platform work.
• Experience with document and file ingestion at scale: parsing messy real-world spreadsheets, PDFs, and email attachments into structured data.
• Experience with sales or CRM systems, especially replacing one.

Why this role
Healthcare is one of the highest-leverage places software can make a difference, and growth is where that leverage compounds: every employer we win is a few hundred more people who get care they can actually afford to use. We are a company where a single engineer can own the entire path from a first page view to a signed group. That is a scope most companies split across four teams and a marketing-
ops contractor. Your day might span unblocking a marketer on the one campaign page no existing component can
build, digging into why organic traffic to a page collection dropped, shipping the component that makes that page type self-serve from then on, building an agent that reads an inbound RFP into a structured quote request, and setting the technical strategy for your platform. If you have been looking for a role where you own the full loop, from problem discovery through production, where the work has a number
attached to it that you can watch move, and where AI-first isn't a buzzword but the actual way work gets done, this is it.
Perks & Benefits

• Curative Health Plan (100% employer-covered medical premiums for you and 50% coverage for dependents on the base plan.)
  
  • $0 copays and $0 deductibles (with completion of our Baseline Visit )
  • Preventive and primary care built in
  • Mental health support (Rula, Televero, Two Chairs, Recovery Unplugged)
  • One-on-one care navigation
  • Chronic condition programs (diabetes, weight, hypertension)
  • Maternity and family planning support
  • 24/7/365 Curative Telehealth
  • Pharmacy benefits
• Comprehensive dental and vision coverage
• Employer-provided life and disability coverage with additional supplemental options
• Flexible spending accounts
• Generous PTO policy plus 11 paid annual company holidays
• 401K for full-time employees
• Generous Up to 8-12 weeks paid parental leave, based on role eligibility.