Build and Release Engineer

• Perform release-candidate cuts, including version bookkeeping and branch management across a set of related repositories.
• Start, monitor, and troubleshoot the CI build/package/sign/publish chain.
• Investigate and resolve build and packaging failures, particularly around third-party dependency changes.
• Maintain and improve the installer bundle definition and its chained component packages.
• Drive measurable reductions in manual steps and lead time, and help implement dependency-aware, incremental build capability - potentially including an evaluation of mono repo consolidation as part of that roadmap.
• Clean up known process debt (e.g., generated files committed to repos, redundant legacy signing paths).
• Coordinate release timing and communication with adjacent teams and business stakeholders.

• Build Systems - Strong hands-on experience with multi-module Maven reactors; comfortable reasoning about module dependencies and build order.
• Mono Repo Experience - Direct experience building, migrating to, or maintaining a mono repo, including dependency graph management, incremental/selective build tooling (e.g., Bazel, Nx, Turborepo, or Maven multi-module strategies at scale), and versioning approaches that work across many co-located modules.
• CI/CD Pipelines - Solid experience with CI/CD tooling: hands-on with the current Jenkins setup (chained/downstream-triggered jobs, Groovy pipeline scripting) and with modern pipeline platforms such as GitHub Actions, which the team is moving toward for fully automated builds.
• Windows Installer Packaging - Experience building and maintaining chained/bundled Windows installer packages (MSI-based), or strong aptitude to ramp quickly.
• Code Signing - Familiarity with code-signing workflows (e.g., signtool, cloud-based signing services) and why signing sequence/immutability matters for release integrity.
• Version Control & Branching - Strong Git/GitHub skills, including release-branch workflows and multi-repo (or mono repo) coordination.
• Scripting - Proficiency in PowerShell, Groovy, or similar for build/release automation work.
• Troubleshooting - Demonstrated, methodical diagnosis of build and packaging failures, with a bias toward root cause over workaround.
• Communication - Clear, timely communication with developers, testers, and other stakeholders around release status and blockers.
• Process Improvement - Track record of reducing manual toil in engineering workflows, not just executing them.
• DORA Metrics - Familiarity with DORA metrics (deployment frequency, lead time for changes, change failure rate, time to restore) and using them to quantify and communicate delivery improvements.

3.63.6 out of 5 stars United States Remote $60 - $70 an hour - Contract