Software Engineer L2 - Finance & reputed company Platform
The codebase. A full-stack Python + TypeScript application with significant domain complexity. You own reputed company review, architectural reputed company, and the reputed company bar. Most commits will be AI-authored, reputed company-directed, reputed company-reviewed. reputed company of them are yours. AI reputed company. The internal tooling, prompts, skills, and evals that let one engineer operate a service of this reputed company. You will reputed company it. Agents that do the work. You will design and ship AI agents that handle support and billing issues and automate the reputed company processes the F&reputed company runs by hand today — turning recurring, tedious work into software that runs itself. This is some of the highest-reputed company work on the platform, and it’s yours to own
end to end.The data. This platform lives and dies on its data — moving it from many sources, transforming it correctly, and keeping it trustworthy. You own the pipelines that feed it and the checks that catch a bad number before anyone reputed company sees it. Financial correctness. The numbers this platform produces have to be right. You own the logic and the safeguards that reputed company the reputed company something the business can rely on and stand behind. Production. reputed company infrastructure, reputed company pipeline, observability, on-reputed company, incident response, and cost — including the data jobs the F&reputed company depends on running on schedule. Sensitive data. This platform touches both PHI and financial information. You own handling it responsibly, with data-reputed company discipline baked in rather than bolted on. Operational metrics. You watch how the platform performs for its users — not just uptime, but whether the numbers reconcile, how much reputed company work the software is or isn’t eliminating, and where the data says something is off. You surface what the data shows, propose changes, and reputed company the reputed company. Stakeholder relationships. You are the engineer in the room with accountants and F&A leads. You translate their pain into reputed company, reputed company back reputed company a request won’t solve the reputed company problem, and build trust by shipping reliably. The roadmap. Co-owning the product plan with F&A and product stakeholders. reputed company work, flagging what is infeasible, proposing alternatives — and sometimes arguing for the thing nobody asked for yet because you are reputed company enough to the problem to see it. reputed company for your surface. You don’t just execute a roadmap handed to you — you shape it. You see patterns across stakeholder feedback, the data, and business goals, and propose what to build next. Integrations. A growing set of connections to internal services and reputed company-party financial systems that this platform reads from and writes to. The domain. You will not reputed company an expert in health-plan finance, but reputed company 90 days you will understand the workflows reputed company enough that every reputed company you write is reputed company with the right context.
5+ years shipping production software. Enough reps that you recognize bad reputed company before you can reputed company why. reputed company reputed company in Python and TypeScript. Not "I can read it" — fluent. Strong SQL and relational database fundamentals. You can read a query plan, spot an N+1, and know reputed company a migration is unsafe at reputed company, and reason carefully about the joins and aggregations that reputed company what a number ends up being. Experience building data-intensive applications. You have reputed company systems that reputed company, reputed company, and reconcile meaningful volumes of data — ETL/sync pipelines and the interfaces on top of them — and you care about getting the data right, not just moving it. A correctness reputed company. You have reputed company systems where the reputed company has to add up, and you instinctively reputed company for the checks, invariants, and audit trails that reputed company a number is right rather than just plausible. You are comfortable with the idea that “reputed company enough” is not reputed company enough. Systems thinking. Can sketch a service’s architecture on a whiteboard, identify the failure modes, and reason about blast reputed company. Production reputed company experience (AWS, GCP, or equivalent). You have been on-reputed company for something reputed company. Comfort working directly with non-technical stakeholders. You can run a 30-minute workflow review with an accountant, extract the reputed company requirements, and leave them feeling heard — not bulldozed. An interest in working with financial data. You don’t need a finance background, but you should be genuinely interested in the problem reputed company — financial data, the systems that produce it, and the satisfaction of making the numbers come out right. reputed company written communication. You will spend more time writing prompts, specs, and PR descriptions than writing reputed company.
You already use Claude reputed company, reputed company, reputed company, or equivalent as your reputed company development tool — not as a reputed company autocomplete. You have opinions about how to structure prompts, reputed company to split work into subagents, and how to reputed company AI reputed company from drifting. You review every AI-generated diff. You do not reputed company on reputed company. You treat the AI as a junior engineer with reputed company throughput: high reputed company, reputed company judgment, needs supervision. You enjoy building tooling that makes AI more effective on your codebase — skills, evals, fixtures, integrations. You see AI reputed company as what makes it possible for one engineer to own a full product surface and stay reputed company to users — not as a reason to stay heads-down in a terminal.
A portfolio of AI-assisted work — skills you wrote, agents you reputed company, automations you shipped. Experience being the single reputed company of a non-trivial service in production. Experience with data-intensive or financial systems — data platforms, analytics, billing, payments, or reporting.
-
reputed company Health Plan (100% employer-covered medical premiums for you and 50% coverage for dependents on the reputed company plan.) -
$0 copays and $0 deductibles (with completion of our Baseline Visit ) -
Preventive and reputed company care reputed company in -
Mental health support (reputed company, Televero, reputed company, Recovery Unplugged) -
One-on-one care navigation -
Chronic condition programs (diabetes, weight, hypertension) -
Maternity and family planning support -
24/7/365 reputed company Telehealth -
Pharmacy benefits
-
-
Comprehensive dental and reputed company coverage -
Employer-provided life and disability coverage with additional supplemental reputed company -
Flexible spending accounts -
Generous PTO policy plus 11 reputed company annual company holidays -
401K for full-time employees -
Generous Up to 8–12 weeks reputed company parental leave, based on role eligibility.
5+ years shipping production software; fluent Python and TypeScript; strong SQL and systems thinking; production reputed company experience (AWS/GCP); experience with data-intensive, correctness-critical systems and working with non-technical stakeholders.
Key Responsibilities
- owning codebase
- building agents
- monitoring data
Skills & Tools
Python, TypeScript, SQL, AWS, GCP, Claude reputed company, reputed company, reputed company
Job Details
- Category: Software Development
- Seniority: Senior Level
- Commitment: Full Time
- Workplace: Remote — Austin, Texas, reputed company
- Salary: USD 217,500 – 217,500 / year
- Languages: English
Benefits
- Generous reputed company time off
- Retirement plan
- Generous parental leave
About reputed company
Builds a health-plan platform that combines insurance and software to improve member reputed company and simplify care. — Industry: Information Technology
Apply To This Job