Senior Full Stack Engineer, People Apps
Job description
Senior Full Stack Engineer, People Apps at Wolt.
About the role
Custom automation services handle employee lifecycle management at scale, and the platform delivers these solutions to a distributed workforce.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Services that manage employee lifecycle events are architected, implemented, and rolled out to support internal users.
The organization's custom automation engine and internally directed full-stack applications are maintained and extended for reliability.
Stakeholder requirements are converted into automated solutions that assist day-to-day operations.
Instructions and documentation are produced for deployed applications so teams can operate and understand them.
Employee lifecycle management services, radio and audio campaigns, and full-stack applications are maintained through ongoing maintenance and iterative improvements.
Potential employee needs are surfaced early so automated options can be provided before issues escalate.
IT functions align to ensure employee tools meet a world-class standard of usability and performance.
Requirements
Python, Flask, FastAPI, React, Vue.js, Pytest, and PostgreSQL are used alongside other data storage technologies.
Professional communication is conducted in English, and fluency in this language is required for the role.
A strong interest in software engineering and automation is demonstrated through relevant experience.
The candidate monitors automation trends and experiments with new tools and approaches.
A quick-thinking mindset enables problem solving while the owner rolls up their sleeves to deliver solutions.
Travel is required when business needs support operations or stakeholders.
Practical notes
The role is based in Budapest under full-time employment terms.
Work is conducted with a globally distributed team in the IT-Automation function.
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Roles in this field rely on Python web frameworks to expose services and on modern JavaScript frameworks for user interfaces. Container orchestration platforms and infrastructure as code tools support scalable and repeatable deployments. Automated testing suites validate behavior and help teams move quickly with confidence.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.