Grove Collaborative
Senior Software Engineer I, Integrations and Internal Systems
Remote
Get past the screening software and onto a recruiter's desk
hirly rewrites your resume for this job — matching the keywords and skills in the posting, moving your most relevant experience to the top, and writing a cover letter to fit. About 30 seconds.
- Keywords matched to this posting
- Fit score before you apply
- Cover letter included
Matched against 2.3M live jobs from 200,000+ employers in 200+ countries.
Tailor my resume for this job →hirly's read of this role
- Role family
- Engineering
- Seniority
- Senior
- Work mode
- Remote-friendly
- First seen by hirly
- 1 Oct 2026
Derived automatically from the posting. Upload your resume above to see how the role scores against it.
the posting
Grove Collaborative is a sustainability-focused consumer products company creating household and personal care essentials that are effective, beautifully designed, and healthier for people and the planet. We are a certified B Corp, plastic-neutral, and on a mission to transform the CPG industry for good.
Grove Collaborative is a sustainability-focused consumer products company creating household and personal care essentials that are effective, beautifully designed, and healthier for people and the planet. We are a certified B Corp, plastic-neutral, and on a mission to transform the CPG industry for good.
About the Opportunity
This isn't a role for someone waiting to be told what to build. We want a true self-starter: endlessly curious, genuinely ambitious, and humble enough to be trusted with real influence.
This person will own our internal systems integrations and the delivery of our MCP layer. You'll keep the lights on while identifying incremental improvements, and build the layer that enables the business to become builders and lets agents do real work safely. You'll spend time in both worlds, often in the same week, sometimes in the same day.
You're an enabler with a high level of ownership, ready to flex whatever muscle the day calls for. An integration breaks — you fix it. The business needs new functionality — you build it. Our MCP layer needs a new connection — you stand it up.
You think beyond the fix. We don't just want someone who keeps integrations running — we want someone who's constantly looking for the opportunity to simplify and consolidate them. You know the difference between patching something and rebuilding it onto better infrastructure, and you have a bias toward leaving every system you touch better than you found it, not just functional.
AI isn't an add-on here — it's how the work gets done. This is an AI-enabled role in an AI-enabled organization. You'll use AI tooling to write code, maintain the environment, and move faster across a wider surface area than one engineer could otherwise cover. It's not a tool you reach for occasionally; it's part of your everyday process.
We're just getting started building the infrastructure that lets everyone in the business become a builder. There's no finished playbook. Our MCP layer doesn't have an established pattern for security, access control, or agent tooling yet — you'll help write it, in partnership with the people who own the roadmap.
What You’ll Own
Back-office integrations — Maintain and enhance the integrations connecting NetSuite, HighJump, our data warehouse, and adjacent systems. Rebuild individual flows onto better infrastructure when it makes sense to, and know the difference between a fix and a rebuild. Go beyond maintenance to actively look for ways to simplify and consolidate our integration landscape — fewer moving parts, less duplicated logic, systems that are easier for the next person to reason about.
Grove Brain / internal MCP layer — Build Grove Brain out from its current early stage into a durable platform other teams build on. Design and implement the connectors and tools that let agents act on real Grove systems.
Security, access, and governance for agents — Help define and build how agents authenticate, what they're allowed to touch, and how that's audited, in partnership with the teams who own security and infrastructure rather than setting policy solo.
Hands-on enablement — Be the person a team calls when they're stuck mid-build on an integration or an agent problem, whether that's a connector, a permissions question, or a "we don't know what's possible yet" question.
Judgment calls — Decide when a systems problem is yours to solve and when it's actually a process problem that belongs to the business.
AI-assisted development — Use AI tooling aggressively as a force multiplier, and hold the line on quality while you do it. You should be moving noticeably faster than an engineer working without these tools, without your standards slipping. More on this below.
Craft, performance, and quality — Own performance, stability and maintainability in the code you ship, at the scale Grove actually runs at.
About You
5+ years building and operating building and maintaining production system integrations — the kind that move data between platforms like NetSuite, HighJump, or similar ERP/WMS systems.
Strong software engineering fundamentals: you can design a pipeline, debug it under pressure, and know the difference between a quick fix and a real one.
Genuine hands-on experience with AI tools and, ideally, agent frameworks or MCP — not just familiarity, but a track record of building with them.
Comfortable operating with a rough direction instead of a finished spec, and you make real progress anyway.
A builder's mindset — you'd rather stand something up yourself than write a design doc for someone else to build.
Enough security instinct to ask the right questions about what an agent should and shouldn't be able to touch, even when you're not the final decision-maker on policy.
You're honest about what you don't know. You can say "I haven't worked with that" without flinching, and you don't paper over the gap with a confident guess.
Background with Airflow, Airbyte, or similar data-pipeline infrastructure
New technology doesn’t scare you. You’ve been dropped into an unfamiliar framework, language, or platform and gotten productive fast, and you can point to a time you did it. You evaluate new tools on the merits instead of defaulting to what you already know or chasing whatever is new.
You’re honest about what you don’t know. You can say “I haven’t worked with that” without flinching, and you don’t paper over the gap with a confident guess.
You’ve taken something vague, made it concrete, brought other people along, and shipped it.
You work well with others. You give direct feedback kindly, you take it well, and people want you on their project.
A real sense of ownership and pride in the experiences you ship and the code you leave behind.
You write things down, and people understand them. You can a non-technical person through a technical tradeoff without hiding behind jargon.
Genuine enthusiasm for Grove’s mission and sustainability values, not just the tech stack.
How We Work Together
This is a high trust environment. You’ll get real scope and real decisions early, and nobody is going to look over your shoulder while you do the work. Trust runs both directions: we’ll be straight with you about the business, the tradeoffs, and the parts of the codebase we aren’t proud of, and we expect that same candor back.
We value psychological safety first and foremost. It’s the precondition for everything else on this list. The teams that solve genuinely hard problems are the ones where people feel safe saying “I don’t understand this yet.”
“I haven’t worked with that” is a complete answer here. We have deep respect for an engineer who names the edge of their own knowledge instead of bluffing past it. We don’t need you to know everything. We need you to be honest about where your expertise begins and ends — and that honesty is worth more to us than a confident guess, in an interview and on the job.
How We think About AI
We’re serious about this, so we’d rather be direct than let you find out later.
AI tooling is part of how this team works every day, not an experiment on the side. We want someone who genuinely enjoys these tools and keeps getting better with them.
Nobody here has AI figured out, and we’re skeptical of anyone who says they do. The tooling changes month to month. We are all working it out together, in the open. We’d rather hire someone actively learning than someone with a methodology to evangelize.
We’re looking for someone whose judgment stays their own. You should be able to read what a model produced, disagree with it, and explain why — about architecture, about corre
Similar jobs
- Software Engineer III - Full stack Developer - Python/ReactJPMorganChase · Hyderabad, Telangana, IndiaFirst seen today
- Custom Software EngineerAccenture · IndiaFirst seen today
- Custom Software EngineerAccenture · IndiaFirst seen today
- (Ind) Staff, Software EngineerWM Global Technology Services India · IndiaFirst seen today
- Software Engineer II, Front End, Google CloudGoogle · Pune, Maharashtra, IndiaFirst seen today
Browse similar roles
Want this one?
Upload your resume and hirly rewrites it for this job and writes the cover letter — in about thirty seconds, before you sign up.
Tailor my resume for this job