Principal Backend Engineer (Go/PostgreSQL) - Remote
Free to start · No card · 5 credits the moment you sign up
Job description
FunnelStory is hiring a Principal Backend Engineer to build reliable customer intelligence and AI workflows. Own unclear product problems and ship solutions customers can trust, using Go and PostgreSQL.
Company Details
FunnelStory brings customer data from multiple systems into a shared context graph, helping revenue teams and AI agents understand accounts and take permissioned actions. Its backend runs on Go, PostgreSQL, Docker, and AWS, with enterprise and on-premise deployments.
Website:
Requirements
Minimum 8 years of backend engineering experience at product-based organisations, including real startup experience.
Strong hands-on experience building production services in Go.
Ability to design PostgreSQL databases, debug queries, and resolve performance issues.
Experience shipping a customer-facing product that uses LLMs to make judgments, beyond a prototype or demo.
Experience owning a service or feature end to end, including reliability and production issues.
Ability to turn unclear customer problems into working solutions independently.
Regular use of AI tools to build products and write clean, maintainable code.
Experience working close to users and improving products through customer feedback.
A public GitHub profile, side project, or technical blog is a strong plus.
Candidate currently working at a product based organisation is a must.
Responsibilities
Build and improve customer-facing features in a multi-tenant Go and PostgreSQL backend.
Connect data sources such as CRMs, conversations, and support systems to produce reliable account intelligence.
Build AI workflows that analyse information, take permissioned actions, and maintain an auditable record.
Decide what an LLM should judge and what application code should calculate and store.
Make workflows safe to rerun and detect drops in output quality.
Keep features reliable and responsive across workspaces with 100 to 100,000 accounts.
Support production operations across AWS, Docker, enterprise, and on-premise deployments.
In the first 30 days, learn the system by shipping 2–3 fixes a week and 1–2 improvements to existing features.
Within 3–6 months, own a major new capability, from an unclear request to a feature customers use regularly. Potential areas include intelligence pipelines, CSM agents, renewal automation, and expansion signals.
Job Details
Location: Remote.
Employment: You will be employed as a full-time contractor with FunnelStory, a USA-based company. The company will not make any deductions from your agreed compensation.
Interview Process
3–4 Technical Rounds: Programming, System Design, and AI Tool Use along with a take-home Assignment
Important Note
ClanX is a recruitment partner, helping FunnelStory hire a Principal Backend Engineer.
Highlights
Own customer intelligence and AI workflows at FunnelStory, turning unclear problems into reliable products with Go and PostgreSQL.
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for ClanX. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.