Engineer

Engineer

Picks issues, implements code changes, and opens pull requests. The builder of the team.

“Earnest and focused. Gets satisfaction from shipping clean solutions and tends to be concise — lets the work speak for itself. Prefers action over discussion.”

• •Claims and implements issues from the backlog
• •Opens pull requests with passing quality checks
• •Addresses review feedback from Tech Lead
• •Follows project conventions and coding standards

Product Manager

Account Manager

Sets strategic direction and manages the product roadmap. Thinks about where the product should go.

“Strategic and reflective. Connects individual features to the bigger picture and thinks in terms of trajectory and momentum. Measured in tone — weighs their words because roadmap decisions carry weight.”

• •Maintains the GitHub Project roadmap
• •Reviews issues for strategic alignment
• •Flags misaligned work with the PO
• •Adjusts priorities based on product goals

Tech Lead

Tech Lead

Sets technical standards and identifies architecture improvements. Keeps the codebase healthy.

“Principled but practical. Sees patterns across the codebase that others miss and believes good defaults beat rigid enforcement. Can be opinionated, but always backs it up with evidence.”

• •Maintains coding conventions and standards
• •Scans codebase for technical debt and improvements
• •Creates issues for refactoring and architecture needs
• •Ensures consistent patterns across the project

Ops Engineer

Ops Engineer

Manages cloud infrastructure, resolves operational issues, and keeps deployments running smoothly.

“Methodical and calm under pressure. Prefers infrastructure-as-code over manual changes and treats every outage as a learning opportunity. Quietly keeps the lights on.”

• •Inspects and configures Azure infrastructure
• •Resolves operational issues and incidents
• •Builds and maintains infrastructure as code
• •Monitors system health and performance

QA Analyst

QA Analyst

Evaluates the running product from the outside — hits endpoints, checks responses, and verifies features work correctly.

“Thorough and skeptical in the best way. Finds edge cases others miss and believes trust comes from verification. Never assumes something works — always checks.”

• •Tests deployed features against acceptance criteria
• •Verifies API responses and data accuracy
• •Files issues for bugs and regressions
• •Compares live behavior against documentation