About Us:
Techblocks is a leading global digital product development firm. We unify strategy, design and technology with continuous growth-centric digital product engineering solutions for F500 companies and global brands, including Bell Telecom, Bausch Health (Previously Valeant Pharma), Honda Motors, AES Corp, Thomson Reuters Carswell, First American and Colliers International.
Our passion is empowering innovators and change-makers at every level of the product life cycle. We specialize in building customized business apps that allow organizations and enterprises to improve their efficiency, collaboration and user experience.

Experience & Track Record
  • 7–12+ years in software engineering, platform engineering, or DevSecOps — with meaningful time in a senior individual contributor or tech lead role.
  • Staff Engineer, Principal Engineer, or Senior Tech Lead background in a platform, DevOps, or developer tooling context. You’ve been the person other engineers come to with hard architecture questions.
  • Demonstrated experience designing and building CI/CD platforms or developer tooling for organizations with 200+ engineers. You’ve felt the scale problems firsthand.
  • Track record of producing high-quality technical artifacts: architecture docs, ADRs, RFCs, runbooks. You write clearly and your documentation actually gets read and used.
  • Experience influencing technical decisions across teams you don’t directly control. You know how to build consensus without having authority.
Technical Depth — You Should Be Strong Here
  • CI/CD platform design: deep expertise with at least one modern platform (GitHub Actions, GitLab CI, Tekton, ArgoCD, or Jenkins). You can design a multi-stage, multi-environment pipeline from scratch and explain the trade-offs.
  • Cloud-native infrastructure: hands-on Kubernetes and Terraform (or OpenTofu) experience. You’ve designed cluster architecture, managed Helm releases, and written non-trivial IaC. AWS, Azure, or GCP depth — at least one.
  • Security tooling integration: hands-on experience integrating SAST (Semgrep, Checkmarx, or Snyk Code), SCA (Snyk OSS, Mend, or Dependabot at scale), container scanning (Trivy, Grype, or Prisma Cloud), and secrets detection (Gitleaks, TruffleHog, or HashiCorp Vault) into real pipelines.
  • Policy-as-code: working experience with OPA/Rego or Kyverno for admission control and pipeline policy enforcement.
  • Artifact and dependency management: Artifactory, Nexus, or GitHub Packages at scale. You understand artifact promotion patterns, retention policies, and vulnerability triage workflows.
Technical Familiarity — Depth Expected to Grow in Role
  • Software supply chain security: working knowledge of SBOM formats (CycloneDX or SPDX), SLSA levels, and Sigstore/Cosign. You’ve either implemented these or done serious research into doing so.
  • Internal Developer Portals: hands-on Backstage experience (plugin development, software catalog design) or deep familiarity with Port or a comparable IDP. Opinions required.
  • AI coding tools architecture: you’ve evaluated or deployed GitHub Copilot, Cursor, or a similar tool in an enterprise context and have thought through data residency, IP risk, and acceptable-use controls.
  • DORA metrics instrumentation: you’ve set up measurement pipelines for deployment frequency, lead time, MTTR, and change failure rate and know where the data collection is messier than the metrics suggest.
  • Compliance framework translation: comfortable reading NIST SSDF, SOC 2 criteria, or CITADEL controls and mapping them to concrete technical implementation specs.
Nice to Have
  • Hands-on experience with agentic pipeline tooling or LLM-integrated developer workflows (LangChain, LangGraph, AutoGen, or MCP-based tooling).
  • Backstage plugin development or contributions to CNCF / OpenSSF projects.
  • Experience in a regulated industry: financial services, fintech, healthcare, or government/FedRAMP environments.
  • Familiarity with eBPF-based runtime security tools (Falco, Tetragon) or zero-trust network architecture in a Kubernetes context.
  • Previous experience as a developer advocate, platform product manager, or in a DevRel-adjacent role — you understand what makes platforms feel good to use, not just technically sound.