Iterable Software Engineer II at Iterable improves Scala, Bazel, and CI foundations to enhance developer workflows and build systems. The role involves owning moderate-complexity projects and contributing to shared engineering foundations.
Responsibilities
Improve the core developer workflow for compiling, testing, packaging, and validating changes
Contribute to shared engineering foundations including libraries, frameworks, and build patterns
Make CI faster and more reliable under production-scale usage
Own moderate-complexity projects independently
Partner with product engineering teams to improve developer experience
Shape AI-assisted and agentic engineering practices
Qualification
Experience with build systemsAbility to debug complex build
Required
We prioritize strong engineering fundamentals, practical systems thinking, and the ability to use modern AI tooling thoughtfully. You do not need to have used our exact stack, but you should be comfortable learning deeply, working in shared codebases, and building tools other engineers depend on.
Strong software engineering fundamentals in Scala, Java, Kotlin, or another production language; able to read, modify, test, and review service code in a large shared codebase.
Experience with build systems, dependency management, CI, or test infrastructure; familiarity with Bazel, SBT, Maven, Gradle, GitHub Actions, or similar systems is valuable.
Ability to debug complex build, test, and developer workflow failures and turn repeated issues into clear fixes, tooling, documentation, or automation.
Product-minded approach to developer experience; you care about usability, feedback loops, adoption, and whether platform changes actually make engineers faster and more confident.
Comfortable using AI tools such as Cursor, Claude, or similar systems for real engineering work, including codebase exploration, migration support, test generation, CI triage, and agent orchestration.
Good judgment about AI-assisted automation: able to break complex tasks into plans, prompts, verification steps, and review loops with appropriate human oversight and safety guardrails.
Clear communicator who can work with service teams, explain trade-offs, keep stakeholders informed, and make progress in ambiguous technical areas.
