Senior Full Stack - vacante remota

La empresa Toggl busca cubrir el puesto de Senior Full Stack: es un puesto senior, así que la empresa espera que las decisiones las tome usted. La vacante pertenece al área de IT y programación y es totalmente remota. La empresa no pone ninguna restricción sobre el lugar de residencia, así que usted puede postular desde donde vive.

Las herramientas principales que nombra el anuncio son: React, TypeScript, Go, SQL. El CV debería mostrar ejemplos concretos justo de esas capacidades.

La empresa publicó la remuneración: €83k al año. El anuncio nombra la zona horaria UTC-4, así que el horario hay que acordarlo con el suyo.

Esta vacante pasó una revisión automática: los anuncios que exigen un permiso de trabajo extranjero, patrocinio de visa, una nacionalidad concreta o residencia en un país determinado no entran en la lista.

Headquarters: Tallinn, Estonia

URL: https://toggl.com/jobs/

We are looking for a Senior Full Stack Engineer to join one of our Product Tribes, the cross-functional units that own the end-to-end experience for a specific Toggl user role. You'll join the Tribe building for managers, the people who plan work, protect margins, and keep projects on time and on budget.

You own significant parts of that experience end-to-end, working hands-on with product and design to ship work that matters. You'll do this as we build and launch Toggl 2.0, our consolidated planning, time tracking, and time intelligence product.

The salary for this position is  €83,000 annually.

You can work from anywhere in the world  as long as your main location is between UTC-4 and UTC+4.

 

The Role

As a Senior Full Stack Engineer, you own meaningful parts of the product end-to-end, from the data model and the API to the interface someone actually clicks: the technical approach, the quality of what ships, and whether it actually works for the people using it. You are accountable not for tickets closed, but for clarity, craft, and outcomes.

You'll work in the Tribe serving managers, across planning and capacity management, dashboards, and billable work. This is some of the most data-dense, interaction-heavy surface area in the product: schedules and capacity views, reports, and visualizations that have to stay fast and readable at real customer scale. The interesting problems live on both sides of the API here - the query behind a capacity view matters as much as how that view renders. You'll build with React and TypeScript on the frontend and our backend services (mostly Golang) and data layer (Postgres) behind them, alongside a product manager, a designer, and engineers who are used to owning their work and pushing back when something isn't right. In a tribe of 5 other engineers, your impact and visibility are high.

Our team meetings are scheduled between 11:00 and 16:00 UTC. Your availability and commitment to participate in these sessions are essential for effective collaboration and team alignment.

Your main responsibilities will be:

Ownership and delivery

* Take projects from problem to production. Own the technical approach for major features front to back, break the work down sensibly, sequence it, and ship in slices rather than one big drop.

* Make the technical calls in your area. Choose between options, name the tradeoffs, and decide without waiting for permission or escalating routine judgment.

* Keep your work visible without being chased. Flag risks and slips early, keep the Tribe in the loop, and unblock yourself.

Craft and quality across the stack

* Build interfaces people trust with dense, real-world data. Planning views, dashboards, and reports that stay fast, accessible, and readable when the dataset gets ugly.

* Design the data and API layer those views depend on. Model it so the feature you're building now doesn't make the next three harder.

* Own performance as a feature, end to end. Profile, measure, and fix the slow query and the slow render instead of hoping the data stays small.

* Write code others can work in. Sensible components and services, real test coverage where it earns its keep, and a codebase that's easier to change after you touch it.

Working with product and design

* Shape solutions, don't just implement them. Push on the problem, question requirements that don't hold up, and propose simpler paths when you see one.

* Partner closely with design. Prototype early, spot the edge cases in a flow before it's built, and hold the bar on UX quality with your designer rather than after handoff.

* Stay close to users and evidence. Join user tests, read the feedback, look at the data, and let it change what you build.

Raising the bar

* Review code with intent. Give precise, actionable feedback that makes the change and the person better.

* Mentor and interview. Help other engineers grow, and help us hire well.

* Improve things across team boundaries. Spot shared components and duplicated work between Tribes, and raise it before we build the same thing twice.

AI as core leverage

* Use AI tools extensively in your daily work for exploration, prototyping, code generation and review, debugging, research, and writing. AI fluency is not optional. It's part of how you increase your speed, depth, and impact - and you're expected to help the rest of the Tribe get better at it too.

 

About You

You will thrive in this role if you:

* Have significant experience building and shipping production web applications end to end, and can lead major projects rather than just contribute to them.

* Are genuinely comfortable on both sides of the stack. You're deep on one side and properly capable on the other, not someone who hands off at the API boundary.

* Have deep, practical knowledge of  JavaScript, TypeScript, React, and modern CSS  - including state management and side-effect handling in large applications.

* Are solid on backend fundamentals: at least one backend language you know well, API design, relational data modelling, and enough instinct for query performance to spot the problem before production does.  Prior Golang experience is not mandatory but you have to be willing to adopt it and become comfortable with it fast.

* Hold an extremely high bar for quality. You know what great looks like, you notice the details others miss, and you don't ship work you wouldn't put your name on.

* Have a knack for data-heavy product surfaces - performance, readability, and the principles behind a chart that actually communicates something.

* Care about the user's problem, not just the ticket. You start from what someone is trying to get done and work back to the implementation.

* Own outcomes, not output. You follow your work into production, watch how it behaves, and fix what needs fixing.

* Thrive in ambiguity and move fast. You make confident decisions with incomplete information, adapt when things change, and course-correct without drama.

* Are hands-on with AI tools. You actively use AI as a core part of how you build, not a side experiment, and you have opinions about where it helps and where it doesn't.

* Don't need to be managed. You set your own direction, keep people in the loop, and ask for help when it matters.

* Have excellent written and verbal English communication skills. You write clearly, explain technical tradeoffs to non-engineers without jargon, and default to async communication that others can follow.

* Are eager to contribute to the engineering team's growth - code review, mentoring, and interviewing included.

* Value transparency, ownership, and speed over perfection. You ship, learn, and improve rather than waiting for the perfect plan.

* Nice to have:

* Experience with TanStack is a bonus, and so is a real understanding of frontend caching and eventual consistency, we'd love to hire someone who's dealt with that tradeoff directly.

* Experience with capacity planning, scheduling, reporting, or other complex B2B SaaS products.

* Experience working with distributed or microservice systems, a basic understanding of infrastructure and infrastructure as code, and some experience creating, improving, or debugging CI/CD pipelines.

This Role Is NOT

* A ticket-taker role. If you want fully specced work handed to you, this isn't the right fit.

* A pixel-pusher translating finished designs into code with no say in the problem or the solution.

* A role where you hand off at the API boundary. If "that's a backend ticket" is your instinct, this will frustrate you.

* A role where quality is someone else's job. Toggl doesn't have a dedicated QA team or layer: there's no separate team that will catch your bugs, write your tests, or own your performance regressions.

* A place to work in isolation from users. You'll be expected to know who you're building for and why.

*…