Callibrity

Backend Engineer

• As a Software Developer, you are a leader by example, you are a subject matter expert, and you help lead strategic technical direction.
• You will get to interact with key client stakeholders on a regular basis and use your experience to prove business ROI through innovative greenfield technology solutions.
• Software Developers typically have longer tenures and higher retention rates with Callibrity than other companies because the work is challenging and rewarding, we have a strong engineering culture, and we invest in the best people.
• Callibrity Software Developers can solve a broad subset of problems with a broader set of solutions by choosing the right language, framework, and tool for a problem.
• Work directly with key stakeholders at our clients to accomplish shared goals.
• Communicate complex ideas effectively, both verbally and in writing.
• Proactively identify opportunities, challenges, and issues and recommend a solution.
• Demonstrate mastery of software development best practices (Agile, DevOps, Test Automation, CI/CD, TDD).
• Stay ahead of the curve by exploring new technologies including AI, Machine Learning, Cloud, and IoT.
• Thrive in an environment where there is close interaction among different roles and teams.
• Are admired by the client as someone they can count on, regardless of title or seniority.

Software Engineer, Ruby

Platform Engineer

• Run hands-on technical discovery across assigned domains — typically cost governance, observability, platform deployment, and management tooling — using Azure Resource Graph, Azure Policy compliance, Microsoft Cost Management, Defender for Cloud, Microsoft Entra reporting, Azure Monitor, and Application Insights.
• Review the client’s existing Terraform footprint and common Azure DevOps deployment paths. Identify standardization opportunities, configuration drift risks, and the foundational moves required to mature toward a code-driven, team-owned platform.
• Assess tagging standards and enforcement, automated alerts and reporting, and Reserved Instance and Savings Plan utilization. Propose practical cost-governance improvements that hold up as Azure adoption grows.
• Evaluate the centralized logging, monitoring, and alerting strategy, including SIEM integration patterns, audit log retention posture, and the application telemetry surface exposed through Azure Monitor and Application Insights.
• Draft the sections of the report tied to your streams of work — findings, recommendations, effort indications, and success-criteria tagging — to a quality bar that lets the Principal Consultant integrate them into the broader narrative with minimal rework.
• Produce the tangible artifacts that Callibrity is known for during assessment engagements: working dashboards, reusable IaC modules, governance-as-code samples, or developer-experience prototypes where they accelerate the client’s ability to act on the recommendations.
• Participate in stakeholder interviews and on-site working sessions. Bring engineering credibility to the conversation, not just note-taking.

Senior Cloud and Platform Engineer

Cloud Engineer

• Lead the discovery effort across all nine assessment domains, including stakeholder interviews with technical and business leaders and hands-on review of the client’s Azure tenant, network topology, identity configuration, IaC repositories, deployment paths, cost reporting, and security posture.
• Own the architectural point of view. Assess the current state against Azure Landing Zone guidance and the Well-Architected Framework, identify the foundational moves that unlock everything else, and decide where the report needs to push back versus where it should affirm the client’s existing direction.
• Author the prioritized recommendations and the phased roadmap. Tag each recommendation against the success criteria the client cares about (security, cost, resiliency, auditability, deployment ease, reduction of single-person dependencies), sequence the work with explicit dependency mapping, and make the sequencing logic legible to non-technical readers.
• Direct the Senior Cloud and Platform Engineer on the engagement. Frame the analysis, divide the work, review the output, and make sure the technical depth in the report holds up under scrutiny from the client’s engineers.
• Run the cadence of the engagement with the client: kickoff facilitation, weekly written status, the mid-Phase-2 draft-review working session, and the final presentation to leadership.
• Write the executive narrative. The leadership-ready summary is part of your deliverable, not a hand-off to someone else, and it has to read well to an audience outside technical engineering.

Software Engineer, Ruby

Senior Cloud and Platform Engineer

Azure Cloud Architect