Senior Software Engineer

We are looking for a Senior Software Engineer to join our PL engineering team and work on an ecosystem of various microfrontend modules deployed within high-throughput, robust career document builders.

In this role, we’d like to invite you to our team as an individual contributor, but also as an architect and owner of business-goal-driven areas of frontend development.

In addition to the above, we’re looking for someone who’s willing to share their knowledge and expertise with their teammates, earned through experience working with client-oriented B2C applications.

ABOUT THIS TEAM

BOLD’s PL engineering organization has been responsible for growing and maintaining both greenfield and brownfield projects, ranging from entire resume and cover letter builders, with a strong focus on optimizing both pre- and post-conversion user flows, to independent white-label features deployed across a wide variety of brands and adjusted, both in terms of design and functionality, to fit specific market needs.

As of now, our main areas of responsibility are small- and medium-sized client-side rendered React apps that provide a broad range of job-hunting functionality, including market-leading, AI-enabled capabilities that support resume refinement, job search, and agentic applications to relevant openings - amongst other things.

The team itself is currently composed of seven people, with experience distributed mainly around the middle of the seniority spectrum. We collaborate closely with our dedicated QA team and many others across the globe, organized into silos based on areas of responsibility and expertise - it’s never a dull moment here :)

How do we work?

Our meetings and rituals

Daily meetings at 9:15 AM - to sync up every morning and plan for the day.

Weekly refinement meetings on Wednesdays and Fridays - to refine and estimate workload, plan sprints, and share the top-down perspective on our timelines and goals.

Regular product calls with our PMs and business stakeholders - our source of priorities and requirements, and a great way to hone one’s communication skills and demonstrate ownership.

We follow flexible core hours between 9:00 and 15:00 to maintain easy communication between teammates.

Our processes, workflow and project management methodology

Two-week sprints, ending with a rolling deployment of multiple apps to production environments.

We aim for Agile-adjacent - we estimate tickets based on prior experience and compose workloads based on the team’s actual capacity.

We follow continuous integration (CI) principles - our devs own their changes end-to-end, with the help of our code-quality and automated-testing suite living in our pipelines, merging straight into testing environments where our QAs await.

Finally

Monthly, our team leaders hold F2Fs with their team members. In the broader scope, we evaluate our yearly progress during Annual Reviews, where we plan for further growth and act on bilateral feedback.

We’re AI-positive - while we recognize that the rapid progress of LLM-based coding tools is a challenge in itself, we believe that the best results lie at the intersection of the depth of individual experience and AI’s ability to multiply its magnitude. We actively use frontier models via GitHub Copilot (with a generous amount of tokens to spend), or any other preferred coding harness — we discuss the best approaches and share tips and expertise. We’re looking forward to what the future holds, and to a candidate who shares this optimism.

Technologies/tools we use:

Language: TypeScript 7

Build/serve: Vite 7 + Rollup + React Compiler compile each app to a client-rendered SPA (no SSR), served as static files by nginx

UI: React 18 with react-router 7, SCSS + CSS Modules, react-intl/FormatJS i18n

State/data: Redux Toolkit for app state + Zustand for local/widget state, talking to BE via custom wrapped fetch

Monorepo: pnpm workspaces (Node 26) orchestrated by Turborepo across packages (shared libs) -> apps (SPAs) -> widgets (embeddable npm libs) -> tools

Quality: tsc + Oxlint + oxfmt, Stylelint, Husky + lint-staged

Architecture: Micro-frontends as independently built/deployed SPAs (no module federation) plus embeddable widget libraries, sharing a common core (components, utils etc.), config-driven per brand/site

Misc: vscode + git, code hosted at Github

AI: Frontier models offered via Github Copilot

Our recruitment process consists of the following stages:

Recruiter Screening Call – An initial conversation to discuss your experience, motivation, and expectations.

Technical Questionnaire and Live Coding – A technical quiz followed by a short live coding exercise.

Final Interview – A discussion focused on system design, technical challenges, and practical business scenarios. We would ideally like the final stage to take place onsite at one of our offices in Warsaw or Gdańsk.

WHAT YOU’LL DO

Build microfrontend apps from the ground up and maintain existing ones, seamlessly embedded within host codebases to provide a great user experience. Work alongside our Lead and Principal Engineers on our monorepo architecture, supporting different deployment styles and use cases, maintaining code quality through code reviews and improvements to our automated checks, as well as by providing guidance and sharing knowledge with less experienced colleagues.

We’re mostly focused on CSR frontend apps, with occasional dives into SSR and orchestration-layer backend services - but be prepared to step outside the boundaries of your current tech stack to support new kinds of requirements.

You’re gonna meet with our business stakeholders to discuss goals and requirements, analyze designs in Figma, plan work, and set boundaries wherever responsibilities should be delegated to other teams. Based on the above, you’ll act as a proxy for other developers, ensuring their efforts are guided by your examples and that blockers are resolved.

Be a great teammate - participate in our rituals, be proactive about problem-solving and communication, and enjoy the occasional off-topic discussion during daily meetings ;)

WHAT YOU’LL NEED

At least 4 years of experience developing high-availability B2C applications.

Deep understanding of, and good intuition for, the CSR TypeScript + React stack.

Expertise in frontend best practices - writing readable, extensible and maintainable code, making performance-aware decisions, and ensuring a great user experience even under suboptimal conditions - alongside experience using the libraries and tools listed in the section above.

Ability to model and reason about multi-purpose monorepo codebases, make architectural decisions, and instill confidence in those decisions across the team

Product-driven, customer-first thinking - we deliver what our users see as the core of the product; we don’t compromise on layout, animation or interaction quality, and we ensure that user flows remain frictionless.

Experience debugging both static and runtime issues in mixed-ownership environments - having multiple codebases contribute to a single screen can pose non-standard challenges.

Experience implementing and maintaining feature flags and running A/B tests, extensive conditional rendering.

Ability to discuss and reason through technical decisions with other engineering teams, working toward the same goal while respecting differences in ownership and responsibilities.

Maturity required to guide and coach others.

Knowledge of spoken and written English at least at the B2 level.

Knowledge of spoken and written Polish at least at the C1 level.

WHAT’S GOOD TO HAVE

Experience with open-source, self-hosted observability platforms such as Grafana, including Faro, Alloy and Loki.

Experience architecting and implementing vector embedding-based solutions for medium to large volumes of text.

Opinions on, and willingness to implement, agentic AI wo