About the Role
We're looking for a Software Engineer who has spent their career building the tools, platforms, and automation that make teams across a company faster and more effective. This is not a feature-factory role and we want someone who looks at a recurring manual process, a clunky cross-team handoff, or a fragmented workflow anywhere in the company and instinctively starts designing a solution before being asked to. The core scope and primary lever of this role is horizontal tooling and workflow automation.
You'll partner with teams across functions to cocreate solutions to address friction points in day-to-day workflows and build the tooling, integrations, and automation that remove them. You operate with a strong bias toward leveraging AI/LLM capabilities as a core foundational lever to improve speed, quality, or operational throughput.
What You'll Do
- Own horizontal tooling and workflow automation as your primary mandate and build leverage across multiple teams and functions and balance going deep in a single domain.
- Design, build, and own tools and automation that reduce manual toil around highest-leverage opportunities around external customer and internal developer workflows.
- Identify gaps and inefficiencies proactively across teams - you don't wait for a ticket to tell you something's broken, and you're comfortable diagnosing a problem in a domain you don't own.
- Build and integrate AI-assisted workflows (e.g., LLM-powered triage, summarization, anomaly detection, auto-remediation) into existing tools and processes used by non-engineering and engineering teams alike.
- Take a request from this is a problem to here's a working solution with minimal hand-holding where you own the solutioning and design, not just the implementation.
- Partner with stakeholders across the company to understand their workflows (ticketing, approvals, reporting, handoffs, internal requests) and automate the repeatable parts.
- Build integrations with platforms like Zendesk/Pylon, CRM/HRIS/finance systems, internal services, and whatever tools a given team already relies on.
- Prioritize ruthlessly across competing requests from different teams, balancing quick wins against higher-effort, higher-impact builds.
- Write clean, maintainable, well-tested code and bring sound engineering judgment to tooling that other teams will depend on daily, often with minimal ongoing support from you.
- Document designs and decisions clearly enough that non-technical stakeholders and other engineers can both understand and build on your work.
What We're Looking For
- 5 - 8 years of professional software engineering experience, with a track record of building internal tools, workflow automation, or cross-functional platforms that served teams beyond engineering (not just product features).
- Strong hands-on coding ability in at least one modern language (Ruby, Python, Go, TypeScript/Node, or similar) and comfort working across the stack when needed.
- Demonstrated initiative like identifying a problem unprompted and driving it through design, build, and adoption.
- Mandatory Practical, hands-on experience using AI/LLM tools or APIs to build real solutions (not just casual usage) e.g., building agents, automations, or integrations on top of LLMs.
- Comfort working with ambiguity where you can take a loosely defined problem and shape it into a concrete technical plan.
- Comfort context-switching across different business domains and stakeholder groups, quickly getting up to speed on an unfamiliar team's workflow well enough to automate it.
- Solid understanding of CI/CD, observability, and infrastructure-adjacent workflows.
- Strong communication skills with ability to explain technical tradeoffs to both engineers and non-technical stakeholders.
Nice to Have
- Experience working with Jira, Pylon/ Zendesk (APIs, workflow automation, ticket triage/routing).
- Experience on an internal tools, DevX, or business systems team that served multiple stakeholder groups across a company.
- Experience building tools that reduce manual workload or turnaround time for non-engineering teams (Support, Ops, SRE).
- Experience working in a distributed/global engineering setup
