Hiring both SDE 1 (1Y+ Exp) and SDE 2 (2Y+ Exp) across Full Stack, BE and FE roles
Stack: Node.js, React.js, Next.js, RDBMS (SQL)
Location: Bengaluru (on-site, hybrid)
About Turnover (turnover.biz):
Founded by Anurag Jhaver, the startup is a new age, global B2B marketplace for resellers and retailers. The startup has multiple new age, never seen before features mapped out. The vision of the company is to be among the largest brand focused B2B marketplace globally and be a decacorn in the coming decade.
Anurag has dabbled across product management, venture capital, private equity and consulting post graduating from IIT Guwahati in 2016. As a growth PM, he built the web product at Anar managing the launch and upkeep of million+ pages. He also led referral and reactivation at Anar. Prior to Anar, at First Cheque, Anurag assisted multiple startups with their Seed/ Series A fundraise from Tier 1 VCs. He was associated with TVS Capital and PwC earlier.
Our engineering is led by Abhijit Ghogre. He has 10+ years of experience building backend, frontend and infrastructure for various applications and platforms in e-commerce - storefronts, seller portals and live commerce. He has built multiple 0-1 products in early stage startups (Shop 101) as well as managed products at scale (Glance, Roposo). Along with E-Commerce, he has also built products in Financial Services, GRC and Fleet Management domains for global players.
~$500K in commits from VCs and angels in India and Valley, closing the round in March
Who are we looking for?
A 0-1 hustler who loves to build products from scratch, who loves dealing with ambiguity and is looking to take on major responsibilities. Curious to try new technologies. Bias to ship fast. Someone who can set the engineering culture at the org and is a thoughtful leader and a team player. Great communicator + oriented towards documentation. Looking to move up the ladder quickly.
Responsibilities:
For BE / FS:
For FE / FS:
Systems to be built / integrated: Storefront, Search, Recommendation, Cart, Seller Portal, Analytics, Payments, Messaging, Admin Portal, Logistics, Customer Support
Must have skills:
For BE / FS:
For FE / FS:
Good to have skills:
Why work with us?
To know more about company click the link below:
Kindly do the assignment then we will be able to process your candidature
click the design link and follow up the questions accordingly.
Design link:
https://www.figma.com/file/Tv0...
ode-id=0%3A1&mode=design&t=BfFChCGWPwEER0Wy-1
Problem statement:
We want to develop a simple sign-up and login flow for an e-commerce website where users
are able to mark the categories that they are interested in.
You will see 4 screens in the above design. First 2 are for the registration of new users, the
third one is for the login of an existing user and the 4th one is a protected page that only
logged in users can access. On this protected page, users see a list of categories that we
have in our database (you can use faker to generate this data - https://fakerjs.dev/). Create
100 entries for the categories in your database using faker. Users can mark the categories
that they are interested in. This is a paginated list where only 6 categories are visible at a
time. Users can interact with pagination to see categories on various pages. Users should be
able to see what categories they selected when they logout and login again. So we should
store what they check in our database.
The header is common for all the pages. The header should be static for the scope of this
assignment and should not have any interactions like menus flying out.
What tech to use?
- Database: MySQL or Postgres. We recommend using https://neon.tech/ that offers a
free postgres database. If you are comfortable with any other database provider than
neon, please feel free to use that. Using RDBMS is a must.
- Framework: We recommend using https://create.t3.gg/. This will provide you with
Next.js for developing react components. tRPC for writing APIs. Prisma as a
database ORM and tailwind setup for writing CSS. Please do not use NextAuth.js (or
any other auth library) for this task. If you wish to write APIs outside tRPC in Next.js,
feel free to do so. You can do it normally in Next.js -
https://create.t3.gg/en/usage/trpc#how-do-i-call-my-api-externally.
- VCS: Push your code on github and share the repository link. Please make sure you
create a public repository.
- App hosting: We recommend hosting your app on vercel’s free tier-
https://vercel.dev/. If you have experience with any other free Next.js hosting
provider, feel free to use that.
- Sending emails verification code: Email verification code can be kept static:
12345678 or you can use an email library like nodemailer.
Can I use some other tech stack?
We insist against using what’s recommended above.
One reason is that we want to test how well you acclimatise yourself with a new tech within
your general area of expertise.
And second, we are able to evaluate your submissions uniformly against other submissions
that we receive.
How do I submit the assignment?
Reply to the email with the following:
1. URL of the github project where you pushed your final code.
2. URL of the live website where we can test your app.
What do we test?
1. If you have created the necessary schema and its correctness.
2. If you have created the necessary APIs and their correctness.
3. If you have followed industry standard practices.
4. If you have created the necessary react components and if you reused the
components where required and there is no unnecessary redundancy.
5. If your UI is pixel perfect and you have not used any redundant CSS.
6. If you have made the necessary obvious product assumptions where required.
What if I am purely applying for a frontend role?
You can mock the API responses and skip database design and database creation part. You
still must create dummy APIs and return mock data from them for your frontend app to
consume.
What if I am purely applying for a backend role?
You can ignore the CSS and React.js part. We still expect you to create unstyled default html
inputs and forms to submit the data to the API. It is alright if your HTML looks ugly. All we
care is if its functional and we can test your APIs with it.