Technical capability aligned to the environment and work.

Representative titles

• ML engineer
• Applied AI engineer
• Automation engineer
• AI platform engineer

Environment signals we check

• Existing model and tooling choices
• Data sensitivity and access constraints
• Whether the role is prototyping or operating production workloads

What we assess beyond the title

• How they evaluate model or application quality, not just build it
• Integration experience with real systems and permission boundaries
• Understanding of the data context the solution depends on
• Deployment, monitoring, and what they do when output quality drifts
• Judgement about responsible use and where a human must stay in the loop

Representative titles

• Frontend engineer
• Backend engineer
• Full-stack engineer
• Mobile engineer
• Platform engineer
• API engineer

Environment signals we check

• Stack, codebase age, and test coverage reality
• Team structure and review culture
• Delivery stage: greenfield, scaling, or modernization

What we assess beyond the title

• Product context — whether they reason about users, not only tickets
• Architecture judgement appropriate to the system's size and stage
• Quality and maintainability habits under real deadline pressure
• Collaboration in code review and cross-functional work
• Delivery practices: testing, release, and ownership after shipping

Representative titles

• Data engineer
• Analytics engineer
• BI developer
• Data analyst
• Data platform engineer

Environment signals we check

• Warehouse or lakehouse platform and transformation tooling
• Governance and access requirements
• Whether the role serves analytics, product, or AI consumers

What we assess beyond the title

• Pipeline design and how they handle schema change and backfills
• Modeling approach and whether definitions are testable
• Data quality and governance instincts
• Understanding of who consumes the output and for what decision
• Operational reliability — what happens when a nightly job fails

Representative titles

• Cloud engineer
• DevOps engineer
• Site reliability engineer
• Platform engineer

Environment signals we check

• Cloud provider, scale, and compliance context
• On-call expectations and incident maturity
• Whether the role is building a platform or operating one

What we assess beyond the title

• Infrastructure design and infrastructure-as-code discipline
• CI/CD practice and how they make releases reversible
• Observability: what they instrument and why
• Security context and least-privilege habits
• Reliability and cost trade-offs they have actually had to make

Representative titles

• QA engineer
• SDET
• Automation engineer
• Performance test engineer

Environment signals we check

• Release cadence and current confidence level
• Existing suite health and flakiness
• Regulatory or safety-driven testing requirements

What we assess beyond the title

• Risk-based thinking — what they choose not to test, and why
• Automation strategy at the appropriate layer
• Integration with the delivery pipeline rather than alongside it
• How they build release confidence a team actually trusts

Representative titles

• Technical product manager
• Product manager
• Scrum or delivery lead
• Program manager

Environment signals we check

• Decision-making structure and stakeholder complexity
• Delivery methodology in practice, not on paper
• Whether the role is discovery-led or execution-led

What we assess beyond the title

• Problem framing — whether they can separate the request from the need
• Stakeholder alignment across business and engineering
• Technical fluency sufficient to challenge an estimate constructively
• Delivery visibility: how they make progress and risk legible