Comment by arnavpraneet

Back to stories Open in a window
Comment

Comment by arnavpraneet

Stpkr Technologies | Noida, India (Delhi NCR) | ONSITE | Multiple roles

Stpkr Technologies is hiring for the following roles to build the next generation of wearable devices.

We are currently looking for the following 4 roles but we are also open to interviewing any candidates who feel like they will do their best work here - even if your skillset/experience doesn't fit the current defined roles. Our current team doesn't fit the conventional mold, and we don't expect our future hires will either. If you don't fit the advertised roles, just send us a mail per the same process with whatever job title would fit you the best.

Work is in person near Noida Sector 18, walking distance from Sector 18 Metro Station. We prefer in office work, but we are super flexible overall, it will be hands down one of the best work environments you can get. Pay is competitive, and there are opportunities to earn meaningful equity down the line. We prefer current and recent undergraduates for our roles. If you are still in college we welcome you to apply nonetheless provided you can work as an intern for us in person. Super-flexible overall and all of our current team started out as interns.

Hiring across OS, full-stack, and hardware. AI policy across all roles: you should be able to do the work without AI, and much faster with it.

Android Systems Engineer (AOSP/BSP) - Everything at the OS layer. You've rooted phones, flashed custom ROMs, broken and fixed Linux for fun. Comfortable in C/C++. GitHub with kernel-adjacent or LineageOS-type projects a plus. Stack: Android, Linux, C, C++, Java. _Filter: send us something you built where you had to fight the OS or hardware.

Full-Stack Engineer (Apps + Backend + ML) - Everything at the platform layer. Generalist who ships end-to-end. Skill check: can build a crude-but-working facial recognition system (camera → model → DB → backend). (using existing facial recog models) Bonus for weird/constrained hardware work or running ML on edge devices. Stack: Android, Java, Python, TypeScript. _Filter: send the most useful thing you've built and used (no CRUD slop). Even better if you still use it for yourself.

Hardware Engineer - Bring-up/Debug/Integration - Take EVT/DVT boards and make them work. Comfortable with J-Link and IDE debugging, reading schematics and reference designs. KiCad/Altium/EasyEDA hobby work would make you ideal. PetaLinux experience or hunger to learn it. ECE undergrad fine. _Filter: photo of a board you designed or debugged, plus what went wrong.

Hardware Engineer - Power/RF/Wireless - Make the power and RF paths behave on EVT/DVT boards. Hands-on with schematic capture, layout, soldering, scope/logic analyzer. Given two unknowns, you pick one and start measuring. _Filter: sensor fusion work, how noise behaves across protocols, and SPI debug chops.

Founder's Office - Work closely with the founder and the rest of the team to manage the day to day and long term affairs of the company, the Man Friday of the company. Must have a decent degree of technical knowledge (we are a tech company after all) and be efficient at administrative tasks as well as management. Speed and learning ability are prized here, there will not always be a clear path to the work you have to do here, so you will have to figure some of it out on your own.

To apply, contact [email protected] with the subject line "HN - Human" and a brief intro for further communication. Attach any documents you deem useful there. Please include the role you are applying for at the top of the email if it is one of the above mentioned, otherwise whatever role fits you best. Shortlisting will be online, interviews will be in person. We are hiring quickly, expect to hear back from us within 2-3 days of applying. If you don't, assume you will not. Thanks for your time!

Replies arnavpraneet · 2026-06-02
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.