Senior Backend Engineer - Data Core (remote, Europe)
About this role
Remote — Data Core Team — Full-time Hey, I'm Andrei . I’m hiring a Senior Backend Engineer to join the Data Core team at Modash. Modash helps brands find, understand, and work with creators across Instagram, TikTok, and YouTube. More than 2,700 companies—including Stanley 1913, Sennheiser, and NordVPN—use us to manage and scale their creator partnerships. Every one of those products depends on fresh, reliable creator data. Data Core owns the systems that collect and maintain profiles for 400M+ creators across social platforms, process billions of data points, and keep the rest of Modash supplied with the raw material it needs. That’s where you come in. Why we're hiring Data Core isn't an internal support team. It owns the collection infrastructure that the entire Modash product—and every d
About software engineering roles
Software engineers design, build, test, and maintain code that powers a product. Day-to-day work mixes writing code, code reviews, debugging production issues, design discussions, and meetings — exact ratio depends on seniority and team size.
Typical skills: Git, one or more languages (JavaScript/Python/Go/Java/Rust), database basics, system design at the senior level
Gear that helps in this role
Remote software engineering setups commonly include:
Affiliate links — small commission to us at no extra cost to you.
Salary insights (US, rough)
Typical range for software engineering roles in the US is $75,000–$220,000/year, varying widely with seniority, company stage, and city.
Estimates only. For company-specific numbers, check levels.fyi (tech), Glassdoor, or ask in the interview.
How to prep for the interview
Most software engineering interviews follow a predictable arc: a recruiter screen, a technical screen (coding or system design), one or more on-site / virtual on-site loops (more coding + behavioral + system design + maybe a deep-dive on a project from your resume), and a final manager or "fit" round. Expect 4–6 hours of total interview time for a senior role, less for junior.
Be ready for: "Walk me through a recent project — what tradeoffs did you make?", "How would you design a service to do X?", a live coding exercise (LeetCode-medium-ish), and "Tell me about a time you disagreed with a teammate". Practice talking while coding — silence in a 45-minute exercise reads as not knowing what you're doing, even when you're just thinking.
Where this role typically leads
Typical progression: Junior (0–2 yrs) → Mid (2–5 yrs) → Senior (5–8 yrs) → Staff / Principal (8+ yrs), with manager track diverging around the senior level. Salary roughly doubles between junior and senior at most companies; staff+ adds another 30–50% for IC track, more for management at big-tech scale.
The biggest career inflection points: going from "writes the code" to "designs the system" (around mid-to-senior), and going from "owns a feature" to "owns ambiguity" (around senior-to-staff). The skill that matters most at every level above junior is communicating technical decisions clearly to non-engineers — not raw coding speed.
Red flags to watch for
- "Rockstar developer wanted" — usually means the role is overworked and under-supported. Look for "team", "collaboration", and "mentorship" in the JD instead.
- No mention of code reviews, testing, or CI/CD. Either the company doesn't do them (technical debt is rampant) or doesn't think they matter enough to mention.
- "Full-stack" in the title but the JD lists 12 frameworks. They want a unicorn for the price of one engineer. The role will be brutal.
- Vague on-call expectations. Always ask explicitly: "How often are engineers on call? What's the pager load?"
Frequently asked questions
How do I apply to this role?
Click the "Apply on Arbeitnow" button at the top of this page. You'll be sent to the original posting where the employer accepts applications. Wikishopline doesn't collect resumes or process applications.
Is this listing current?
Wikishopline aggregates jobs daily from partner sources (arbeitnow). Postings older than ~14 days are pruned, but always verify the role is still open on the employer's site before you spend time on a cover letter.
Does Wikishopline charge employers or applicants?
No. Aggregated jobs are free for both sides. Wikishopline also accepts $5 / 30-day paid postings at /jobs/submit for employers who want direct visibility — but the listing you're viewing was sourced from a partner.
What does a software engineering role typically involve?
Software engineers design, build, test, and maintain code that powers a product. Day-to-day work mixes writing code, code reviews, debugging production issues, design discussions, and meetings — exact ratio depends on seniority and team size.
What's the typical salary range for software engineering roles in the US?
Roughly $75,000–$220,000 USD/year, depending on seniority, location, and company stage. This is a wide range on purpose — verify against levels.fyi or Glassdoor for the specific company.