Junior Backend Java Engineer Role Summary

<p>Why join Secfix?<br /> Secfix is a fully remote early-stage startup in the best sense: a tight-knit, fun team driven by the mission to automate security and compliance for modern companies and become Europe’s leader in compliance automation. We’ve grown quickly—from three founders to 20 team members in under two years.</p> <p>Your work will have a real impact on a product used by CTOs, engineering teams, and COOs, and the entire team will celebrate your wins.</p> <p>Unlike many startups, we’re growing at a sustainable pace, balancing rapid progress with careful runway management. Most of our costs are already covered by revenue.</p> <p>With big goals ahead (we plan to double the team next year), you’ll experience continuous growth and development. Our momentum is supported by top investors, including Octopus Ventures, Neosfer (Commerzbank), the founders of Signavio, and several seasoned angel investors.</p> <p>Who are we looking for?<br /> We’re building an environment where ambitious, self-driven engineers can truly excel. We want people who take pride in building and maintaining real products, who are curious about how our features solve real problems, and who use their deep engineering insight to push our product forward. We focus on owning products and outcomes—not just completing Jira tickets.</p> <p>Bring your drive and desire to grow, and we’ll provide a supportive environment that keeps you happy, healthy, and empowered to do your best work.</p> <p>This role consists of roughly 90% backend troubleshooting and 10% new feature development.</p> <p>Experience you ideally bring:<br /> • At least 1 year of backend engineering experience through a full-time role or internships<br /> • Strong grounding in object-oriented programming with Java<br /> • Initial production experience with Java Spring Boot, Hibernate, and SQL<br /> • Familiarity with third-party APIs and interest in monitoring and troubleshooting<br /> • A willingness to take ownership, collaborate, and adapt to feedback </p> <p>You should apply if:<br /> • You are ambitious, independent, and eager to grow<br /> • You bring early career talent with at least one year of relevant experience<br /> • You have strong engineering fundamentals and write efficient code, knowing your strengths and weaknesses<br /> • You thrive with autonomy and enjoy managing your own work<br /> • You communicate well in a remote setting and understand that remote work requires proactive communication </p> <p>You should not apply if:<br /> • You need heavy processes or rely on detailed Jira tickets to know what to do<br /> • You only want to write code without caring about customers or the bigger picture<br /> • You don’t want to test, deploy, monitor, and troubleshoot your own work<br /> • You prefer to be led rather than leading your own projects<br /> • You don’t want to collaborate closely with other teams or speak with users when needed </p> <p>What happens when you join us?<br /> • You’ll take ownership of complex backend issues, collaborating with the Tech Lead while solving problems independently<br /> • You’ll debug, troubleshoot, and fix production bugs that impact customers<br /> • You’ll strengthen your backend expertise with technologies like Java Spring Boot, Hibernate, and SQL<br /> • You’ll work closely with a skilled team to analyze root causes, design solutions, and improve backend systems<br /> • You’ll occasionally contribute to new feature development as the product evolves<br /> • You’ll embody our values: customer obsession, smart building, trust creation, hackiness, ownership, and excellence in remote work </p> <p>Our technology stack:<br /> • Frontend: Typescript, Angular, Ngrx, Tailwind, Material UI<br /> • Backend: Java Spring Boot, PostgreSQL, Hibernate<br /> • MDM product: Golang and Osquery<br /> • Infrastructure: AWS with ECS<br /> • Tools: GitLab CI/CD, Figma, Slack, Notion, Gather.town, ClickUp </p> <p>Interview process:<br /> We aim to invite promising applicants to interview within a week and provide feedback after the take-home assignment.</p> <p>The process includes:<br /> 1. Introductory call with our talent team (15–20 minutes)<br /> 2. Take-home task (1–2 hours) and technical interview with the Tech Lead<br /> 3. Virtual on-site with the team and co-founders on Gather.town (around 2 hours)<br /> 4. Offer </p> <p>After applying, expect an email from Grigory (CTO) or Chiara (People Ops). We move quickly.</p> <p>What we offer:<br /> • 100% remote work with a virtual office in Gather<br /> • Competitive local salaries following GitLab’s philosophy<br /> • Generous equity package—everyone is an owner<br /> • 26 vacation days plus public holidays<br /> • Comprehensive health insurance<br /> • €1,000 yearly personal development budget<br /> • Remote workspace budget and access to co‑working spaces<br /> • Annual retreat (this year: Milan!)<br /> • Modern tech equipment (MacBook, monitors, headphones)<br /> • Company-wide events to connect and have fun<br /> • Access to top-tier mentors through our investors </p> <p>We are an equal-opportunity, remote-only company. Because we rely on synchronous communication for fast collaboration, we cannot support fully asynchronous work.</p>

Back to blog

Other Jobs To Apply

No other job posts for this day.

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...