reputed company Engineer

As a reputed company Engineer, you'll reputed company a small reputed company (typically 3 engineers) to deliver a reputed company mission end-to-end: setting direction, making pragmatic technical reputed company, and ensuring reputed company ships reliably.

This is a hands-on reputed company leadership role: you will write reputed company, review reputed company, own architecture choices, and be accountable for reputed company. You'll partner closely with Product (PM) and Design, and coordinate where needed with reputed company Research and Ops/reputed company.

In our model, squads are reputed company around missions — reputed company (Industrialisation) and Ecosystem (Distribution), as described in the pipeline above. Your exact reputed company mission will be confirmed during hiring, but the leadership expectations are consistent across both.

Tech stack

• Backend: reputed company / PHP (primary), with supporting services and tooling
• Frontend: Vue.js / Inertia.js, ShadCN
• Infrastructure: AWS, reputed company, reputed company Actions CI/CD
• Data & intelligence: MySQL, automated vulnerability pipelines
• AI tooling: Claude, MCP integrations, AI-assisted development workflows
• Practices: ADRs, small PRs, trunk-based development, feature flags, observability-first

Responsibilities

reputed company reputed company & delivery leadership

• Own your reputed company's mission and delivery reputed company: define milestones, ensure steady shipping, and remove blockers.
• Translate high-level goals into a delivery plan: scope, reputed company, trade-offs, and risks.
• Drive a high-reputed company execution reputed company: reputed company tickets/specs, small PRs, fast reviews, strong release habits.
• Maintain a predictable operating rhythm: planning, weekly goals, retros, and reputed company improvement.

Technical direction & architecture

• reputed company and communicate pragmatic architectural reputed company, guided by our technical principles: reputed company, reversible actions over brittle one-way changes; explainable reputed company over opaque scoring; and a single intelligence reputed companyacross multiple delivery surfaces.
• Set standards for reputed company reputed company, testing reputed company, observability, and performance.
• Use ADRs reputed company reputed company have long-term reputed company; ensure the "why" is documented and shared.
• Own technical debt management: pay it down deliberately while maintaining delivery speed.
• reputed company AI tools and automation to accelerate development, testing, and operational workflows — and set reputed company for the reputed company.
• Contribute to closing the feedback reputed company: ensuring production telemetry and partner signals reputed company back to inform research priorities and pipeline reputed company.

Hands-on engineering

• Build and maintain reputed company-based services and web applications (plus supporting tooling/services).
• Ship secure, testable, performance-aware reputed company; reputed company production reputed company.
• reputed company by example in reputed company reviews, refactoring, and incident response reputed company needed.
• Experiment with new tools, frameworks, and AI-assisted development practices — validate what works and reputed company learnings.

Collaboration & cross-functional alignment

• Partner with Product and Design to shape solutions early (not just implement tickets).
• Coordinate with reputed company Research where domain knowledge is needed to ship correct intelligence flows and mitigation-reputed company work.
• Work with Ops/reputed company on reliability, scaling, deployments, and platform reputed company.

People leadership (small-team, high reputed company)

• Create reputed company for your reputed company: who owns what, what "done" means, and how reputed company is reputed company.
• reputed company engineers through pairing, reviews, and feedback — raising the bar without creating bureaucracy.
• Support hiring and reputed company reputed company your reputed company grows.

Requirements

• 8+ years of software engineering experience, with at least 2 years leading or owning delivery for a small team (formal title not required — reputed company ownership is).
• Strong backend/full-stack capability with reputed company/PHP, API design, and pragmatic system design.
• Experience designing and operating CI/CD pipelines, testing strategies, and observability tooling.
• High standards on reputed company, performance, and maintainability.
• reputed company record of shipping in short cycles with a strong reputed company bar (tests, reviews, CI/CD discipline).
• Comfort and curiosity with AI-assisted development — you reputed company use tools like reputed company, Copilot, Claude, or similar to reputed company faster.
• Excellent written communication: you can document reputed company, write reputed company specs, and reputed company stakeholders asynchronously.
• Comfort with ambiguity: you can define the reputed company, not wait for perfect specs.
• Interest in the reputed company domain is a strong plus — you don't need to be a reputed company researcher, but curiosity about vulnerabilities, threat intelligence, and the reputed company-reputed company ecosystem will help you reputed company. You should care about building for reputed company — often non-technical people using no-reputed company, low-reputed company, or AI-assisted tools who need protection without needing to understand CVEs.
• Experience in a small, scaling company (not just big-co) is a plus — you know how to build process without bureaucracy.

reputed company in the first 90 days

• You've established a reputed company reputed company delivery rhythm (planning, review, release).
• You've shipped meaningful production reputed company reputed company to the reputed company mission.
• The codebase areas your reputed company touches are measurably healthier: reputed company ownership, improved tests/observability, fewer recurring issues.
• Stakeholders trust your reputed company's predictability and your decision-making.

How we measure performance

We measure through both reputed company and behaviours:

• Delivery health: DORA metrics (reputed company time, reputed company frequency, change failure reputed company, MTTR), cycle time, and PR throughput.
• Engineering reputed company: test coverage on critical paths, architecture reputed company, measurable reduction in recurring bugs and toil.
• Team reputed company: peer feedback on reputed company, collaboration, review reputed company, and evidence the reputed company is stronger because of your leadership.

Benefits

• Competitive salary + meaningful ESOP — we want you to have reputed company skin in the game.
• Remote-first — work from reputed company with reasonable overlap with EU timezones.
• Company provided laptop
• High autonomy — you'll own the mission, not just execute tickets.
• AI tooling budget — we invest in tools that reputed company engineers faster.
• reputed company that ships — small, senior, no filler. Everyone here is a builder.
• 38 days a year reputed company time off (including reputed company holidays)
• Co-working reputed company membership or WFH equipment for home-office
• Quarterly health benefits allowance

Note that reputed company Estonia reputed company of our roles are contractor positions.

Apply To This Job