/ TEAMS · Specialist engineering · TypeScript
Source engineers experienced in Strict typing, reliable backend and frontend contracts, and maintainable TypeScript architecture. for business-critical production systems, safe integrations and measurable technical ownership.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
Type-level API contracts
strict compiler settings
shared packages
runtime schema validation
monorepo boundaries
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid+ TypeScript Engineer
Available5+ years of experience · Slovakia
TypeScript Engineer with 5 years in production systems, focused on Type-level API contracts and strict compiler settings.
Languages: Slovak, English B2+
Senior TypeScript Engineer
Available7+ years of experience · Croatia
TypeScript Engineer with 7 years in production systems, focused on strict compiler settings and shared packages.
Languages: Croatian, English C1
Senior TypeScript Engineer
Inquire availability10+ years of experience · Croatia
TypeScript Engineer with 10 years in production systems, focused on shared packages and runtime schema validation.
Languages: Croatian, English B2+
Mid-level TypeScript Engineer
Inquire availability3+ years of experience · Croatia
TypeScript Engineer with 3 years in production systems, focused on runtime schema validation and monorepo boundaries.
Languages: Croatian, English B2+
/ Engineering teams
Onectus uses its active engineering network and regional recruiting partners to search against concrete systems, environments and responsibilities. We evaluate practical experience rather than treating a framework mention or certification as proof of delivery. Particular availability and engagement terms are confirmed after an enquiry. For this role, practical knowledge of Type-level API contracts, strict compiler settings, shared packages helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
TypeScript responsibilities include type-level api contracts, related strict compiler settings, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
TypeScript responsibilities include strict compiler settings, related shared packages, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
TypeScript responsibilities include shared packages, related runtime schema validation, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
TypeScript responsibilities include runtime schema validation, related monorepo boundaries, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
TypeScript responsibilities include monorepo boundaries, related esm interoperability, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
TypeScript responsibilities include esm interoperability, related type-level api contracts, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Introduce types into a legacy JavaScript codebase. Define constraints around type-level api contracts, map dependencies and test how the proposed implementation behaves under real operating conditions.
Eliminate unsafe API response assumptions. Define constraints around strict compiler settings, map dependencies and test how the proposed implementation behaves under real operating conditions.
Refactor shared packages without breaking clients. Define constraints around shared packages, map dependencies and test how the proposed implementation behaves under real operating conditions.
Improve build and dependency boundaries. Define constraints around runtime schema validation, map dependencies and test how the proposed implementation behaves under real operating conditions.
/ Practical evaluation
A senior engineering interview should surface directly relevant implementation details, debugging history and operational judgment.
Describe a production issue involving Type-level API contracts and what evidence led to a fix.
Which decisions around strict compiler settings and shared packages were you personally accountable for?
Describe a production issue involving shared packages and what evidence led to a fix.
Which decisions around runtime schema validation and monorepo boundaries were you personally accountable for?
/ Sourcing process
Define platform versions, deployment constraints, traffic patterns, required integrations and ownership.
Search the active network and partner channels for platform-specific engineering experience.
Discuss real systems, code or configuration decisions, troubleshooting and change control.
Confirm role boundaries, location or remote access, availability, security and interviews.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Tell us the relevant versions, operational environment and the responsibilities connected to Type-level API contracts. We qualify hands-on experience during each search.
These can be included when central to the project. We distinguish practical implementation work from general familiarity and ask about failure scenarios and testing.
We look at production decisions, trade-offs, incident diagnosis, code or infrastructure ownership and the ability to explain decisions without relying on a technology checklist.
Share your architecture, technical constraints, collaboration model and priorities. We can then discuss relevant sourcing channels, evaluation criteria and next steps.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
