South Guild Tech
Website:
southguild.tech
Job details:
Full Stack Engineer (2–4 yrs)
Who we are SouthGuild is an applied AI R&D lab operating across business, medicine, and audit. We combine domain depth with strong engineering in NLP, data systems, and emerging tech to solve high-impact problems. Work spans consulting → prototyping → production systems.
Why this role exists (core) Build end-to-end systems where the API contract, the data layer, and the rendered pixel are equally load-bearing. A bug here is rarely "frontend" or "backend" — it's a race condition stretched across both. We need engineers who can chase it without changing tabs.
Why you should care
- Constant exposure to messy, non-textbook problems
- Engineering-first culture (yes, we enjoy DSA)
- Direct product involvement no PM bottlenecks
- Cross-domain thinking: AI, systems, design
- Strong peer group; high signal conversations
- Healthy environment (including non-code discipline)
What you'll do
- Tame cross-browser inconsistencies (Safari included) and engineer robust layouts without fragile hacks
- Design clean APIs, model data thoughtfully, and ship migrations without breaking traffic
- Hunt performance bottlenecks across the stack — render thrash, N+1 queries, cold cache, async gaps
- Build secure, testable systems end-to-end (XSS / CSP on the UI; authn/z, rate limits, idempotency on the API)
- Work tightly with AI engineers and infra — full context, not tickets
- Trace bugs from button click → DB row → log line, and fix them at the right layer
- Contribute to UX and system design through reasoned arguments
- Leave code cleaner than you found it; future-you (and your on-call peer) thanks you
What we expect
- 2–4 years of hands-on full-stack engineering (real production, not toy projects)
- Strong JavaScript/TypeScript + CSS fundamentals (not just Tailwind copy-paste)
- At least one backend language used in anger (Python / Go / Node)
- Comfort with one modern frontend framework (React / Angular / Vue)
- SQL fundamentals: schema design, indexing, transactions, reading a query plan
- Solid understanding of browser APIs and HTTP semantics
- Performance and security mindset as a default, not an afterthought
- Ability to hold and navigate complex context across services and layers
- Writes clean, explainable, maintainable code
Bonus signals
- Opinions on bundle size or query plans (ideally both)
- Debugged real production breakages yours or someone else's
- Exposure to AI-driven products or workflows
- Side projects or open-source contributions
- Familiarity with frontend security (CSP, XSS) and backend security (authn/z, secrets, rate limiting)
- Has lived through bugs where the symptom was three layers away from the cause
- Comfort with observability stacks (traces, structured logs, metrics)
Culture
- Curious builders over checklist executors
- Direct, respectful disagreement > silent compliance
- Equal interest in debugging and building
- Comfort with ambiguity and startup velocity
Bottom line If you enjoy hard problems where the answer turns out to be "actually it's a race between the API and the cache, surfacing as a CSS bug" and you want context, not just tasks you'll fit.
Click on Apply to know more.